5 ms·
It would depend on the use case, but as this looks like it's aimed at a technical audience, you'd generally have some sort of CI/CD pipeline that renders the ma
by harg 4y ago
It would depend on the use case, but as this looks like it's aimed at a technical audience, you'd generally have some sort of CI/CD pipeline that renders the markdoc on a server and deploys the output accordingly, be it a react app, plain html, etc.
In many cases, authors would probably need to run the toolchain locally so they can preview their changes. But publishing would basically be the same as committing code and having a CI pipeline take it from there
- verdverm 4y agoyou definitely need something around this, it lacks a lot of the other features in Hugo or Jekyll Might be easier to graft into an existing, dynamic CMS (that uses a DB)