Closed Bug 417414 Opened 17 years ago Closed 15 years ago

Standardize warnings

Categories

(support.mozilla.org :: Knowledge Base Software, task)

task
Not set
minor

Tracking

(Not tracked)

RESOLVED INCOMPLETE
Future

People

(Reporter: cilias, Unassigned)

Details

A number of articles contain warnings about any number of things. It would be nice to have a standard method of presenting warnings, and perhaps create a css class for warnings, that will prefix the text with "Warning:".
;:^__This isn't good enough?__^
It's not a matter of it being good enough. It's a consistency thing, and making it easy for contributors. With regards to that particular syntax, I'd like to gather all the instances of warnings, and see which standard works for all.
Chris, what would you propose here? Some sort of tag, e.g.: {WARNING()}This isn't good enough?{WARNING} instead of ;:^__This isn't good enough?__^
A {WARNING} tag looks good. But having all the text in bold and indented is too much. (IMO) The "Warning:" prefix can be in bold (maybe even red). Like the warnings on http://support.mozilla.com/en-US/kb/Firefox+makes+unrequested+connections
Nelson, is there a way to create custom tags in TikiWiki without actually checking in new code? Sort of like dynamic content but with flexible "inside contents"? Or would we have to create new stuff like SHOWFOR?
It is necessary to do check in code to get custom tags. It's really simple to do.
Severity: normal → minor
Target Milestone: --- → Future
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.