Markdown or HTML for content #196
Replies: 6 comments 7 replies
-
I use StackEdit to go from gDocs to Markdown. My workflow doesn't involve MS Office anymore. A lot of my Markdown editing is done straight into VS Code with a few Markdown plugins. |
Beta Was this translation helpful? Give feedback.
-
For more complex layouts, we could consider includes with variables. I'm starting to use this technique with Jekyll and so far it works well. I haven't tested the experience with a non developer as of yet, still exploring. |
Beta Was this translation helpful? Give feedback.
-
I also think that maybe only main pages, which could be created using collections to create the content should use HTML and most of the other documents could just be using straight markdown. |
Beta Was this translation helpful? Give feedback.
-
What would be cool is if we use something to convert Word Docs to markdown in the build. |
Beta Was this translation helpful? Give feedback.
-
On thing we noticed was that lists inside of lists can be tricky. Example:
Versus
|
Beta Was this translation helpful? Give feedback.
-
We've decided on using Markdown for as much as possible on the site |
Beta Was this translation helpful? Give feedback.
-
I'd like to open up the discussion of switching to markdown for content of the site that doesn't need any special designs like columns.
@delisma and I were speaking and we think that it might be better to use markdown for all the content.
Once we get the use of it it's quicker to code with less room for error.
I use PuppyPaste to convert Word content to markdown. What do you use?
Beta Was this translation helpful? Give feedback.
All reactions