Fix _config.yml duplicate keys; add projects collection; create two sample project items; list projects on /projects/ page

[recursionlab]

Summary by Sourcery

Add and configure a new 'projects' collection by cleaning up '_config.yml', implement a listing page at '/projects/', and include two example project items

New Features:

• Add 'projects' collection with output and permalink settings
• Create a '/projects/' page that dynamically lists all project items
• Add two sample project entries in the '_projects' directory

Bug Fixes:

• Remove duplicate 'exclude' keys and consolidate excluded paths in '_config.yml'

[sourcery-ai]

Reviewer's Guide

This PR consolidates duplicate key definitions in the Jekyll config, adds a new 'projects' collection with routing, implements a listing template on the /projects/ page, and provides two sample project entries to bootstrap the new collection.

Entity relationship diagram for new 'projects' collection in Jekyll site

erDiagram
    PROJECTS {
      string title
      string summary
      string status
      string permalink
      string layout
    }
    PROJECTS ||--o| PAGES : "listed on"
    PAGES {
      string title
      string permalink
      string layout
    }

Loading

File-Level Changes

Change	Details	Files
Removed duplicate 'exclude' definitions and consolidated file exclusions	Added vendor, node_modules, gulpfile.js, and package.json to the top-level exclude list Deleted the redundant exclude block under the defaults section	_config.yml
Introduced 'projects' collection in configuration	Defined a new projects collection with output enabled Set permalink pattern to /projects/:name/ for project items	_config.yml
Updated the projects page to dynamically list project items	Assigned and sorted site.projects into a local variable Iterated over each item to render titles with optional summaries	_pages/projects.md
Added two sample project pages under the new collection	Created a recursive-reasoning-tools-for-llms.md sample with metadata and description Created a recursive-self-reflection-engine.md sample with metadata and description	_projects/recursive-reasoning-tools-for-llms.md _projects/recursive-self-reflection-engine.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• The projects collection permalink is defined using :name but your sample items only set title in their front matter—either switch the permalink to :title or add a name field to avoid broken URLs.
• There's a leftover commented-out exclude block under defaults in _config.yml that’s now redundant—consider removing it to keep the config clean.
• On the /projects/ page, you might add an empty-state message or placeholder when no projects exist to improve the user experience.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The projects collection permalink is defined using :name but your sample items only set title in their front matter—either switch the permalink to :title or add a name field to avoid broken URLs.
- There's a leftover commented-out exclude block under defaults in _config.yml that’s now redundant—consider removing it to keep the config clean.
- On the /projects/ page, you might add an empty-state message or placeholder when no projects exist to improve the user experience.

## Individual Comments

### Comment 1
<location> `_config.yml:89-91` </location>
<code_context>
   poetry:
     output: true
     permalink: /:collection/:title/
+  projects:
+    output: true
+    permalink: /projects/:name/

 # Plugins (preferred order: remote theme first)
</code_context>

<issue_to_address>
**question:** Check consistency of permalink structure for new 'projects' collection.

Confirm that all project items include a 'name' field, or switch to ':title' for consistency unless a distinct reason exists for using ':name'.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

question: Check consistency of permalink structure for new 'projects' collection.

Confirm that all project items include a 'name' field, or switch to ':title' for consistency unless a distinct reason exists for using ':name'.