You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
arguments added to includes like with {% include figure.html caption="..." %} (which are a special case too b/c they actually get processed as markdown...)
It's not always intuitive how ' and " will interact in which domain, and there are often mutiple ways to do it which can be confusing for newcomers to try and sort it all out. We need a cheat sheet so editors can look this up when working on tricky things like #1644
i'm tired. but I'll start work on it at some point - if anyone @programminghistorian/technical-team finds some good pre-existing resources that we could link to, that would also be lovely.
The text was updated successfully, but these errors were encountered:
Oof I'm not certain I'm really good on all the distinctions either, and I couldn't find any readymade resources for this when googling around - just a thousand stack overflow threads. I could help write this up, but is the following correct? Something like…
YAML - use double quotation marks, with a caveat for escaping the double quotes as necessary
Markdown - should not matter which you use if it's just content
HTML inside markdown - should be double quotation marks with internal quotes escaped as necessary?
code blocks - should not matter for the site since the code blocks aren't being parsed - it would just depend on the language for the code block
arguments - should be double quotation marks with internal quotes escaped as necessary?
We need to put strings in to a lot of places:
includes
like with{% include figure.html caption="..." %}
(which are a special case too b/c they actually get processed as markdown...)It's not always intuitive how
'
and"
will interact in which domain, and there are often mutiple ways to do it which can be confusing for newcomers to try and sort it all out. We need a cheat sheet so editors can look this up when working on tricky things like #1644i'm tired. but I'll start work on it at some point - if anyone @programminghistorian/technical-team finds some good pre-existing resources that we could link to, that would also be lovely.
The text was updated successfully, but these errors were encountered: