app3.py

# Section 2: FAQ (FOR CHALLENGE PARTICIPANTS)
with gr.Column(scale=4):
    gr.HTML(
        """
        <div class="dds-card">
            <h3 class="dds-section-title">Section 2 — Challenge FAQ</h3>
            <p class="dds-muted">
                Quick answers for participants. If something isn’t answered here, ask the Copilot in the chat.
            </p>
        </div>
        """
    )

    with gr.Accordion("FAQ 1 — What should I build for this challenge?", open=False):
        gr.Markdown(
            """
- Build a simple AI application that matches one of the challenge paths (e.g., LLM/API integration, no-code/low-code, etc.).
- Your goal is a **working demo** + **proof-of-work** you can share.
- Ask in chat: *“What are good project ideas that fit the rules in this challenge?”*
            """.strip()
        )

    with gr.Accordion("FAQ 2 — What are the paths/tracks and which one should I choose?", open=False):
        gr.Markdown(
            """
- Choose based on your comfort level:
  - **LLM/API Integration Path:** Python + API calls + basic RAG patterns
  - **No-code/Low-code Path:** build fast using tooling
  - **Sponsor/Tool-specific path (if applicable):** follow the workshop/demo tool
- Ask in chat: *“Given my background (X), which path fits best and why?”*
            """.strip()
        )

    with gr.Accordion("FAQ 3 — What is the minimum deliverable to be eligible?", open=False):
        gr.Markdown(
            """
Typical minimum for eligibility:
- A working app link (Gradio / Hugging Face / Streamlit / etc.)
- A short description + how to use it
- A repo or shared proof-of-work (optional but recommended)
Ask in chat: *“What is the minimum submission requirement mentioned in the challenge doc?”*
            """.strip()
        )

    with gr.Accordion("FAQ 4 — How do I submit my project?", open=False):
        gr.Markdown(
            """
- Usually you submit:
  - App URL (where judges can open it)
  - Repo URL (optional but strong)
  - Short write-up + screenshots/video (if required)
Ask in chat: *“What is the official submission format and where do I submit?”*
            """.strip()
        )

    with gr.Accordion("FAQ 5 — Where should I deploy so judges can access easily?", open=False):
        gr.Markdown(
            """
Low-friction options (no install needed):
- **Hugging Face Spaces (Gradio)** ✅ easiest for demos
- **Streamlit Community Cloud**
- **Vercel (for web apps)**
Ask in chat: *“Which deployment options are recommended in the challenge rules?”*
            """.strip()
        )

    with gr.Accordion("FAQ 6 — What do judges usually look for?", open=False):
        gr.Markdown(
            """
Common judging signals:
- **Working demo** (no errors, easy to use)
- Clear problem statement + target user
- Good AI behavior (grounded answers, guardrails, no hallucination)
- Product thinking (UX, clarity, flow)
Ask in chat: *“What are the judging criteria stated in the challenge document?”*
            """.strip()
        )

    with gr.Accordion("FAQ 7 — What should I post on LinkedIn (proof-of-work)?", open=False):
        gr.Markdown(
            """
Strong proof-of-work post includes:
- 1-line problem + who it helps
- Demo link + screenshot/GIF
- What you learned + next improvement
Ask in chat: *“Give me a LinkedIn post draft based on my project and this challenge.”*
            """.strip()
        )

    with gr.Accordion("FAQ 8 — How do I make my app ‘RAG grounded’ (not hallucinating)?", open=False):
        gr.Markdown(
            """
Best practices:
- Keep answers restricted to retrieved context
- Show sources/snippets (optional but strong)
- If missing info → respond “Not in document” and ask to add content
Ask in chat: *“What does the document say about [X]? If not present, tell me what to add.”*
            """.strip()
        )

    with gr.Accordion("FAQ 9 — I can’t find a detail (dates/rules/prizes). What now?", open=False):
        gr.Markdown(
            f"""
- The Copilot can only answer what is inside **{DOC_PATH.name}**.
- If the official rule/prize/date isn’t in the TXT, add it and restart the Space.
Ask in chat: *“What exact section should I add to the TXT to cover [missing detail]?”*
            """.strip()
        )