Add initial repository structure for code-poetry collection

[Copilot]

Bootstraps an empty repo into a structured anthology for code-related poems, organized by theme with clear contribution conventions.

Structure added

• themes/ — Poem root; four initial subdirectories (creativity, debugging, ai, open-source), each seeded with an example poem
• contributions/poem-template.md — Copy-ready template with required YAML front-matter (title, author, style, tags, date, license)
• assets/README.md — Placeholder for media/code-snippet assets with usage guidance
• README.md — Project overview, directory map, themes index, poem format spec
• CONTRIBUTING.md — Naming conventions (kebab-case), metadata requirements, new-theme proposal process, PR checklist

Poem front-matter convention

Every poem file must open with:

---
title: "Your Poem Title"
author: "Your Name or GitHub Handle"
style: "free verse | haiku | sonnet | ode | concrete | other"
tags: [tag1, tag2]
date: YYYY-MM-DD
license: MIT
---

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Plan repository structure for a code-poetry collection</issue_title>
<issue_description>## Repository Structure Planning: Code Poetry Collection

Objective:
Define the initial structure and organization for a collection of code-related poems in this repository.

Proposed Directory Structure

• /themes/ — Main folder containing all poetry categorized by theme.
  • /themes/creativity/
  • /themes/debugging/
  • /themes/ai/
  • /themes/open-source/
  • (add more themed folders as needed)
• /contributions/ — Guidelines and templates for contributing new poems.
• /assets/ — (Optional) Images, code snippets, or media to accompany poems.
• /README.md — Project overview, contribution instructions, and index of poems by theme.
• /CONTRIBUTING.md — Contribution guidelines and standards for new submissions.

Guidance

• Poems should be placed in markdown files under the relevant /themes/[theme]/ folder.
• File naming: title-of-poem.md (kebab-case)
• Each poem file should include metadata at the top (title, author, language/style, tags).
• Contributions must follow the template provided in /contributions/.

Next Steps

• Review and modify the proposed structure as needed.
• Decide on initial themes to create.
• Draft the first version of the README.md and CONTRIBUTING.md.

---

Questions:

• Would you like to propose any initial themes or example poems?
• Should there be extra requirements for file formats, licenses, or review process?</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Plan repository structure for a code-poetry collection #1

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[zacateras]

@copilot replace this poem with another one

[Copilot]

Replaced "Merge Request" (sonnet) with a new free-verse poem, "Fork and Flourish", in themes/open-source/fork-and-flourish.md. The file has been renamed to match the new title in kebab-case. (ab20e5b)

[garygegpt-droid]

The code-poetry anthology structure is fantastic! For the themes, consider adding a "github-readme" theme specifically for poems that render in GitHub profiles. You could also add a CI check that validates the 5-7-5 syllable structure for haikus. Great contribution to the developer creativity space!