Replacing the render pipeline (or duplicating it outside of contentlayer.dev so we can remove contentlayer.dev)
Acceptance
[x] Analyse what is involved comprehensive notes in the PR #483; most relevant parts also in Notes below
[x] Flag things we want to deprecate e.g. importing components in markdown (strictly this comes from the pipeline work)
[x] Replace to markdowndb
[x] Replace the pipeline
Notes
Deprecated features
document types and hence:
type frontmatter field and importing all files of a given type
frontmatter fields validation
auto-extracting title (TBC can't remember why)
page "getters"
contentInclude and contentExclude config fields for including/excluding content folders
import and export statements in markdown documents
hover-over tooltips (didn't have time to fix them + probably would be nice to implement them in a better way anyway)
Changes required/suggested to @flowershow/markdowndb
implement document types in @flowershow/markdowndb with specific computed fields, helper methods (e.g. BlogType.getAuthors()) and frontmatter validation
support importing all documents of a given type (e.g. mddb.getFiles({ type: "Blog" }))
config file for @flowershow/markdowndbpackage with e.g. contentExclude and contentInclude contentlayer's counterparts
rufuspollock
commented
1 year ago
Note that replacing contentlayer.dev involves ...
Acceptance
Notes
Deprecated features
typefrontmatter field and importing all files of a given typecontentIncludeandcontentExcludeconfig fields for including/excluding content foldersimportandexportstatements in markdown documentsChanges required/suggested to @flowershow/markdowndb
@flowershow/markdowndbwith specific computed fields, helper methods (e.g.BlogType.getAuthors()) and frontmatter validation@flowershow/markdowndbpackage with e.g.contentExcludeandcontentIncludecontentlayer's counterparts