We use Markdown files for pages that are text-centric. There are two main collections of these dynamically-created-from-Markdown pages:

1. Newsletter issues: web versions of Newsletter issues, like blog posts, that are also sent out via email (see Email Newsletter).
2. Legal pages: https://www.peels.app/terms, Privacy, and Colophon (that last one is not really ‘legal’ in nature but close enough, we can rename ‘legal’ to something else later if need be).

You can think of both of these like collections in Eleventy or Jekyll. Both of these collections’ Markdown content live in the src/content folder. Their shared types and shared utils live in src/lib/content.

These ‘collections’ were built based on a system described by ‘Di Does Digital’ across multiple blog posts on her website. Mainly these three:

• https://didoesdigital.com/blog/nextjs-blog-02-add-mdx/
• https://didoesdigital.com/blog/nextjs-blog-06-metadata-and-navigation/
• https://didoesdigital.com/blog/nextjs-blog-09-rss/

Typography

• [ ] Automatically import common MDX components into the mdx-components file so I don’t need to import them at the top of each MDX file.
• [ ] Automatically convert dumb quotes to smart quotes, perhaps via the mdx-components file, via the remark-smartypants plugin or similar.

RSS

The newsletter ‘collection’ has an RSS feed handled in route.ts.

• [ ] Add author (array) and image fields.