You are writing a web design/development tutorial article (for Webflow, Framer, or general web topics) using the BRIX Templates Article Prompt v1.5.

ARTICLE TOPIC: [INSERT_TOPIC][INSERT_CONTEXT]

REFERENCE DOCUMENTS:
You have access to three research documents and one strategic direction document. Reference them as needed, but strictly follow the Article Prompt v1.5.

[ARTICLE FOCUS DIRECTION]
Our content strategist has analyzed the topic and identified a strategic direction the article **may** take. This is guidance to inform your approach, but the article must still comprehensively cover the full topic based on the research documents below.

[INSERT_ARTICLE_FOCUS]

**Important:** The Article Focus is strategic guidance, not a constraint. Your article must:
- Cover ALL relevant aspects found in the research documents
- Address ALL user pain points from Community Insights
- Answer relevant questions from SEO Questions research
- Include ALL technical details and steps from Research Technical Details
- Use the Article Focus to enhance depth and angle, not to narrow scope

[RESEARCH TECHNICAL DETAILS]
[INSERT_RESEARCH_TOPIC]

[RESEARCH COMMUNITY INSIGHTS]
[INSERT_COMMUNITY_INTEL]

[RESEARCH SEARCH QUERIES]
[INSERT_SEO_QUESTIONS]

[ARTICLE PROMPT]
# Web Design/Development Tutorial Article Generation Prompt
- Prompt Version 1.5

Create a comprehensive, actionable tutorial about [SPECIFIC TOPIC] (Webflow, Framer, or general web design/development) that follows BRIX Templates' style. The specific topic will be provided separately in another part of the prompt. The **research documents will guide what the article should cover**, but you must **strictly follow the BRIX Templates tone and writing style** while significantly improving its structure, clarity, and actionability.

## Article Structure

[HEADER]
# How to [action/task] in/on [Platform]
(Use the relevant platform: Webflow, Framer, or omit if general web topic)
(Examples: "How to setup Google Ads conversion tracking on Webflow sites", "How to block countries from accessing your Framer site")

Start with a compelling problem statement that resonates with users of the relevant platform/technology. Identify a specific challenge they face and why solving it matters. Make this opening immediately connect with the reader's pain points to create engagement from the first sentence.

## Introduction
- Define the problem/challenge in 1-2 sentences
- Explain why this solution is valuable for users (1-2 sentences)
- Briefly outline what the reader will learn (1 sentence)
- Include a transition to the main content

## Why [feature/solution] matters for [platform] sites/projects
- Create 4-6 bullet points highlighting specific use cases
- For these use cases, follow this format: **[Use case title]**: Brief explanation with practical example
- Ensure each use case directly relates to a common user challenge for the platform/technology
- When describing features, benefits, or similar structured information, use the format: **Bold title or category**: Followed by the explanation or details
- Use concrete, specific language rather than generic corporate phrasing
- Focus on tangible benefits and outcomes, not abstract concepts

## Main Content Sections
- Organize content in logical sections that flow from preparation to implementation
- Use numbered headings for sequential processes (if appropriate)
- Begin with necessary preparation or setup
- Always include 1-2 introductory sentences after each H2 heading before adding H3 subheadings
- Include the platform name (Webflow, Framer, etc.) in ALL section headings (both H2 and H3) for SEO optimization when relevant
- For each major step:
  - Break into numbered sub-steps where appropriate
  - Avoid deeply nested bullets; use flat sequential numbering with clear step labels instead
  - **Bold all UI elements, button names, and field names**
  - Include tip boxes after complex steps
  - Include any code snippets in proper code blocks
  - Where relevant, provide a concrete, specific example of the solution in action to help readers better understand implementation

## Troubleshooting Section
- Format as a bullet list with bolded problem statements
- For each issue, provide specific solution steps
- Include verification steps to confirm the fix worked
- Add troubleshooting items specific to the topic/integration at hand
- Bold specific error messages or common issues

## Frequently Asked Questions about [TOPIC] in [Platform]
- Create exactly 10 SEO-optimized, top-of-funnel (TOFU) questions that address common searches related to the topic
- Format each question as an H3 subheading that begins with interrogative words (What, Why, How, Which, Is, Can, etc.)
- Always include the platform name (Webflow, Framer, etc.) and relevant keywords in each question when relevant
- Questions should follow natural search patterns and represent what beginners would ask
- Include these question types:
  * 2-3 definition/explanation questions (What is X in [Platform]? Why do I need X?)
  * 2-3 comparison questions (What's the difference between X and Y? Is X better than Y for [Platform]?)
  * 2-3 implementation questions (How do I implement X? What are the steps to set up X?)
  * 2 best practice questions (What are the best practices for X? Which X solution works best?)
  Keep in mind these are just EXAMPLES, and you must deeply reflect about what topics are typically searched for on this specific article, and write the FAQs about that. We must not add generic questions, but questions people indeed search.
- For each answer:
  * Keep answers concise (100-150 words)
  * Write in a direct, informative style
  * Include at least one specific, actionable tip in each answer
  * When appropriate, reference and link to relevant sections within the main article
  * Include exactly one relevant keyword 1-2 times naturally within each answer
  * Avoid repeating information verbatim from other parts of the article
  * End with a definitive statement or recommendation

## Conclusion
- Summarize the key benefits of implementing this solution (2-3 sentences)
- Mention potential next steps or advanced options
- Include a subtle reference to BRIX Templates' agency services in the final paragraph
- Add a link to the agency page using natural anchor text

## Meta Information
[META TITLE OPTIONS]
Create exactly 10 title options (55-60 characters each) that are SEO-optimized with variety:
- All titles must use sentence case (only capitalize first word and proper nouns)
- All titles must explicitly include the primary keywords (e.g., platform name and relevant feature)
- Include at least one "How to" format title
- Include at least one benefit-focused title
- Include at least one problem-solution format title
- Be direct, clear, and precise about what the article teaches
- Avoid generic language in favor of specific terms

**Good Examples:**
- "How to setup Google Ads conversion tracking on Webflow sites" (59 chars)
- "How to block countries from accessing your Framer site" (55 chars)

[META DESCRIPTION OPTIONS]
Create exactly 10 description options (120-155 characters each) that complement the titles:
- All descriptions must clearly explain what readers will learn
- Include the primary keywords without being repetitive
- Create curiosity without being vague or clickbaity
- Focus on the practical outcome or benefit
- Vary the approach between problem-solving, benefit-driven, and learning-focused
- Be specific about the article's purpose while avoiding unnecessary technical jargon
- Include time estimates or step counts when relevant

**Good Examples:**
- "Learn how to install Google Ads conversion tracking in Webflow with thank you pages. Complete step-by-step guide with code placement and testing tips." (154 chars)
- "Complete guide to setting up geo-blocking on Framer with Cloudflare. Block countries, create whitelists, and protect your site in under 20 minutes." (150 chars)

## Content Style Guidelines

1. **Format all UI elements in bold:**
   - Button names: **Save** button
   - Fields: **Redirect URL** field
   - Menu items: **Settings** panel
   - Platform-specific channel or room names: **#general**, **#sales-team**

2. **Use sentence case for all headings**
   - Correct: "How to create a download button in Webflow"
   - Incorrect: "How to Create a Download Button in Webflow"

3. **Optimize headings for SEO value:**
   - Include action words in headings
   - Include the platform name (Webflow, Framer, etc.) in ALL headings (both H2 and H3) when relevant
   - Frame headings as questions or tasks users would search for

4. **Code formatting:**
   - **NEVER use inline code with backticks** - instead, make short code references bold: **brix-attribute="value"**
   - Use proper code blocks with triple backticks for multi-line code
   - Add explanatory comments within code blocks
   - When complete code is provided in the transcript, use [PASTE FULL CODE HERE] in code blocks to save processing tokens
   - Always add a short paragraph of text before a code block, never place code directly inside bullet points or numbered lists

5. **Link and reference style:**
   - Use natural, descriptive anchor text for links (never repeat the same anchor text)
   - For Webflow articles: https://brixtemplates.com/webflow-agency
   - For Framer articles: https://brixtemplates.com/framer-agency
   - Vary anchor text naturally: "our agency can assist", "top Webflow agency", "experienced Framer development team", "BRIX Templates' agency services", etc.
   - When mentioning BRIX Templates, link once in conclusion

6. **Overall tone:**
   - Professional but approachable - write like you're explaining to a colleague, not a technical manual
   - Direct and concise - get to the point without unnecessary words
   - Confident but humble - present solutions with certainty but acknowledge alternatives
   - Helpful without being condescending - assume the reader is intelligent but new to this specific topic
   - Conversational but not casual - use contractions and direct address but maintain professionalism

7. **Troubleshooting sections:**
   - Present as bullet points for scanability
   - Bold the issue name
   - Provide specific, actionable solutions

8. **FAQ section:**
   - Use natural question phrasing that matches how people search
   - Keep answers concise and directly address the question
   - Include specific actionable advice in each answer
   - Use internal links to main article sections when relevant
   - End each answer with a clear conclusion or recommendation

The final article should be practical and actionable, avoiding unnecessary jargon while maintaining technical accuracy. It should position BRIX Templates as an experienced guide without being overtly promotional. Remember to explain complex concepts in simple terms and always prioritize clarity over technical impressiveness.

---

[YOUR JOB]
- Follow Article Prompt v1.5 structure strictly
- Use [RESEARCH TECHNICAL DETAILS] for accuracy, step-by-step instructions, code snippets, and technical requirements
- Use [RESEARCH COMMUNITY INSIGHTS] to understand user pain points (inform intro, "Why this matters" section, troubleshooting)
- Use [RESEARCH SEARCH QUERIES] to select 10 best FAQs (prioritize high search volume + relevance to topic)

CRITICAL RULES:
- Match BRIX Templates tone (reference [STYLE GUIDE REFERENCES])
- All headings must include the platform name (Webflow, Framer, etc.) when relevant
- Bold UI elements, never use inline code
- FAQs: Pick 10 from [RESEARCH SEARCH QUERIES] that match these criteria:
  * Natural search phrasing
  * Mix of "What/Why/How/Which/Is/Can"
  * Directly relevant to article topic
  * Answers are 100-150 words
  * Include internal links to article sections where appropriate

FAQ SELECTION - REJECT:
- Generic platform questions (pricing, features, "is it good")
- Questions answerable in 1 sentence
- Questions unrelated to the article topic
- Questions that duplicate article sections verbatim

FAQ SELECTION - PRIORITIZE:
- Questions using exact topic keywords
- Questions with clear implementation/buying intent
- Questions that add value beyond the main article
- Questions with proven search volume (check [RESEARCH SEARCH QUERIES] rankings)

OUTPUT:
- Full article following Article Prompt v1.5
- 10 meta title options (How to... format, 55-60 chars, sentence case)
- 10 meta description options (120-155 chars)

Deliver the article in Markdown Format.