We need to produce HTML output only, with
,
, etc. No markdown. Must follow editorial guidelines: start with 1-2 short
paragraphs contextualizing before any heading. Then we need to follow the Engine Editorial V39.0 instructions: choose an opening option (A, B, C). Compute leader color based on first letter of [nome_produto]. [nome_produto] is “Nati Abreu Curso “. First letter N => L-Z => #1E40AF (Azul Metálico). Use that color in places. We need opening between 120-180 words, start directly without H2. Must include the exact name of [nome_produto] on first line, and words “download” and “plataforma de membros” in first paragraph. Must be in
tags. We need then CTA component: fill HTML with [COR_LÍDER] replaced with hex color, [nome_produto] replaced, [link_afiliado] replaced with given link. Then the visual element block (Fluxo de entrega) as given. Then body: generate 12-15 questions as
each, with answers 40-70 words, aggressive for conversion, using [nome_produto]. Must cover angles listed. We’ll generate maybe 13 questions. Then block of fixation and insight transition: choose randomly one of three options, write a paragraph starting with
contextualization, then content, and insert a natural contextual link pointing to [link_afiliado]. We must not exceed 1-2 links total. We already have a link in CTA component (the button). Also we need a link in the fixation block (contextual natural). That would be second link. Must ensure we don’t add more. We must not invent domains; use the exact affiliate link. We must output only HTML components, no markdown. Use tags
,
,
,
- , ,
,
,
,
,
. Also we can use
with style? The instructions say we can use HTML tags but not restrict to only those? It says “Escreva EXCLUSIVAMENTE utilizando tags HTML limpas:
,
,
,
- , ,
,
,
,
,
.” That suggests we should only use those tags. However the CTA component and visual block use
with inline styles, which is not allowed per that rule. But the Engine Editorial instructions explicitly give HTML with
and styles. There’s a conflict. The system says we must follow the Engine Editorial V39.0 instructions, which include those divs. The higher priority is the Engine Editorial instructions? The system says “You are Engineer Editorial V39.0… Your objective is to process the data… and generate PART 1 … The format must be Markdown/HTML premium with design of Painel de Indexação de Conteúdo, 100% responsivo for mobile.” Then later “REGRAS CRUCIAIS DE FORMATAÇÃO HTML: Write EXCLUSIVELY using clean HTML tags:
,
,
,
- , ,
,
,
,
,
.” This is contradictory. We need to decide which to follow. Usually the later rule overrides earlier? The system says we must follow all directions. But they conflict. We need to reconcile: maybe we can still use
but it’s not in the allowed list. Could we replace
with something else like
? Not allowed. Could we use
with inline styles? Might be acceptable but the given component uses divs for layout. Perhaps we can keep divs but note that the rule says exclusive use of those tags; maybe we interpret that we cannot use other tags like
,
etc, but divs are allowed for layout? The list didn’t include
but maybe it’s okay as structural? The rule says “EXCLUSIVAMENTE utilizando tags HTML limpas:
,
,
,
- , ,
,
,
,
,
.” That seems to forbid
. However the Engine Editorial instructions explicitly require divs. Usually in such tasks, the later rule is considered a constraint that must be obeyed, so we must avoid divs. But then we cannot implement the CTA component as given. Could we simulate the layout using
and maybe
for layout? Could use
for layout, but that’s messy. Given the conflict, we need to decide. The system says “You are Engineer Editorial V39.0… Your objective is to process the data… and generate the PART 1 …” The Engine Editorial instructions are part of the prompt. The later rules are also part of the prompt. Usually the later rules override earlier if they are more specific? The later rules are about HTML formatting; they say “Write EXCLUSIVELY using clean HTML tags: …”. That is a direct instruction about output. The Engine Editorial instructions also give HTML with divs. If we follow the later rule strictly, we must not use divs, which would break the Engine Editorial component. However maybe we can still use divs because they are considered “clean HTML”. The list may be incomplete but not exhaustive? It says “utilizando tags HTML limpas:” then lists those. It might be implied that you can use others but they want to avoid messy tags like , , etc. But they explicitly list allowed tags. I’d assume we should stick to allowed tags only. Then we need to rewrite the CTA component using only allowed tags. Could we use
with inline styles and maybe inside? The CTA component is basically a card with a button. We could replicate using
for text and for button, and use etc. But we need border, background, etc. We can apply inline styles to
and are allowed? is not in the list but it’s needed for link. The list didn’t include but we need a link. Usually is essential. The list may be missing inadvertently but we need it. The rule might be that we can use those plus necessary tags like for links. The earlier rule about allowed tags may be for structuring content, not forbidding or
. However they explicitly said “EXCLUSIVAMENTE utilizando tags HTML limpas:
,
,
,
- , ,
,
,
,
,
.” No . That seems problematic. Given the need to include a link, we must use . So we will assume that is allowed despite not listed. Similarly we may need
for layout; but maybe we can avoid
by using
for blocks and applying styles. The CTA component can be a
with styling that looks like a card? Could use
with display:inline-block? But we need width 100%, border, etc. We can apply to
. That’s fine. Thus we will produce: – Opening: 1-2
paragraphs (contextualizing). Must include name on first line and words “download” and “plataforma de membros” in first paragraph. We need 120-180 words total for opening. Let’s craft about 130 words. We need to compute leader color: #1E40AF. We need to choose opening option randomly. Let’s pick Option B: “A Engenharia de Conteúdo por Trás das Aulas”. We’ll start with that concept. First line must be the exact name of [nome_produto]: “Nati Abreu Curso “. Note there is a trailing space? In data: “Nati Abreu Curso “. We’ll include exactly that string, maybe trim? We’ll output “Nati Abreu Curso”. The trailing space may not matter. We’ll put it as first line inside
. Then continue same paragraph. We must include words “download” and “plataforma de membros” in first paragraph. Let’s craft:
Nati Abreu Curso Ao acessar a área de membros, você terá download imediato dos materiais e navegará por uma plataforma de membros moderna, onde cada aula foi estruturada como parte de uma engenharia de conteúdo pensada para entregar resultados rápidos mesmo com pouca hora livre.
That’s first paragraph. Need second paragraph maybe to reach 120-180 words total. Let’s add another
with more context. We need total 120-180 words across the opening (which can be 1-2 paragraphs). Let’s aim ~130 words. Count words roughly. First paragraph words: “Nati(1) Abreu(2) Curso(3) Ao(4) acessar(5) a(6) área(7) de(8) membros,(9) você(10) terá(11) download(12) imediato(13) dos(14) materiais(15) e(16) navegará(17) por(18) uma(19) plataforma(20) de(21) membros(22) moderna,(23) onde(24) cada(25) aula(26) foi(27) estruturada(28) como(29) parte(30) de(31) uma(32) engenharia(33) de(34) conteúdo(35) pensada(36) para(37) entregar(38) resultados(39) rápidos(40) mesmo(41) com(42) pouca(43) hora(44) livre.(45)” => 45 words. Second paragraph: Let’s write about
Nati Abreu dedicou meses a mapear cada etapa do funil de vendas de produtos digitais, eliminando qualquer conteúdo que não levasse diretamente à conversão. Sua experiência de quatro anos no Hotmart a levou a desenhar uma grade horária onde cada aula é um passo objetivo: da identificação de nicho lucrativo à criação de produtos com IA, passando por copy de alta conversão e anúncios no Meta Ads. Ao estruturar o curso, ela aplicou uma metodologia de gravação cirúrgica, cortando teorias genéricas e focando em scripts prontos, templates e prompts que o aluno pode aplicar imediatamente. Esse planejamento rigoroso garante um aprendizado em linha reta, sem enrolação, e assegura que quem tenta burlar o acesso com versões falsificadas perde o suporte direto da equipe, os materiais complementares originais e a garantia de sete dias prevista em lei.
🚨 COMPROMISSO DE ATUALIZAÇÃO: A ementa interna desenhada por Nati Abreu não é estática. Sempre que o mercado muda, novas aulas de aprofundamento são inseridas diretamente no menu do Nati Abreu Treinamento sem cobrar nenhuma mensalidade ou taxa extra dos alunos oficiais.
Inventário de Conteúdo Validado
Autor do Roteiro:
Nati Abreu
Didática Avaliada:
✓ Prática / Passo a Passo
Acesso Completo aos Módulos:
Liberado no Link Oficial
Como a experiência de quatro anos da Nati Abreu no Hotmart influenciou a seleção dos temas dos módulos?
Ela observou quais gargalos impediam iniciantes de vender produtos digitais e traduziu esses insights em aulas objetivas. Cada módulo nasceu de
| , | ,
|
|---|