3 ms·
This one smells a bit like something I run into at work sometimes, where a non-technical person makes a technical decision and the technical people don't suffic
by k1t 4y ago
This one smells a bit like something I run into at work sometimes, where a non-technical person makes a technical decision and the technical people don't sufficiently challenge it.
If you're trying to convert markdown documents into webpages, the most likely output format would surely be HTML, or perhaps something custom to the site like MediaWiki markup.
It's totally possible that a site would allow for new documents to be uploaded in a JSON format, but the format would have to be specified (e.g. which keys are used for the post body and subject) - so "whatever you deem best" is unlikely to work, it would need to be "whatever my webhost expects, which is documented -here-"
I'm happy to be wrong here, and zainhoda's markdown to JSONified HTML is interesting regardless - but I suspect you really wanted a markdown to HTML converter. ex: https://markdowntohtml.com/ https://markdowntohtml.com/ or something more extreme like a static site generator: https://www.getzola.org/ https://www.getzola.org/
- RollAHardSix 4y agoNot necessarily. With the push towards headless development, using JSON to fill content opens up layout options significantly. Being tied to pre-made HTML runs you into significant issues trying to do anything that isn't just markdown page presented with HTML. I left the decision to him because why interfere with someone else who probably has a stronger handle on their own strengths. As for your webhost concern, I can always change webhosts.