207
edits
PCJD:Guidelines: Difference between revisions
Changed "element" to "parameter" to avoid confusion
PilleniusMC (talk | contribs) (This is actually hard to write, there's a lot of things to think about) |
PilleniusMC (talk | contribs) (Changed "element" to "parameter" to avoid confusion) |
||
| Line 10: | Line 10: | ||
The How to use section just explains how you can include the meta tags and the SEO extension. | The How to use section just explains how you can include the meta tags and the SEO extension. | ||
Parameters from the required section need to be included and are required on all content pages in the main namespace in the PCJD namespace other rules apply and are judged on a page per page basis. | |||
Parameters from the optional section are not specifically required, but can be included as seen fit. | |||
Last but not least the templates, these are pre fabricated elements you can copy into the pages. | Last but not least the templates, these are pre fabricated elements you can copy into the pages. | ||
| Line 18: | Line 18: | ||
=== How to use === | === How to use === | ||
The meta tags are added via a parser function magic word, in this case being <code><nowiki>{{#seo}}</nowiki></code>, but to actually use the parser function and the meta tags it needs to look like this: <code><nowiki>{{#seo:|}}</nowiki></code> after the first pipe you start with the tags while then also separating the other tags with pipes. | is the pipe character. | The meta tags are added via a parser function magic word, in this case being <code><nowiki>{{#seo}}</nowiki></code>, but to actually use the parser function and the meta tags it needs to look like this: <code><nowiki>{{#seo:|}}</nowiki></code> after the first pipe you start with the tags while then also separating the other tags with pipes. | is the pipe character. | ||
<br>Each | <br>Each parameter consists of a keyword and a value, separated by an equal sign (=). The keyword can't be separated by a space, any space in a keyword would be replaced with and underscore (_), but they are listed as how they need to be used. There should be no space before or after the equal sign. In the value you can have spaces. | ||
So the parser looks like this as an example: <code><nowiki>{{#seo:|keyword1=value1|keyword2=value2|keyword3=Text with spaces}}</nowiki></code> | So the parser looks like this as an example: <code><nowiki>{{#seo:|keyword1=value1|keyword2=value2|keyword3=Text with spaces}}</nowiki></code> | ||