Page components: Difference between revisions

Line 49:

== Cross-CMS terminology ==

Page components is supposed to be about a high-level design system and editor-centered workflow or toolset to easily produce good-looking content. But there is a '''language''' problem before you can even ~~discusss~~ the topic with different people: different product communities do not use the same terminology. A MediaWiki '''template''' is not what you might be ~~familiar with~~ from ~~other definitions of~~ the ~~word template~~. A '''module''' is not a plugin, unless it ''is'' like a plugin, but not when you mean a Lua module. While Drupal and WordPress both use the term "theme" for the UI, MediaWiki calls this a "skin".

Page components is supposed to be about a high-level design system and editor-centered workflow or toolset to easily produce good-looking content. But there is a '''language''' problem before you can even discuss the topic with different people: different product communities do not use the same terminology. In fact, sometimes a term can mean quite the opposite in different communities. A MediaWiki '''template''' is totally not what you might be accustomed to from the CMS definition<ref name="z6"></ref>. A '''module''' is not a plugin, unless it ''is'' like a plugin, but not when you mean a Lua module. While Drupal and WordPress both use the term "theme" for the UI, MediaWiki calls this a "skin".

This table will not achieve a unified lexicon across the industry, but it does at least show where the same concepts have completely different terminology; or where the exact same word is used for different concepts by different groups.

This table will not achieve a unified lexicon across the industry, but it does at least attempt to show where the same concepts have completely different terminology; or where the exact same word is used for different concepts by different groups.

{| class="wikitable"

@@ Line 49: / Line 49: @@
 ==  Cross-CMS terminology ==
-Page components is supposed to be about a high-level design system and editor-centered workflow or toolset to easily produce good-looking content. But there is a '''language''' problem before you can even discusss the topic with different people: different product communities do not use the same terminology. A MediaWiki '''template''' is not what you might be familiar with from other definitions of the word template. A '''module''' is not a plugin, unless it ''is'' like a plugin, but not when you mean a Lua module. While Drupal and WordPress both use the term "theme" for the UI, MediaWiki calls this a "skin".
+Page components is supposed to be about a high-level design system and editor-centered workflow or toolset to easily produce good-looking content. But there is a '''language''' problem before you can even discuss the topic with different people: different product communities do not use the same terminology. In fact, sometimes a term can mean quite the opposite in different communities. A MediaWiki '''template''' is totally not what you might be accustomed to from the CMS definition<ref name="z6"></ref>. A '''module''' is not a plugin, unless it ''is'' like a plugin, but not when you mean a Lua module. While Drupal and WordPress both use the term "theme" for the UI, MediaWiki calls this a "skin".
-This table will not achieve a unified lexicon across the industry, but it does at least show where the same concepts have completely different terminology; or where the exact same word is used for different concepts by different groups.
+This table will not achieve a unified lexicon across the industry, but it does at least attempt to show where the same concepts have completely different terminology; or where the exact same word is used for different concepts by different groups.
 {| class="wikitable"