[Flowershow] Documentation updates after switch to MarkdownDB

[olayway]

Acceptance

• [x] all docs pages are up-to-date
  • [x] /docs/assets renamed to Embedding files + minor instructions corrections
  • [x] /docs/blog
  • removed references to document types, i.e. Page, Blog, Person or setting them in the frontmatter
  • all documents in /blog folder will be treated as blog posts (at least for now)
  • removed section about BlogsList component as it is now "hard coded" in the template's blog.tsx page
  • [x] /docs/blog-tutorial rm as mostly irrelevant content and duplicate of (already updated) /docs/blog-section-tutorial
  • [x] /docs/blog-section-tutorial removed instructions on setting type: Blog; removed instructions re creating blog index page as this page is "hard-coded" in the /pages folder atm, rm duplicated instructions on blog authors and added link to relevant docs page; renamed to simply: /docs/blog-tutorial
  • [x] /docs/callouts
  • [x] /docs/comments
  • [x] /docs/config
  • replaced all mentions of config.js with config.mjs as this extension has been required for some time already
  • replaced ambiguous authorUrl with domain
  • [x] /docs/contentlayer removed as irrelevant for Flowershow template V2
  • [x] /docs/contributors replace npx with pnpm (should've been done long ago)
  • [x] /docs/custom-layout removed parts related to creating custom Contentlayer document types and creating a home page for recipes (for now, need to think about the best way to approach it now)
  • [x] /docs/custom-theme
  • [x] /docs/dropdown removed as nav bar drop-downs have been deprecated
  • [x] /doc/edit-this-page correct config field name for repo edit root
  • [x] /docs/excalidraw
  • [x] /docs/seo small fixes applied
  • [x] /docs/layouts removed part about setting changing default layout as was possible by tweaking the contentlayer file and about creating custom document types in contentlayer config
  • [x] /docs/light-dark-theme just some adjustments to phrasing
  • [x] /docs/link-previews hidden for now as we need to re-implement this feature
  • [x] /docs/math replaced references to MathJax with KaTeX
  • [x] /docs/mdx removed (copy is on v1 branch)
  • [x] /docs/publish-tutorial updated a note about hot-reloading
  • [x] /docs/search some minor adjustments + fix of search.json file path in flowershow/core
  • [x] /docs/sitemap
  • [x] /docs/site-wide-toc
  • [x] /docs/social-previews renamed to social-links-embeds
  • [x] /docs/syntax some minor fixes; removed section about frontmatter for now as data set in it can't really be used in any way (apart from setting title, description or blog-specific fields, which are all mentioned in other, relevant places)
  • [x] /docs/table-of-contents minor phrasing corrections
  • [x] /docs/tailwind

[rufuspollock]

@olayway i would definitely consider markdowndb is Flowershow v2-alpha or something. We could even have 2 sites e.g. v1.flowershow.app that runs v1 branch (we could branch v1) and a v2 which is main ... (cf how tailwind etc does it). However, this could be overkill given where we are in terms of usage etc atm.