Closed olayway closed 1 year ago
Not sure what do we want to do with our blog posts. Should we update them as well (and e.g. add "updated" date to frontmatter) or archive and write new ones with focus on MarkdownDB?
Can you move this discussion into issue so we don't lose it. I think this is a separate discussion.
@luccasmmg could you review - it's good practice to have an outsider check it!
Not sure what do we want to do with our blog posts. Should we update them as well (and e.g. add "updated" date to frontmatter) or archive and write new ones with focus on MarkdownDB?
Can you move this discussion into issue so we don't lose it. I think this is a separate discussion.
Sure, I've created an issue for it.
Name | Link |
---|---|
Latest commit | c3de3d2b67f0c9248a9aff28a081a21d954753ce |
Latest deploy log | https://app.netlify.com/sites/spectacular-dragon-c1015c/deploys/644952851ff4640008bf0ac0 |
LGTM One question, Why isn't there a section explaining markdowndb the same way there was explaining the content layer? The last month I kinda of got curious about it but there wasn't any place besides the github discussions to figure it out, is there a plan to have documentation about it?
@luccasmmg We do have some basic information in the MarkdownDB package README itself. Probably we'll also write some blog post about the whole switch from Contentlayer to MarkdownDB in Flowershow but that's for another time I think.
Closes #484
Changes
All docs pages reviewed and updated to be in line with current Flowershow version, which uses MarkdownDB. Comprehensive list of changes in issue #484.
TBD
Not sure what do we want to do with our blog posts. Should we update them as well (and e.g. add "updated" date to frontmatter) or archive and write new ones with focus on MarkdownDB?