The style guide already prescribes how emphasis is to be applied. It describes using wiki text.
"Any kind of emphasis you want to make should default to mixed or lower case in italics. Italics markup, as noted elsewhere on this page, is accomplished with two single quotes/apostrophes before and after the text to be emphasized."
I'm not opposed to using other kinds of emphasis if there are reasonable benefits, such as semantic uses, but they should be done smartly. For example, via a template, or in an edge case.
In general I would just say don’t use bare HTML if the result is achievable in wikitext. Not all editors are going to know what HTML is, and we don’t currently require it as a prerequisite to edit. Otherwise we could just have a git repo to collaborate and push to a static host, which I’m sure would save a lot on cost at the expense of killing user friendliness for the casual editor without prerequisite knowledge.
"Any kind of emphasis you want to make should default to mixed or lower case in italics. Italics markup, as noted elsewhere on this page, is accomplished with two single quotes/apostrophes before and after the text to be emphasized."
I'm not opposed to using other kinds of emphasis if there are reasonable benefits, such as semantic uses, but they should be done smartly. For example, via a template, or in an edge case.
In general I would just say don’t use bare HTML if the result is achievable in wikitext. Not all editors are going to know what HTML is, and we don’t currently require it as a prerequisite to edit. Otherwise we could just have a git repo to collaborate and push to a static host, which I’m sure would save a lot on cost at the expense of killing user friendliness for the casual editor without prerequisite knowledge.