Replies: 2 comments 1 reply
-
I saw Matthew Auld send this via email and it's not clear to me whether they deleted the comment or GH discussions bugged out (which it has done in the past) so I'm reproing here:
|
Beta Was this translation helpful? Give feedback.
-
Jekyll/Hugo/Hexo and others do follow the pattern of:
They then use a huge CLI preprocessor to convert all that into your static site. I have had success parsing YAML and Markdown right in the browser, though, using (possibly) the same modules they are: http://nodeca.github.io/js-yaml/ Ironically, the YAML module was only made to work in the browser to power the demonstration on its webpage. But the parsing is just as good. |
Beta Was this translation helpful? Give feedback.
-
In the last resolved Markdown related issue (#1610 ) Paul brought parsing of YAML Front Matter (YFM) up.
I personally use YFM in a lot of my markdown files to add meta information to the files. Some of these files were copied out of my old Jekyll blog.
If Beaker could handle this "front matter" and not render it in the final HTML, but parse it the way Jekyll, Hugo and other CMSes do, this might help other website owners migrate over to Hyperdrive more easily.
Of course it is up for discussion as to just how much parsing Beaker should be doing here?
I would suggest support for these tags: title, status, description, author, tag, category
We could also add control over how the file is parsed to HTML by adding the keys: layout, published, etc
Resources
Beta Was this translation helpful? Give feedback.
All reactions