Preparatório PM-RJ Comprovado | Instituto Óliver 12×14,27
We need to produce PART 1 of a report focusing on “Login / Área de membros / Como acessar”. Must be Markdown/HTML premium with static design focusing on Security of Authentication and Onboarding, 100% responsive for mobile. Use only allowed tags:
,
,,- , ,
,,, ,. No markdown syntax like #, **, etc. Only HTML tags. Must start with a
contextualizing analysis before any question. Must not start with
. Must have intro paragraph(s) of 1-2 short paragraphs in
tags before exposing any question. Must generate 12-15 questions as
each, with answers 40-70 words, aggressive conversion tone, using product name. Must embed the static design components as described. We need to choose one of three options for opening article: Option A, B, or C. Choose randomly or sequentially. We’ll pick Option A: “A Rota de Acesso Oficial e Login Seguro”. Must include product name exactly as [nome_produto] = “Preparatório Completo PM-RJ – Pracinha”. Must include words “e-mail de acesso” and “plataforma de alunos” in first paragraph. Must be 120-180 words. Must be in
tags (multiple paragraphs okay). Must be direct, no H2. Then determine COR LÍDER based on first letter of product name. First letter is ‘P’ (since product name starts with “Preparatório”? Actually product name is “Preparatório Completo PM-RJ – Pracinha”. The first character is ‘P’. The rule: A-K = #059669 (Verde Esmeralda) | L-Z = #0F172A (Azul Noturno / Grafite Escuro). ‘P’ is in L-Z, so COR_LÍDER = #0F172A (dark blue/gray). Use that hex for border and accent. We need to embed the CTA component HTML with [COR_LÍDER] replaced with #0F172A, and [nome_produto] replaced with exact product name. Also link href must be the affiliate link exactly: https://go.hotmart.com/N106245370A?dp=1. Need to include the visual static entry block (the “Roteiro Estático de Entrada”) as provided. Then generate 12-15
questions with answers 40-70 words each, focusing on login issues etc. Must be aggressive conversion tone, using product name. We must ensure answers length 40-70 words. We’ll craft maybe 13 questions. We must not use markdown syntax; only HTML tags. Use
,
not allowed; we must use for questions? The instruction says each question should be a. So we will useQuestion
. That’s allowed? The allowed tags list includes
, but not. However the instruction says “transformando-as em ``”. The allowed tags list didn’t include. But the directive says we must use only tags:
,
,,- , ,
,,, ,. It does not include
. Conflict. But the instruction explicitly says to transform them into. The higher-level instruction likely overrides allowed tags? The “REGRAS CRUCIAS DE FORMATAÇÃO HTML” says “Escreva EXCLUSIVAMENTE utilizando tags HTML limpas:
,
,,- , ,
,,, ,.” So we cannot use
. But the earlier part says to create. There’s conflict. We need to decide which to follow. The higher-level “REGRAS CRUCIAS DE FORMATAÇÃO HTML” seems more specific and must be followed. So we cannot use. But the earlier part says to create. The instruction hierarchy: The user gave detailed directives, including “Cada resposta deve ter entre 40 a 70 palavras, ser agressiva para conversão e usar o nome [nome_produto].” and “As perguntas geradas por você devem cobrir… transformando-as em ``.” Then “REGRAS CRUCIAS DE FORMATAÇÃO HTML: 1. Escreva EXCLUSIVAMENTE utilizando tags HTML limpas:
,
,,- , ,
,,, ,.” So we cannot use
. Perhaps we can use for questions? But they specifically said. However the rule says only those tags allowed. Possibly we can use as a substitute? But they’d want. I’d prioritize the explicit rule that we can only use those tags. But the earlier instruction about may be considered part of the content generation, not a tag restriction? The rule says “Escreva EXCLUSIVAMENTE utilizando tags HTML limpas:
,
,,- , ,
,,, ,.” That seems to restrict all tags to those. So we cannot use
. But we need to output questions as. Conflict. I think we must obey the stricter rule: only allowed tags. So we cannot use. Maybe we can use for questions, but that deviates from instruction. However the instruction says “transformando-as em ``”. Might be considered part of the output spec, but the later rule overrides? Usually the later rule is more specific about formatting. I’d choose to use because it’s allowed, but that may be considered not following the instruction. But the instruction also says “Cada resposta deve ter entre 40 a 70 palavras, ser agressiva para conversão e usar o nome [nome_produto].” It doesn’t explicitly require tag, just says transform them into. But the rule says only certain tags allowed; is not allowed. So we must not use. Perhaps we can use as the closest allowed heading. But they’d want. I think we should use and note that it’s the only heading allowed. However the rule also includes as allowed. So we can use for questions. Thus we will use for each question. That satisfies allowed tags. We need to produce 12-15 questions. Let’s do 13 questions. Each answer 40-70 words. We’ll craft each answer accordingly. We must include the link to affiliate at the end of the fixation block. We must start with a
contextualizing analysis before any question. That means before the first
we need a
paragraph that contextualizes the analysis of the product before exposing any question. The instruction: “Entrada editorial obrigatória: Comece o seu texto obrigatoriamente gerando de 1 a 2 parágrafos curtos em tags
contextualizando a análise técnica do produto antes de expor qualquer pergunta. Não comece o texto direto com uma tag de título
.” So we need 1-2 short paragraphs in
tags before any
. So we will have maybe two
paragraphs that talk about the product technical analysis, then after that we start with
questions. But also we need to include the opening dynamic part (120-180 words) before any question. That opening must be in
tags as well, and must include product name and “e-mail de acesso” and “plataforma de alunos”. That opening is part of the article before any question. So we need to embed that opening as
paragraphs (maybe multiple) before the first
. That’s okay. Thus structure: – Opening dynamic paragraph(s) in
tags (120-180 words) includes product name, “e-mail de acesso”, “plataforma de alunos”. Must be 120-180 words total. We’ll write maybe two
paragraphs to reach word count. – Then after that, we need to include the CTA component HTML (the card) as given. That HTML includes
etc. That’s allowed? The allowed tags list does not include, but the instruction includes that HTML block as part of the output. The rule says “Escreva EXCLUSIVAMENTE utilizando tags HTML limpas:,
,,- , ,
| , | ,
|
|---|