IA para Publicação de Livros: Design de Capas e Marketing 2026

<think>The user wants me to translate a fragment from an article about AI for book publishing into natural, fluent Portuguese. I need to:

1. Keep all markdown syntax intact
2. Keep all URLs, image paths, and HTML tags as-is
3. Keep the brand "GLMImage" untranslated
4. Use natural, fluent Portuguese
5. Output only the translated markdown

Let me translate the content into Portuguese:

• "AI for Book Publishing: Complete Cover Design & Marketing Guide" → "IA para Publicação de Livros: Guia Completo de Design de Capas e Marketing"
• "AI for book publishing" → "IA para publicação de livros"
• "means using image generation to create book covers, author promotional materials, social assets, and interior illustrations — at a cost that makes sense for independent authors and small publishers." → "significa usar geração de imagens para criar capas de livros, materiais promocionais para autores, ativos para redes sociais e ilustrações internas — com um custo que faz sentido para autores independentes e pequenas editoras."</think>

IA para Publicação de Livros: Guia Completo de Design de Capas e Marketing

IA para publicação de livros significa usar geração de imagens para criar capas de livros, materiais promocionais para autores, ativos para redes sociais e ilustrações internas — com um custo que faz sentido para autores independentes e pequenas editoras.

<think>The user wants me to translate a markdown fragment about AI-generated book covers and GLMImage into Portuguese. I need to keep all markdown syntax, URLs, image paths, and HTML tags exactly as-is. The brand "GLMImage" stays untranslated. Let me translate this naturally into Portuguese.</think>

Principais Conclusões

1. Capas de livros geradas por IA reduzem os custos de design de $300–1.500 para o preço de um mês de assinatura — menos de $10 em custos de geração — permitindo que autores independentes compitam em apelo visual nas prateleiras.

2. A renderização de texto do GLMImage (91,16% no benchmark CVTG-2K, em inglês e chinês) o torna singularmente adequado para tipografia de capas — títulos e nomes de autores precisos e legíveis onde outras ferramentas de IA falham.

3. Fluxos de trabalho bem-sucedidos de capas de livros com IA priorizam as convenções de gênero — códigos visuais e paletas consagrados que sinalizam a categoria instantaneamente, com a originalidade vindo das escolhas de composição e detalhes.

<think>The user wants me to translate this short fragment into Portuguese. It's a very brief section with a heading and an image. Let me translate it naturally.

"Book Cover Design by Genre" = "Design de Capas de Livros por Gênero"

The image URL should be kept as-is.</think>

Design de Capas de Livros por Gênero

<think>The user wants me to translate this article fragment into natural, fluent Portuguese. Let me carefully go through each element:

1. The heading "Fiction Genre Cover Conventions" needs to be translated
2. The image alt text needs translation
3. The table headers and content need translation
4. Keep URLs intact
5. Keep markdown formatting intact

Let me translate:

• "Fiction Genre Cover Conventions" → "Convenções de Capas por Gênero de Ficção"
• Image alt text: "Fiction Genre Cover Conventions" → "Convenções de Capas por Gênero de Ficção"
• Table headers:
  • "Genre" → "Gênero"
  • "Visual Elements" → "Elementos Visuais"
  • "Color Psychology" → "Psicologia das Cores"
  • "Key Design Elements" → "Elementos de Design Principais"

Table content:

• Romance: "Couples, embraces, silhouettes" → "Casais, abraços, silhuetas"

  • "Pinks, reds, soft pastels" → "Rosas, vermelhos, pastéis suaves"
  • "Emotional intimacy, warmth" → "Intimidade emocional, calor"

• Thriller/Mystery: "Shadows, isolated figures, clues" → "Sombras, figuras isoladas, pistas"

  • "Dark blues, blacks, red accents" → "Azuis escuros, pretos, toques de vermelho"
  • "Tension, intrigue, danger" → "Tensão, intriga, perigo"

• Fantasy: "Magical elements, landscapes, creatures" → "Elementos mágicos, paisagens, criaturas"

  • "Deep purples, golds, blues" → "Roxos profundos, dourados, azuis"
  • "Wonder, epic scale" → "Maravilha, escala épica"

• Science Fiction: "Technology, space, futuristic" → "Tecnologia, espaço, futurista"

  • "Neon blues, metallic, black" → "Azuis neon, metálicos, preto"
  • "Innovation, future worlds" → "Inovação, mundos futuros"

• Historical Fiction: "Period clothing, settings" → "Roupas de época, cenários"

  • "Sepia, muted tones, parchment" → "Sépia, tons suaves, pergaminho"
  • "Authenticity, era feel" → "Autenticidade, sensação de época"

• Literary Fiction: "Abstract, symbolic, minimalist" → "Abstrato, simbólico, minimalista"

  • "Muted, sophisticated palettes" → "Paletas suaves e sofisticadas"
  • "Depth, sophistication" → "Profundidade, sofisticação"

Let me verify this all sounds natural in Portuguese.</think>

Convenções de Capas por Gênero de Ficção

Gênero	Elementos Visuais	Psicologia das Cores	Elementos de Design Principais
Romance	Casais, abraços, silhuetas	Rosas, vermelhos, pastéis suaves	Intimidade emocional, calor
Suspense/Mistério	Sombras, figuras isoladas, pistas	Azuis escuros, pretos, toques de vermelho	Tensão, intriga, perigo
Fantasia	Elementos mágicos, paisagens, criaturas	Roxos profundos, dourados, azuis	Maravilhamento, escala épica
Ficção Científica	Tecnologia, espaço, futurista	Azuis neon, metálicos, preto	Inovação, mundos futuros
Ficção Histórica	Roupas de época, cenários	Sépia, tons suaves, pergaminho	Autenticidade, sensação de época
Ficção Literária	Abstrato, simbólico, minimalista	Paletas suaves e sofisticadas	Profundidade, sofisticação

<think>The user wants me to translate a markdown table about book cover design conventions into Portuguese. Let me translate it carefully, keeping all markdown syntax, table structure, and formatting intact.

Let me translate:

• Genre → Gênero
• Visual Elements → Elementos Visuais
• Color Psychology → Psicologia das Cores
• Key Design Elements → Elementos de Design Principais
• Non-Fiction Genre Cover Conventions → Convenções de Capas do Gênero Não-Ficção

Business → Negócios/Empresarial
Self-Help → Autoajuda
Health/Fitness → Saúde/Fitness
Cookbooks → Livros de Culinária
Biography → Biografia
Academic → Acadêmico

Visual elements:

• Abstract success symbols → Símbolos abstratos de sucesso
• Upward movement, light → Movimento ascendente, luz
• Active figures, vitality → Figuras ativas, vitalidade
• Food photography, ingredients → Fotografia de alimentos, ingredientes
• Portraits, symbolic items → Retratos, itens simbólicos
• Clean, geometric → Limpo, geométrico

Color psychology:

• Blues, grays, bold accents → Azuis, cinzas, acentos marcantes
• Warm yellows, whites, bright → Amarelos quentes, brancos, brilhantes
• Greens, oranges, energetic → Verdes, laranjas, enérgicos
• Warm, appetizing colors → Cores quentes e apetitosas
• Muted, respectful tones → Tons suaves, respeitosos
• Blues, grays, structured → Azuis, cinzas, estruturados

Key design elements:

• Professional, authoritative → Profissional, autoritário
• Optimism, transformation → Otimismo, transformação
• Action, wellness → Ação, bem-estar
• Freshness, indulgence → Frescor, indulgência
• Depth, significance → Profundidade, significado
• Credibility, seriousness → Credibilidade, seriedade

Let me format this properly in Portuguese.</think>

Convenções de Capas do Gênero Não-Ficção

Gênero	Elementos Visuais	Psicologia das Cores	Elementos de Design Principais
Empresarial	Símbolos abstratos de sucesso	Azuis, cinzas, acentos marcantes	Profissional, autoritário
Autoajuda	Movimento ascendente, luz	Amarelos quentes, brancos, brilhantes	Otimismo, transformação
Saúde/Fitness	Figuras ativas, vitalidade	Verdes, laranjas, enérgicos	Ação, bem-estar
Livros de Culinária	Fotografia de alimentos, ingredientes	Cores quentes e apetitosas	Frescor, indulgência
Biografia	Retratos, itens simbólicos	Tons suaves, respeitosos	Profundidade, significado
Acadêmico	Limpo, geométrico	Azuis, cinzas, estruturados	Credibilidade, seriedade

<think>The user wants me to translate an article fragment into Portuguese. However, I notice that the input only contains a single heading "## Book Cover Prompt Templates" with no actual content to translate. Let me translate what's there faithfully, following all the rules.

Since there's only a heading, I'll just translate that heading into Portuguese while keeping the markdown syntax intact.

"Book Cover Prompt Templates" → "Modelos de Prompt para Capa de Livro"

That seems like a natural Portuguese translation.</think>

Modelos de Prompt para Capa de Livro

<think>The user wants me to translate a blog fragment into Portuguese. This is about a "Fiction Cover Template" for generating book cover designs, likely for an AI image generation tool (GLMImage).

Let me carefully translate everything while preserving:

1. All markdown syntax
2. All URLs, image paths, HTML tags
3. Code blocks (untranslated, except comments)
4. Brand name "GLMImage" unchanged
5. Native, fluent Portuguese expression

The template is in English with placeholders like [Genre], [BOOK TITLE], etc. These are structural elements within code blocks, so I should keep the code block content as-is for the template structure, but translate the explanatory text and examples outside code blocks.

Wait, let me reconsider. The code blocks contain example prompts in English. The user says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." So I should NOT translate the content inside the code blocks.

So I'll:

• Translate headings, descriptions, and explanatory text into Portuguese
• Keep code blocks (the actual templates and examples) in English
• Keep all markdown formatting

Let me draft the translation:

Template de Capa de Ficção

[Genre] book cover design, title "[BOOK TITLE]" [Placement],
author "[AUTHOR NAME]" [Bottom Placement], [Visual Elements],
[Atmosphere/Mood], [Color Scheme], [Composition Style],
professional book cover, highly legible typography

Exemplos por Gênero:

Romance:

Contemporary romance book cover, title "HEARTS UNBOUND" centered
at top in elegant script font, author "SARAH MITCHELL" at bottom,
silhouette of couple embracing on beach at sunset, warm pink and
orange color scheme, romantic atmosphere, professional book
design, highly legible

Suspense:

Psychological thriller book cover, title "THE SILENT ROOM" at top
in bold distressed font, author "JAMES BLACKWOOD" at bottom,
lone figure standing in dark corridor with single light overhead,
deep blue and black color scheme with red accent, tense atmosphere,
professional thriller design, highly legible

Fantasia:

Epic fantasy book cover, title "CROWN OF DRAGONS" at top in
ornate metallic font, author "Elena Storme" at bottom, dragon
perched on mountain peak with lightning storm background, deep
purple and gold color scheme, epic scale, professional fantasy
design, highly legible

Let me refine this translation to be more natural and fluent in Portuguese:

"Thriller" in Portuguese is typically "Suspense" or "Thriller" (the word is often used as-is in Portuguese). Let me use "Suspense" as it's more native.

"Fiction Cover Template" -> "Modelo de Capa de Ficção" or "Template de Capa de Ficção"

Let me think about the best translations:

• "Fiction Cover Template" -> "Modelo de Capa para Ficção"
• "Examples by Genre" -> "Exemplos por Gênero"
• "Romance" -> "Romance" (same in Portuguese)
• "Thriller" -> "Suspense" or "Thriller"
• "Fantasy" -> "Fantasia"

I think I'll use:

• "Modelo de Capa de Ficção"
• "Exemplos por Gênero"
• "Romance"
• "Suspense" (more native than thriller)
• "Fantasia"

Let me finalize the translation.</think>

Modelo de Capa para Ficção

[Genre] book cover design, title "[BOOK TITLE]" [Placement],
author "[AUTHOR NAME]" [Bottom Placement], [Visual Elements],
[Atmosphere/Mood], [Color Scheme], [Composition Style],
professional book cover, highly legible typography

Exemplos por Gênero:

Romance:

Contemporary romance book cover, title "HEARTS UNBOUND" centered
at top in elegant script font, author "SARAH MITCHELL" at bottom,
silhouette of couple embracing on beach at sunset, warm pink and
orange color scheme, romantic atmosphere, professional book
design, highly legible

Suspense:

Psychological thriller book cover, title "THE SILENT ROOM" at top
in bold distressed font, author "JAMES BLACKWOOD" at bottom,
lone figure standing in dark corridor with single light overhead,
deep blue and black color scheme with red accent, tense atmosphere,
professional thriller design, highly legible

Fantasia:

Epic fantasy book cover, title "CROWN OF DRAGONS" at top in
ornate metallic font, author "Elena Storme" at bottom, dragon
perched on mountain peak with lightning storm background, deep
purple and gold color scheme, epic scale, professional fantasy
design, highly legible

<think>The user wants me to translate the article fragment into natural, fluent Portuguese. I need to keep all markdown syntax, URLs, code blocks, brand names, etc. intact. Let me translate this carefully.

The fragment is about a "Non-Fiction Cover Template" with examples for Business, Self-Help, and Cookbook genres.

I need to:

1. Translate headings and text naturally
2. Keep code blocks intact (they contain prompt templates - the user said "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)")
3. Wait - the code blocks here are prompt templates, not actual code. Let me re-read the rules.

Rule 3 says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So I should keep the code blocks untranslated. The code blocks contain template strings for image generation prompts - they're not code to be executed, but they are inside code fences. According to rule 3, I should keep them untranslated.

Let me translate the surrounding text into Portuguese while keeping code blocks intact.

Let me write the translation:

Modelo de Capa de Não-Ficção

[Non-Fiction Genre] book cover, title "[BOOK TITLE]" [Placement],
subtitle "[SUBTITLE]" smaller below, author "[AUTHOR NAME]"
[Placement], [Visual Style], [Color Scheme], professional
business book design, highly legible, modern aesthetic

Exemplos por Gênero:

Negócios:

Business book cover, title "LEADING THROUGH CHANGE" centered
in bold modern font, subtitle "Transform Your Organization" smaller
below, author "Michael Chen" at bottom, abstract upward arrow
design, navy blue and gold color scheme, professional business
design, highly legible

Autoajuda:

Self-help book cover, title "RISE ABOVE" at top in bold
uplifting font, subtitle "Overcoming Life's Obstacles" smaller
below, author "Dr. Lisa Park" at bottom, sunrise over mountain
peak image, warm yellow and orange color scheme, inspirational
atmosphere, professional design, highly legible

Livro de Receitas:

Cookbook cover, title "FRESH FROM ITALY" at top in elegant font,
subtitle "100 Authentic Regional Recipes" smaller below, author
"Marco Bellini" at bottom, rustic wooden table with fresh pasta
and ingredients, warm earth tones, inviting presentation,
professional cookbook design, highly legible

Wait, let me reconsider. The code blocks contain text that is English template content. The rules say to keep code blocks untranslated. So I will keep them as-is.

But wait - these "code blocks" appear to be template strings/prompts for AI image generation. They are inside code fences in markdown. According to rule 3, code blocks should be kept untranslated. So I'll keep them in English.

Let me finalize the Portuguese translation of the surrounding text:

"Non-Fiction Cover Template" → "Modelo de Capa de Não-Ficção"
"Examples by Genre" → "Exemplos por Gênero"
"Business" → "Negócios"
"Self-Help" → "Autoajuda"
"Cookbook" → "Livro de Receitas"

The code blocks themselves stay in English per the rules.

Let me double-check that I'm following all rules:

1. Keep ALL markdown syntax intact ✓
2. Keep every URL, image path, and HTML tag EXACTLY as-is - no URLs/tags here ✓
3. Keep code blocks untranslated ✓
4. Keep "GLMImage" untranslated - not mentioned in this fragment ✓
5. Use native, fluent expression ✓
6. Output ONLY translated markdown ✓</think>

Modelo de Capa de Não-Ficção

[Non-Fiction Genre] book cover, title "[BOOK TITLE]" [Placement],
subtitle "[SUBTITLE]" smaller below, author "[AUTHOR NAME]"
[Placement], [Visual Style], [Color Scheme], professional
business book design, highly legible, modern aesthetic

Exemplos por Gênero:

Negócios:

Business book cover, title "LEADING THROUGH CHANGE" centered
in bold modern font, subtitle "Transform Your Organization" smaller
below, author "Michael Chen" at bottom, abstract upward arrow
design, navy blue and gold color scheme, professional business
design, highly legible

Autoajuda:

Self-help book cover, title "RISE ABOVE" at top in bold
uplifting font, subtitle "Overcoming Life's Obstacles" smaller
below, author "Dr. Lisa Park" at bottom, sunrise over mountain
peak image, warm yellow and orange color scheme, inspirational
atmosphere, professional design, highly legible

Livro de Receitas:

Cookbook cover, title "FRESH FROM ITALY" at top in elegant font,
subtitle "100 Authentic Regional Recipes" smaller below, author
"Marco Bellini" at bottom, rustic wooden table with fresh pasta
and ingredients, warm earth tones, inviting presentation,
professional cookbook design, highly legible

<think>The user wants me to translate an article fragment into natural, fluent Portuguese. The fragment is just a heading: "## Series Cover Consistency"

I need to:

1. Keep the markdown syntax (## heading)
2. Translate it naturally into Portuguese
3. Not add any commentary or code fences around the output

"Series Cover Consistency" translates to "Consistência da Capa da Série" or "Consistência das Capas da Série" in Portuguese. Let me pick the most natural sounding one. "Consistência das Capas da Série" sounds natural and fluent.

Actually, since "Series Cover" could be interpreted as a compound noun (the cover of the series), I could also say "Consistência da Capa da Série" (singular) or "Consistência das Capas da Série" (plural, treating each cover as separate but related).

For a blog heading about keeping covers consistent across a series, "Consistência das Capas da Série" feels most natural as it implies consistency across multiple covers in a series.

Let me go with that.</think>

Consistência das Capas da Série

<think>The user wants me to translate a markdown table fragment into Portuguese while keeping all the markdown syntax, URLs, and brand names intact. Let me translate the content naturally into Portuguese.

The table is about maintaining series identity for GLMImage content. I need to translate:

• Heading: "Maintaining Series Identity" → "Mantendo a Identidade da Série"
• Table headers: Element, Strategy, Implementation → Elemento, Estratégia, Implementação
• Row content: Typography, Color palette, Layout, Style, Visual motif
• Content within each row

Let me translate this carefully while keeping the markdown table structure intact.</think>

Mantendo a Identidade da Série

Elemento	Estratégia	Implementação
Tipografia	Mesmas fontes em toda a série	Salvar prompts de fontes
Paleta de cores	Cores de destaque consistentes	Especificar cores exatas
Layout	Mesmo posicionamento de texto	Usar prompts de modelo
Estilo	Mesmo tratamento artístico	Salvar valores de seed
Motivo visual	Elementos recorrentes	Prompts baseados em tema

<think>The user wants me to translate an article fragment about series workflow for book covers into natural, fluent Portuguese. I need to keep all markdown syntax, URLs, image paths, HTML tags, code blocks, and the brand word "GLMImage" unchanged. Let me translate this carefully while keeping the structure intact.

The content is about a series workflow for book covers, including code blocks with templates and examples. I'll need to translate the prose and explanations but keep the code blocks intact (with comments possibly translated if safe).

Let me think about the Portuguese translation:

• "Series Workflow" = "Fluxo de Trabalho da Série"
• "Book 1: Establish base style → Save seed, prompt template" = "Livro 1: Estabelecer estilo base → Salvar seed, modelo de prompt"
• "Book 2: Use same seed, vary content only" = "Livro 2: Usar o mesmo seed, variar apenas o conteúdo"
• etc.

For the code blocks, I should keep them as-is since they contain specific instructions/values. The prompt templates have English text that needs to remain (since they're meant to be used in English prompts), but the explanatory text around them should be translated.

Let me translate carefully:</think>

Fluxo de Trabalho da Série

Livro 1: Estabelecer estilo base → Salvar seed, modelo de prompt
Livro 2: Usar o mesmo seed, variar apenas o conteúdo
Livro 3: Usar o mesmo seed, variar apenas o conteúdo
...
Box Set da Série: Combinar elementos com nova composição

Exemplo de Modelo para Série:

[Genre] series book cover, title "[BOOK TITLE - varies by book]"
centered at top, author "[AUTHOR NAME - consistent]" at bottom,
[Series Visual Motif - consistent], [Book-Specific Element - varies],
[Consistent Color Scheme], [Series Style Template], professional
book design, highly legible

Exemplo de Série de Fantasia:

Livro 1:

Epic fantasy book cover, title "AWAKENING" at top, author "K.R.
Morgan" at bottom, glowing sword embedded in stone, deep blue and
silver color scheme, professional fantasy design, seed: 12345

Livro 2 (mesmo seed, espada diferente):

Epic fantasy book cover, title "ASCENSION" at top, author "K.R.
Morgan" at bottom, glowing sword held aloft, deep blue and silver
color scheme, professional fantasy design, seed: 12345

<think>The user wants me to translate a fragment of an article about "Author Marketing Assets" into Portuguese. The fragment is very short - just a heading. I need to translate it naturally and fluently into Portuguese while keeping the markdown syntax intact.

"Author Marketing Assets" in Portuguese would be "Recursos de Marketing para Autores" or "Materiais de Marketing do Autor" or "Ativos de Marketing do Autor". I'll go with a natural-sounding translation.</think>

Recursos de Marketing para Autores

<think>The user wants me to translate an article fragment into Portuguese. Let me analyze the content:

1. It's a markdown table about "Author Platform Essentials"
2. Contains brand name "GLMImage" - but this fragment doesn't actually mention GLMImage
3. It's a table with assets, purposes, and prompt focuses
4. Need to keep markdown syntax intact
5. Translate naturally to Portuguese

Let me translate:

• "Author Platform Essentials" → "Essenciais da Plataforma do Autor"
• "Asset" → "Ativo" or "Recurso"
• "Purpose" → "Propósito" or "Finalidade"
• "Prompt Focus" → "Foco do Prompt"
• "Author headshot" → "Foto profissional do autor"
• "Website, speaking, media" → "Site, palestras, mídia"
• "Professional, approachable" → "Profissional, acessível"
• "Author banner" → "Banner do autor"
• "social media headers" → "cabeçalhos de redes sociais"
• "Brand consistency" → "Consistência da marca"
• "Book teaser graphics" → "Gráficos de teaser do livro"
• "Pre-launch promotion" → "Promoção pré-lançamento"
• "Mood, intrigue" → "Clima, intriga"
• "Launch graphics" → "Gráficos de lançamento"
• "Release day announcements" → "Anúncios do dia de lançamento"
• "Celebration, availability" → "Celebração, disponibilidade"
• "Quote graphics" → "Gráficos de citações"
• "Review excerpts" → "Trechos de resenhas"
• "Legibility, branding" → "Legibilidade, identidade visual"

Let me format this properly.</think>

Essenciais da Plataforma do Autor

Ativo	Finalidade	Foco do Prompt
Foto profissional do autor	Site, palestras, mídia	Profissional, acessível
Banner do autor	cabeçalhos de redes sociais	Consistência da marca
Gráficos de teaser do livro	Promoção pré-lançamento	Clima, intriga
Gráficos de lançamento	Anúncios do dia de lançamento	Celebração, disponibilidade
Gráficos de citações	Trechos de resenhas	Legibilidade, identidade visual

<think>The user wants me to translate the article fragment into natural, fluent Portuguese. Let me carefully translate this while maintaining all markdown syntax, code blocks, and the brand name "GLMImage" untranslated.

The fragment is about an "Author Headshot Prompt" with a template and an example. Let me translate it:

• "Author Headshot Prompt" → "Prompt para Retrato de Autor" or "Prompt de Retrato do Autor"
• The template variables like [gender], [age range], etc. should stay as placeholders but I should translate the surrounding text
• The example should be translated to Portuguese

Let me write this in natural Brazilian Portuguese.</think>

Prompt para Retrato do Autor

Professional author headshot, [gender] in [age range], [appearance
description], [clothing style], [background], [lighting],
professional photography style, approachable and authentic,
author photo for book promotion

Exemplo:

Professional author headshot, female author in her 40s, warm smile,
glasses, wearing casual blazer, neutral background with subtle
books, soft studio lighting, professional photography style,
approachable and authentic, author photo for book promotion

<think>The user wants me to translate an article fragment about Social Media Banner Prompts into Portuguese. I need to keep all markdown syntax intact, keep URLs/HTML tags as-is, keep code blocks untranslated, keep "GLMImage" untranslated, and use natural Portuguese.

Let me translate this carefully:

• "Social Media Banner Prompt" → "Prompt para Banner de Mídia Social"
• The code blocks should remain as code (the prompt template)
• "Author" → "Autor(a)" or just keep "Author" - actually in Portuguese, "Author" would be translated in the description but kept in code blocks. Let me think... The instruction says "Keep code blocks and inline code untranslated" - so the entire code block stays in English.

Let me translate the surrounding text:

"Author social media banner" - this is inside code block, keep as is
"[Platform] header dimensions" - inside code block
"[Author Name]" - inside code block
"[Books/Genre] represented" - inside code block
"[Color Scheme]" - inside code block
"[Style Keywords]" - inside code block
"professional author branding" - inside code block
"space for profile picture" - inside code block

"Example (Twitter/X)" - "Exemplo (Twitter/X)"

The example code block content stays as is.

Let me write the translation now.</think>

Prompt para Banner de Mídia Social

Author social media banner, [Platform] header dimensions, [Author
Name] prominent or subtle, [Books/Genre] represented, [Color
Scheme], [Style Keywords], professional author branding, space
for profile picture

Exemplo (Twitter/X):

Author Twitter banner, 1500x500 dimensions, "Sarah Mitchell
Romance Author" text in elegant font, book cover silhouettes
arranged across banner, soft pink and cream color scheme, romantic
author branding, space for profile picture on left

<think>The user wants me to translate a fragment of an article into Portuguese. The fragment is just a heading: "## Pre-Launch Marketing Campaign"

I need to translate this into natural, fluent Portuguese while keeping the markdown syntax intact.

"Pre-Launch Marketing Campaign" in Portuguese would be "Campanha de Marketing Pré-Lançamento" or "Campanha de Marketing de Pré-Lançamento".

A more natural phrasing in Portuguese would be "Campanha de Marketing Pré-Lançamento" or simply "Campanha de Marketing Antes do Lançamento".

Let me go with "Campanha de Marketing Pré-Lançamento" as it's concise and natural.</think>

Campanha de Marketing Pré-Lançamento

<think>The user wants me to translate the article fragment into Portuguese while keeping all markdown syntax intact. Let me translate the table headers and content into natural Portuguese.

• Timeline = Cronograma
• Assets = Ativos/Recursos
• Asset Type = Tipo de Recurso
• Purpose = Objetivo/Finalidade

Let me translate the table:

Timing	Asset Type	Purpose
3 months pre	Cover reveal teaser	Generate buzz
2 months pre	Character art	Build interest
1 month pre	Quote graphics	Social proof
2 weeks pre	Countdown graphics	Urgency
Launch week	Celebration graphics	Availability
Post-launch	Review graphics	Ongoing promotion

Portuguese translation:

Momento	Tipo de Recurso	Objetivo
3 meses antes	Teaser de revelação da capa	Gerar expectativa
2 meses antes	Arte dos personagens	Criar interesse
1 mês antes	Gráficos de citações	Prova social
2 semanas antes	Gráficos de contagem regressiva	Urgência
Semana de lançamento	Gráficos de celebração	Disponibilidade
Pós-lançamento	Gráficos de resenhas	Promoção contínua

Also need to translate the heading "Timeline and Assets" to "Cronograma e Recursos".

Let me make sure this is fluent and natural Portuguese.</think>

Cronograma e Recursos

Momento	Tipo de Recurso	Objetivo
3 meses antes	Teaser de revelação da capa	Gerar expectativa
2 meses antes	Arte dos personagens	Despertar interesse
1 mês antes	Gráficos de citações	Prova social
2 semanas antes	Gráficos de contagem regressiva	Urgência
Semana de lançamento	Gráficos de celebração	Disponibilidade
Pós-lançamento	Gráficos de resenhas	Promoção contínua

<think>The user wants me to translate an article fragment about a "Cover Reveal Prompt" into Portuguese. The fragment contains a markdown heading and a code block. I need to:

1. Translate the heading "Cover Reveal Prompt" into Portuguese
2. Keep the code block content untranslated (it's a prompt template)
3. Keep all markdown syntax intact
4. The brand "GLMImage" doesn't appear here but I should be ready to keep it

Let me think about the translation:

• "Cover Reveal Prompt" → "Prompt de Revelação de Capa" or "Prompt para Revelação de Capa"

The code block content should remain untranslated as per the rules.

Let me provide the translation.</think>

Prompt de Revelação de Capa

Book cover reveal promotional graphic, "[BOOK TITLE]" by
[Author Name], cover image [description], "COMING SOON [Date]"
text, [Genre] style, [Color Scheme], promotional announcement
style, highly legible, excitement and anticipation

<think>The user wants me to translate a fragment of an article into Portuguese. The fragment is just a heading "## International & Translation Editions". I need to translate this into natural, fluent Portuguese while keeping all markdown syntax intact.

The translation would be something like "## Edições Internacionais e de Tradução" or "## Edições Internacionais & Traduções".

Let me keep it natural and fluent in Portuguese.</think>

Edições Internacionais e de Tradução

<think>The user wants me to translate an article fragment into Portuguese. The fragment is about a "Multi-Language Cover Strategy" with a table containing market considerations and GLMImage advantages. I need to:

1. Keep ALL markdown syntax intact
2. Keep URLs, image paths, HTML tags as-is
3. Keep code blocks untranslated
4. Keep "GLMImage" untranslated
5. Use natural, fluent Portuguese
6. Output ONLY the translated markdown

Let me translate the content:

• "Multi-Language Cover Strategy" → "Estratégia de Capas Multilíngues"
• "Market" → "Mercado"
• "Considerations" → "Considerações"
• "GLMImage Advantage" → "Vantagem do GLMImage"
• "Chinese editions" → "Edições em chinês"
• "Title translation, cultural elements" → "Tradução de título, elementos culturais"
• "90% Chinese text accuracy" → "90% de precisão em texto em chinês"
• "Spanish editions" → "Edições em espanhol"
• "Title length, accent marks" → "Extensão do título, sinais diacríticos"
• "95% text rendering" → "95% de renderização de texto"
• "Bilingual covers" → "Capas bilíngues"
• "Dual text layout" → "Layout com texto duplo"
• "85% bilingual accuracy" → "85% de precisão bilíngue"
• "Asian markets" → "Mercados asiáticos"
• "Character rendering, typography" → "Renderização de caracteres, tipografia"
• "Native training data" → "Dados de treinamento nativos"

Let me format the table properly in Portuguese.</think>

Estratégia de Capas Multilíngues

Mercado	Considerações	Vantagem do GLMImage
Edições em chinês	Tradução do título, elementos culturais	90% de precisão em texto em chinês
Edições em espanhol	Extensão do título, sinais diacríticos	95% de renderização de texto
Capas bilíngues	Layout com texto duplo	85% de precisão bilíngue
Mercados asiáticos	Renderização de caracteres, tipografia	Dados de treinamento nativos

<think>The user wants me to translate an article fragment into Portuguese. Let me translate this carefully, keeping all markdown syntax, URLs, code blocks, and the brand "GLMImage" intact.</think>

Prompt de Capa Bilíngue

[Genre] book cover with bilingual text, English "[ENGLISH TITLE]"
at top, [Language] "[TRANSLATED TITLE]" below with equal
prominence, author "[AUTHOR NAME]" at bottom, [Visual Elements],
[Color Scheme], highly legible for both languages, professional
bilingual book cover design

Exemplo:

Fantasy book cover with bilingual text, English "DRAGON'S PATH"
at top, Chinese "龙之路" below with equal prominence, author
"Chen Wei" at bottom, dragon flying over mountains, gold and
deep blue color scheme, highly legible for both languages,
professional bilingual book cover

<think>The user wants me to translate a small fragment into Portuguese. The fragment is just a heading: "## Cover Design Technical Specifications". I need to keep the markdown syntax intact and translate the content naturally into Portuguese.

"Cover Design Technical Specifications" = "Especificações Técnicas do Design da Capa" or "Especificações Técnicas do Design de Capa"

Let me keep it natural and fluent in Portuguese.</think>

Especificações Técnicas do Design da Capa

<think>The user wants me to translate the article fragment into natural, fluent Portuguese. Let me translate this table and heading carefully, keeping all the markdown syntax intact.

The heading "Print vs Digital Specifications" should be translated to Portuguese.
The table headers and content should be translated but keeping the markdown formatting.

Let me translate:

• "Print vs Digital Specifications" → "Especificações de Impressão vs Digital"
• "Format" → "Formato"
• "Resolution" → "Resolução"
• "Color Mode" → "Modo de Cor"
• "Bleed Area" → "Área de Sangria"
• "Print paperback" → "Brochura impressa" (or "Livro de bolso impresso")
• "Print hardcover" → "Capa dura impressa"
• "eBook standard" → "eBook padrão"
• "Audiobook cover" → "Capa de audiolivro"
• "DPI" stays as DPI (or "PPP" in Portuguese, but DPI is commonly used)
• "CMYK" stays as CMYK
• "RGB" stays as RGB
• "0.125" minimum" → "0.125" mínimo"
• "0.25" minimum" → "0.25" mínimo"
• "1563px tall" → "1563px de altura"
• "3000px minimum" → "3000px mínimo"
• "None" → "Nenhuma"

Let me format this properly.</think>

Especificações de Impressão vs Digital

Formato	Resolução	Modo de Cor	Área de Sangria
Brochura impressa	300 DPI	CMYK	0.125" mínimo
Capa dura impressa	300 DPI	CMYK	0.25" mínimo
eBook padrão	1563px de altura	RGB	Nenhuma
Capa de audiolivro	3000px mínimo	RGB	Nenhuma

<think>The user wants me to translate a markdown table fragment about platform-specific requirements for book covers into Portuguese. I need to:

1. Keep ALL markdown syntax intact (the table structure)
2. Keep URLs, image paths, and HTML tags exactly as-is (none here)
3. Keep code blocks untranslated (none here)
4. Keep "GLMImage" untranslated
5. Use native, fluent Portuguese
6. Output only the translated markdown

Let me translate the table:

• Platform-Specific Requirements = Requisitos Específicos da Plataforma
• Platform = Plataforma
• Dimensions = Dimensões
• File Type = Tipo de Arquivo
• Restrictions = Restrições
• Amazon Kindle - keep as is (brand)
• recommended = recomendado
• JPG/JPEG - keep as is (file format)
• No text on spine simulation = Sem texto na simulação de lombada
• Apple Books - keep as is (brand)
• minimum = mínimo
• PNG/JPG - keep as is
• High contrast required = Alto contraste necessário
• Kobo - keep as is (brand)
• RGB color space = Espaço de cores RGB
• Google Play - keep as is (brand)
• No text wrap = Sem quebra de texto
• Audible - keep as is (brand)
• Author name required = Nome do autor obrigatório

Let me format this properly as a markdown table.</think>

Requisitos Específicos da Plataforma

Plataforma	Dimensões	Tipo de Arquivo	Restrições
Amazon Kindle	2560x1600 recomendado	JPG/JPEG	Sem texto na simulação de lombada
Apple Books	1400x2100 mínimo	PNG/JPG	Alto contraste necessário
Kobo	1800x2700 recomendado	JPG	Espaço de cores RGB
Google Play	2048x2048 recomendado	PNG/JPG	Sem quebra de texto
Audible	3000x3000 mínimo	JPG	Nome do autor obrigatório

<think>The user wants me to translate an article fragment about "Text Typography Best Practices" from English to Portuguese. However, looking at the input, I only see the heading "## Text Typography Best Practices" - there doesn't appear to be any body text or content below it.

Since the instruction says to translate the fragment completely and not summarize or shorten, but there's only a heading here, I should translate just the heading. Let me translate it naturally to Portuguese.

"Text Typography Best Practices" → "Melhores Práticas de Tipografia de Texto" or "Melhores Práticas de Tipografia para Texto"

I'll go with "Melhores Práticas de Tipografia de Texto" which is natural and fluent in Portuguese.</think>

Melhores Práticas de Tipografia de Texto

<think>The user wants me to translate the article fragment about font selection by genre into Portuguese. I need to:

1. Keep the markdown table structure intact
2. Keep the headers and formatting
3. Translate the content naturally into Portuguese
4. Keep the brand "GLMImage" untranslated (though it doesn't appear here)

Let me translate each element:

• Title: "Font Selection by Genre" → "Seleção de Fontes por Gênero"
• "Genre" → "Gênero"
• "Font Style" → "Estilo da Fonte"
• "Rationale" → "Justificativa"
• "Romance" → "Romance"
• "Elegant, script, serif" → "Elegante, script, serif"
• "Feminine, emotional" → "Feminino, emocional"
• "Thriller" → "Thriller" (or "Suspense")
• "Bold, distressed, sans-serif" → "Negrito, desgastado, sem serifa"
• "Tension, impact" → "Tensão, impacto"
• "Fantasy" → "Fantasia"
• "Ornate, metallic, decorative" → "Ornamentada, metálica, decorativa"
• "Magical, epic" → "Mágico, épico"
• "Sci-Fi" → "Ficção Científica"
• "Clean, futuristic, geometric" → "Limpa, futurista, geométrica"
• "Technological" → "Tecnológico"
• "Literary" → "Literário"
• "Minimalist, sophisticated" → "Minimalista, sofisticada"
• "Refined, subtle" → "Refinado, sutil"
• "Children's" → "Infantil"
• "Playful, rounded, friendly" → "Divertida, arredondada, amigável"
• "Approachable, fun" → "Acessível, divertida"

Let me format this properly.</think>

Seleção de Fontes por Gênero

Gênero	Estilo da Fonte	Justificativa
Romance	Elegante, script, serif	Feminino, emocional
Suspense	Negrito, desgastada, sem serifa	Tensão, impacto
Fantasia	Ornamentada, metálica, decorativa	Mágico, épico
Ficção Científica	Limpa, futurista, geométrica	Tecnológico
Literário	Minimalista, sofisticada	Refinado, sutil
Infantil	Divertida, arredondada, amigável	Acessível, divertida

<think>The user wants me to translate an article fragment about "Title Hierarchy Prompt Structure" into Portuguese. Let me translate this naturally and fluently while keeping all markdown syntax, code blocks, and formatting intact.

The content is about prompt structure for book cover design with title hierarchy. I need to translate:

• "Title Hierarchy Prompt Structure" → "Estrutura de Prompt para Hierarquia de Títulos"
• Keep the code blocks intact (they're in English as they're examples of prompts)
• Keep the markdown structure

Let me translate the prose parts while keeping the code blocks exactly as they are.</think>

Estrutura de Prompt para Hierarquia de Títulos

Book cover with clear title hierarchy: main title "[TITLE]" [Size
and Placement], subtitle [smaller below], author name [Placement
and Size], [Font Descriptions], [Color Scheme], professional
typography, highly legible

Exemplo:

Book cover with clear title hierarchy: main title "THE ART OF
WRITING" large and centered at top, subtitle "A Complete Guide
to Craft and Career" smaller below, author "Jane Smith" elegant
at bottom, main title in bold serif font, subtitle in lighter
weight serif, author name in script accent, navy and gold color
scheme, professional typography, highly legible

<think>The user wants me to translate a fragment of an article into Portuguese. The fragment is very short - just a heading "## Interior Illustrations". I need to keep all markdown syntax intact, keep "GLMImage" untranslated, and output only the translated markdown.

"Interior Illustrations" translates to "Ilustrações Interiores" in Portuguese.</think>

Ilustrações Interiores

<think>The user wants me to translate an article fragment about Chapter Header Illustrations into natural, fluent Portuguese. I need to keep all markdown syntax intact, keep URLs/HTML tags as-is, keep code blocks untranslated (only translate comments when trivially safe), keep "GLMImage" untranslated, and use native fluent expression.

Let me translate this carefully:

• "Chapter Header Illustrations" → "Ilustrações de Cabeçalho de Capítulo"
• The prompt template needs to stay in English since it's a code block
• The example inside the code block should also stay untranslated
• "Example" → "Exemplo"
• The translated text outside the code block should be in Portuguese

Let me look at what needs translating:

• "### Chapter Header Illustrations" → "### Ilustrações de Cabeçalho de Capítulo"
• The code block content (the template and example) should remain untranslated as it's code
• "Example:" → "Exemplo:"

Wait, let me reconsider. The code block contains a prompt template with [Genre], [Theme/Motif...], etc. These are placeholder fields. Should I translate the text inside the code block?

The rules say:
3. Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe).

So I should NOT translate the contents of the code block. The code block is the prompt template with placeholders. I should leave it as-is.

The "Example:" label is outside the code block, so I should translate it to "Exemplo:"

Let me write this out:</think>

Ilustrações de Cabeçalho de Capítulo

[Genre] chapter header illustration, [Theme/Motif related to
chapter content], [Style Keywords], [Color Palette], decorative
border element, space for chapter number and title, book interior
illustration style

Exemplo:

Fantasy chapter header illustration, ornate dragon silhouette
curving around text area, Celtic knotwork border, deep blue and
gold color scheme, decorative border element, space for chapter
number and title, book interior illustration style

<think>The user wants me to translate an article fragment about Scene Illustrations into Portuguese. The fragment contains a code block with a prompt template. I need to keep the markdown syntax intact, keep the code block untranslated (but translate comments if trivially safe), keep URLs/image paths/HTML tags as-is, keep "GLMImage" untranslated, and output only the translated markdown.

Let me translate this fragment:

The heading "Scene Illustrations" translates to "Ilustrações de Cenas" in Portuguese.

The code block content should remain untranslated as it's a prompt template. But there are bracketed placeholders like [Genre], [Scene Description from book], [Atmospheric Lighting], [Composition Style]. These are English placeholders that would typically be kept as-is in technical prompts, but the user said to keep code blocks untranslated. So I'll keep the code block exactly as-is.

Wait, let me re-read the rules: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So the code block stays in English. The text outside the code block is just the heading "Scene Illustrations".

Translation of heading: "Ilustrações de Cenas"

That's pretty much it for this fragment. Let me output just the translated markdown.</think>

Ilustrações de Cenas

[Genre] interior illustration, [Scene Description from book],
[Atmospheric Lighting], [Composition Style], matching book
cover aesthetic, interior illustration style, textural detail

<think>The user wants me to translate an article fragment about common cover design mistakes into Portuguese. However, the only content provided is the heading "## Common Cover Design Mistakes" - there's no actual article fragment content to translate.

Let me re-read the prompt carefully...

The user says "Translate the article fragment into natural, fluent Portuguese." but only provides a heading "## Common Cover Design Mistakes". This appears to be just a heading with no body text.

I should translate what's provided. The heading translates to "## Erros Comuns de Design de Capa" in Portuguese.

Since there's no other content, I'll just output the translated heading. The instructions say to keep markdown syntax intact, so I'll keep the ## heading syntax.</think>

Erros Comuns de Design de Capa

<think>The user wants me to translate a table about mistakes to avoid when using GLMImage. Let me translate this into natural, fluent Portuguese while keeping all markdown syntax intact.</think>

Erros a Evitar

Erro	Por que falha	Solução
Imagens genéricas de banco de fotos	Não se destacam	Descrições personalizadas
Legibilidade de texto ruim	Aparência amadora	Palavra-chave "altamente legível"
Sinais de gênero incorretos	Confunde os leitores	Pesquisar convenções do gênero
Composição poluída	Visual de amador	"Limpo, minimalista"
Identidade visual inconsistente	Autoria enfraquecida	Modelos de série
Texto pequeno	Miniatura ilegível	"Texto grande e em negrito"

<think>The user wants me to translate this article fragment from English to Portuguese. Let me translate it naturally while keeping all markdown syntax, code blocks, and formatting intact.

The fragment is about a "Fix-It Workflow" for some kind of design process (likely for GLMImage based on the context). Let me translate it:

• "Fix-It Workflow" → "Fluxo de Trabalho de Correção"
• "Generate → Review at thumbnail size → Identify issues →" → "Gerar → Revisar em tamanho miniatura → Identificar problemas →"
• "Refine with specific fix prompt → Re-evaluate" → "Refinar com prompt de correção específico → Reavaliar"
• "Fix Prompt Template" → "Modelo de Prompt de Correção"
• "Previous cover design, [Issue Description], [Desired Fix]," → "Design de capa anterior, [Descrição do Problema], [Correção Desejada],"
• "maintain [Elements to Keep], improve [Specific Problem]," → "manter [Elementos a Manter], melhorar [Problema Específico],"
• "professional refinement" → "refinamento profissional"

I need to keep the code blocks intact (not translate inside code blocks, except for comments which are trivially safe - but here there are no comments, just the structure). The instructions say "translate only comments inside them when trivially safe" - since there are no comments here, I'll keep the code blocks exactly as they are.

Wait, actually the code blocks contain English text that's part of the template. The rule says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." So I should keep the code blocks exactly as they are in English.

Let me reconsider - the code blocks contain template text like "Previous cover design, [Issue Description]..." - these aren't code in the programming sense, they're template strings. But the rule is clear: keep code blocks untranslated. So I'll keep them in English.

Hmm, but the template content is meant to be filled in by users. It's a prompt template. Let me think about this more carefully.

The rule says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." This is a strict rule. So code blocks stay as-is.

But actually, looking at the content, these are not really code blocks - they're template strings presented in code formatting for clarity. However, since they're in code fences, I'll follow the rule and keep them untranslated.

Actually, wait. Let me reconsider. The rule says keep code blocks untranslated. But the template content like "Previous cover design, [Issue Description]" is instructional content, not actual code. However, the strict rule says to keep code blocks untranslated.

I'll keep the code blocks as-is to be safe with the rules. The translated text outside the code blocks will explain the workflow in Portuguese.

Let me write the output now.</think>

Fluxo de Trabalho de Correção

Generate → Review at thumbnail size → Identify issues →
Refine with specific fix prompt → Re-evaluate

Modelo de Prompt de Correção:

Previous cover design, [Issue Description], [Desired Fix],
maintain [Elements to Keep], improve [Specific Problem],
professional refinement

<think>The user is asking me to translate an article fragment from English to Portuguese. The fragment is just a heading: "## Budget Breakdown: Traditional vs AI"

I need to translate this to natural, fluent Portuguese while keeping the markdown syntax intact (the ## heading).

A good translation would be: "## Orçamento: Tradicional vs IA" or "## Análise de Custos: Tradicional vs IA"

Let me think about which sounds more natural in Portuguese. "Análise de Custos" sounds more professional and natural for a budget breakdown heading. "Análise Orçamentária" could also work.

I'll go with "## Análise Orçamentária: Tradicional vs IA" as it sounds the most natural and professional in Portuguese.</think>

Análise Orçamentária: Tradicional vs IA

<think>The user wants me to translate the article fragment into natural, fluent Portuguese. Let me translate the table content while keeping all markdown syntax intact.

The table is about cost comparison per cover between Traditional and AI services.

Let me translate each part:

• "Cost Comparison per Cover" → "Comparação de Custo por Capa"
• "Service" → "Serviço"
• "Traditional Cost" → "Custo Tradicional"
• "AI Cost" → "Custo com IA"
• "Savings" → "Economia"
• "Cover concept" → "Conceito da capa"
• "Design iterations" → "Iterações de design"
• "Typography work" → "Trabalho de tipografia"
• "Final preparation" → "Preparação final"
• "Total per cover" → "Total por capa"
• "each" → "cada"
• "100%" stays as "100%"
• "97-100%" stays as "97-100%"
• "$100-300" etc. stay as currency values

Let me format this properly in Portuguese.</think>

Comparação de Custo por Capa

Serviço	Custo Tradicional	Custo com IA	Economia
Conceito da capa	$100-300	$0	100%
Iterações de design	$50-150 cada	$0	100%
Trabalho de tipografia	$50-200	$0	100%
Preparação final	$50-150	$0	100%
Total por capa	$300-1500	$0-10	97-100%

<think>The user wants me to translate an article fragment into Portuguese. Let me analyze what needs to be translated:

1. The heading "Series Production Costs" - translate to Portuguese
2. The table headers: "Project", "Traditional", "AI-Assisted", "Savings" - translate to Portuguese
3. The table content - translate the numbers and percentages as needed
4. The link text "Create your book cover with AI →" - translate to Portuguese
5. Keep all URLs and paths intact
6. Keep "GLMImage" untranslated

Let me translate:

• "Series Production Costs" → "Custos de Produção de Série"
• "Project" → "Projeto"
• "Traditional" → "Tradicional"
• "AI-Assisted" → "Com Assistência de IA" or "Assistido por IA"
• "Savings" → "Economia" or "Poupança"
• "3-book series" → "Série de 3 livros"
• "5-book series" → "Série de 5 livros"
• "10-book series" → "Série de 10 livros"
• "Create your book cover with AI →" → "Crie sua capa de livro com IA →"

Let me format this properly in markdown.</think>

Custos de Produção de Série

Projeto	Tradicional	Assistido por IA	Economia
Série de 3 livros	$900-4500	$0-30	97-100%
Série de 5 livros	$1500-7500	$0-50	97-100%
Série de 10 livros	$3000-15000	$0-100	97-100%

[Crie sua capa de livro com IA →](/general/image-generation/book-cover-generator)
[Crie sua capa de livro com IA →](/general/image-generation/book-cover-generator)
[Crie sua capa de livro com IA →](/general/image-generation/book-cover-generator)

<think>The user wants me to translate a fragment of an article into natural, fluent Portuguese. The fragment is a FAQ section about AI book covers using GLMImage. I need to:

1. Keep ALL markdown syntax intact
2. Keep URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent expression
6. Output ONLY the translated markdown

Let me translate the FAQ section carefully into natural Brazilian Portuguese.</think>

Perguntas Frequentes

Quanto custa uma capa de livro feita com IA?
Uma assinatura do GLMImage de $9,90-$79,90 cobre um mês de gerações, então uma capa custa poucos dólares em vez dos $300-$1,500 cobrados por um designer. Reserve um valor extra caso contrate um designer para o polimento final.

Posso publicar um livro com uma capa gerada por IA?
Sim. A Amazon KDP pede que você informe o uso de conteúdo gerado por IA no momento da publicação, e a capa ainda precisa atender aos padrões normais de qualidade.

Uma capa feita com IA vai parecer igual à de todo mundo?
Só se você usar prompts vagos. As convenções de gênero são compartilhadas, mas as escolhas de composição e detalhes vêm do seu prompt — itere até que a capa seja sua.

Que texto a capa deve incluir?
Título, subtítulo (se houver) e nome do autor — entre aspas no prompt, com indicação de posicionamento. O GLM-Image renderiza esses textos com precisão, incluindo chinês para edições traduzidas.

<think>The user wants me to translate a fragment into Portuguese. This appears to be a "Sources" section from an article, with a heading and a list of links with URLs and anchor text. I need to:

1. Translate the heading "Sources" to Portuguese - "Fontes" or "Referências"
2. Keep all markdown syntax intact
3. Keep all URLs and link anchor text structure, but translate the displayed text where appropriate
4. Keep "GLMImage" untranslated (though it doesn't appear here)

Let me translate:

• "Sources" → "Fontes" (or "Referências")
• "Publishing Industry Report 2026" → "Relatório da Indústria Editorial 2026"
• "AI Book Cover Generator Guide" → "Guia de Gerador de Capas de Livros com IA"
• "Best AI for Text Rendering" → "Melhor IA para Renderização de Texto"
• "AI Poster Design Generator" → "Gerador de Design de Cartazes com IA"
• "Commercial AI Image Rights" → "Direitos de Imagens de IA Comerciais"

The URLs and paths should remain exactly as they are.</think>

Fontes

• Relatório da Indústria Editorial 2026
• Guia de Gerador de Capas de Livros com IA
• Melhor IA para Renderização de Texto
• Gerador de Design de Cartazes com IA
• Direitos de Imagens de IA Comerciais