Frontmatter for deep dive pages - including editor instructions

[rufuspollock]

Let’s store “structured” content for page in frontmatter e.g. image, description etc so that …

• can do SEO tags for the page – these are pages where we have a specific description, image etc
• can pull this info into the front page “Latest Releases”
• can showcase this on a “deep dives” page

Acceptance

• Refactor one deep dive page to use frontmatter @notes/neo-metallism.md
• [ ] Document these fields in editing guide Moved to Editor guide #103
• Create a template for deep dive pages @ ./templates/template.md
• Refactor all deep dive pages
  commits (2022/04/22):
  • notes/are-crypto-tokens-securities.md
  • notes/collective-action-problems-and-climate-change.md
  • notes/fintech-incrementalism-and-responsible-innovation.md
  • notes/market-fundamentalism.md
  • notes/post-state-technocracy.md

Tasks

• Refactor one page to use frontmatter
  • Identify key frontmatter fields
    • key fields: title, date (published), description, (youtube, podcasts although can be left out)
    • other fields: image (thumbnail) and featured (defaulted to false), created, aliases
  • Update MDX component page template to display those fields if present
  • Add SEO based on the frontmatter fields
    • title, description and Image
• Create a template for creating / editing deep dive pages
  • 'templates/' folder in root web3 for Obsidian
• Update contentlayer to support these fields

Editor guide

• create a template for these pages - BONUS: obsidian templates

Notes

Key front matter fields

Required for deep dive

• title
• date: publication date
• description
• image
• featured: true - this will be used to determine whether featured on Latest Releases on front page

Optional ... (to be decided if we use these - if we have them all the time we could have a standard layout for these pages)

• youtube
• podcast

Note standard fields:

• created: date this page in wiki was created (so more internal housekeeping)
• aliases: obsidian field for aliasing pages

[EilidhRoss1]

@catherinet1 I've assigned you to this task as it's relevant to the editors' guide.

[rufuspollock]

@khalilcodes pretty much all done on tech side. What i suggest is you and @EilidhRoss1 go through late next week and update the deep dive pages and add info to editing guide (reassigning to you @EilidhRoss1 as relates to the deep dive pages which you are maintaining)

[khalilcodes]

Moving 'Document fields in editing guide' to #103 and closing issue.