Lab: Markdown Reflection File

Objective

Create a Markdown reflection file in Zed, use Zed's render option to preview it, revise anything that renders incorrectly, and submit the finished .md file.

Success Criteria

• Create a file named markdown-reflection.md in your lab project folder.
• Use Markdown headings, paragraphs, unordered and ordered lists, a checklist, a link, inline code, a fenced code block, a small table, and an escaped character.
• Preview the file with Zed's render option and revise at least one part based on what you see.
• Explain the difference between Markdown source and rendered output.
• Submit the markdown-reflection.md file.
• Turn the lab folder into a public GitHub repository and submit the URL.

Instructions

1. Open Codex.

2. Create a new Codex project for this lab.

When Codex asks you to choose a folder, create or select this lab folder inside your course labs folder:

~/labs/markdown-reflection-file

The goal is for this lab project to live at:

labs/markdown-reflection-file

3. Ask Codex:

Create a file named markdown-reflection.md with a beginner Markdown reflection template.

Write the Markdown source on multiple lines, not as one long paragraph.
Use headings, blank lines between sections, lists with one item per line, and one fenced code block.

Include sections for:
- What I learned
- What I tried
- Evidence or examples
- What confused me
- Preview fix
- Next steps

4. Open the project folder in Zed.

5. Open markdown-reflection.md in Zed.

6. Fill in the reflection with your own real content from the Markdown primer. Your file must include:

• one title heading
• one short paragraph
• one unordered list
• one ordered list
• one checklist
• one link
• one inline-code filename or command
• one fenced code block
• one small table
• one escaped character example, such as \# not a heading

7. Use Zed's render option to preview the rendered version of your Markdown file.

8. Compare your Markdown source to the rendered output. Fix anything that does not render the way you intended.

9. Add a short ## Preview Fix section explaining one thing you changed after previewing in Zed. If everything rendered correctly on the first try, intentionally make one small mistake, preview it, fix it, and describe the fix.

10. Save the file.

11. Ask Codex:

Review markdown-reflection.md for valid beginner Markdown.

Check that it includes:
- a title heading
- one short paragraph
- one unordered list
- one ordered list
- one checklist
- one link
- one inline-code filename or command
- one fenced code block
- one small table
- one escaped character example
- a Preview Fix section

Also check that the Markdown source is readable, with line breaks and blank lines where they help.

12. Make any final edits Codex recommends only if you understand them.

Required Deliverables

Submit:

• markdown-reflection.md
• the public GitHub repository URL for this lab

Your Markdown file should show that you can write source text, preview rendered output, revise your work, and explain what changed.

Submit Your Lab

• Just attach your markdown file