Xenharmonic Wiki talk:Conventions: Difference between revisions
Joemcmahon (talk | contribs) |
Joemcmahon (talk | contribs) |
||
| Line 16: | Line 16: | ||
In my opinion this would be contra-productive. Every wiki syntax aims to be as simple as possible ''and'' obvious also in the wiki text. You get the idea of markup's purpose easily. Ans it's easy to adapt for people new to the wiki ho to achieve a goal. It's normally not necessary to know HTML tags for editing wiki content. That's why lists should be created the wiki way (using <code>*</code> and <code>#</code>). <br/> --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 19:22, 30 September 2018 (UTC) | In my opinion this would be contra-productive. Every wiki syntax aims to be as simple as possible ''and'' obvious also in the wiki text. You get the idea of markup's purpose easily. Ans it's easy to adapt for people new to the wiki ho to achieve a goal. It's normally not necessary to know HTML tags for editing wiki content. That's why lists should be created the wiki way (using <code>*</code> and <code>#</code>). <br/> --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 19:22, 30 September 2018 (UTC) | ||
I'm going to agree with [[User:Xenwolf]] here. As a wiki author (as in, I've ''written'' one of these), the''point'' of wiki syntax '''at all''' is to permit you to write pages quickly without having to actually write syntactically-valid HTML. If there was no utility to adding wiki markup, it wouldn't have ''been'' added at all, and we'd just be opening edit boxes to paste in HTML. Which we would all have to always get right. Which we mostly would not, and would then spend time dorking with instead of writing about tunings. | I'm going to agree with [[User:Xenwolf]] here. As a wiki author (as in, I've ''written'' one of these), the ''point'' of wiki syntax '''at all''' is to permit you to write pages quickly without having to actually write syntactically-valid HTML. If there was no utility to adding wiki markup, it wouldn't have ''been'' added at all, and we'd just be opening edit boxes to paste in HTML. Which we would all have to always get right. Which we mostly would not, and would then spend time dorking with instead of writing about tunings. | ||
Wiki list markup, which ''is'' implemented in this wiki, is there to allow you to concentrate on providing content. The [[FREEZE]] stuff was introduced because the person who wrote the conversion chose to just inline rendered lists instead of parsing and converting the markup. Insisting on working against the tool, i.e., the wiki, by forcing HTML markup is counterproductive because it doesn't need to be done, and doing it is slower to write, and harder to update. And updating is the '''''point''''' of using a wiki at all. | Wiki list markup, which ''is'' implemented in this wiki, is there to allow you to concentrate on providing content. The [[FREEZE]] stuff was introduced because the person who wrote the conversion chose to just inline rendered lists instead of parsing and converting the markup. Insisting on working against the tool, i.e., the wiki, by forcing HTML markup is counterproductive because it doesn't need to be done, and doing it is slower to write, and harder to update. And updating is the '''''point''''' of using a wiki at all. | ||
[[FREEZE]] is not a standard. It was a programming shortcut; insisting that it's a reason to hardcode HTML smacks of "I want to do this so I'm finding a reason" not "there is no other way to do this so I've adopted this workaround". There is no need for a workaround. Use the tools. Unless the markup ''cannot be done'' with wiki markup, it should not be there.[[user:joemcmahon]] | [[FREEZE]] is not a standard. It was a programming shortcut; insisting that it's a reason to hardcode HTML smacks of "I want to do this so I'm finding a reason" not "there is no other way to do this so I've adopted this workaround". There is no need for a workaround. Use the tools. Unless the markup ''cannot be done'' with wiki markup, it should not be there.[[user:joemcmahon]] | ||