Page components: Difference between revisions
a little clarification |
elaborate |
||
| Line 6: | Line 6: | ||
<!-- {{#ev:service|id|dimensions|alignment|description|container|urlargs|autoresize|valignment}} --> | <!-- {{#ev:service|id|dimensions|alignment|description|container|urlargs|autoresize|valignment}} --> | ||
{{ambox | {{ambox | ||
|text=Inspired by [https://www.youtube.com/live/jCjaMnxgq2Q?t=6022 river's talk about the wiki.gg IMP (Improved Main Page) framework], I finally got around to creating | |text=Inspired by [https://www.youtube.com/live/jCjaMnxgq2Q?t=6022 river's talk about the wiki.gg IMP (Improved Main Page) framework], I finally got around to drafting this initiative. The goal is to create a reference, or even an installable system for third-party wikis to be able to equip their authors and content creators with the best tools, guidelines and components for creating said content. If MediaWiki is the platform, and a full set of curated extensions (plus attendant microservices) creates an even more powerful platform, you still end up with an unfurnished mansion on day one (launch). | ||
To develop such a system we | To develop such a system we need to refer to all the technical underpinnings used by developers and wiki admins, so bear with us during the process. Eventually there will be separate technical vs. user content. | ||
[[mw:Design]] is probably the best starting point to learn about User Interface in the MediaWiki context. | [[mw:Design]] is probably the best starting point to learn about User Interface in the MediaWiki context. | ||
| Line 30: | Line 30: | ||
<ref name="z8">https://wpvip.com/blog/wordpress-block-data/</ref> | <ref name="z8">https://wpvip.com/blog/wordpress-block-data/</ref> | ||
== | == Context == | ||
We try to untangle the confusing mess of terminology later, but first let's just jump into an overview of some of the current solutions available for Drupal and WordPress users to | We try to untangle the confusing mess of terminology later, but first let's just jump into an overview of some of the current solutions available for Drupal and WordPress users to frame the discussion of what could be possible for MediaWiki in terms of | ||
# Creating Pages and Content | # Creating Pages and Content | ||
# Building Page Components | # Building Page Components | ||
# Managing Site Design | # Managing Site Design | ||
If you want, you can [[Page components/about|skip all the context and just dive into solutions for MediaWiki]] | |||
=== Drupal === | === Drupal === | ||
| Line 48: | Line 49: | ||
Both Divi and Elementor perform well on pages of simple and moderate complexity. The current version of Divi shows poor performance on complex pages. Elementor performs much better than Divi on complex pages, though not as well as modern page builders like [https://breakdance.com/ '''Breakdance'''] or Oxygen<ref>For a decent comparison of Divi vs Elementor, see https://www.wpallimport.com/divi-vs-elementor/</ref>. '''[https://oxygenbuilder.com/ Oxygen]''' is distinct from traditional page builders like Elementor or Divi because it replaces the standard WordPress theme system, allowing users to design every aspect of their website, including headers, footers, content areas, and dynamic data layouts, directly within its visual editor. | Both Divi and Elementor perform well on pages of simple and moderate complexity. The current version of Divi shows poor performance on complex pages. Elementor performs much better than Divi on complex pages, though not as well as modern page builders like [https://breakdance.com/ '''Breakdance'''] or Oxygen<ref>For a decent comparison of Divi vs Elementor, see https://www.wpallimport.com/divi-vs-elementor/</ref>. '''[https://oxygenbuilder.com/ Oxygen]''' is distinct from traditional page builders like Elementor or Divi because it replaces the standard WordPress theme system, allowing users to design every aspect of their website, including headers, footers, content areas, and dynamic data layouts, directly within its visual editor. | ||
== Cross- | == Cross-platform 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''' | 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 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. | 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. | ||
| Line 90: | Line 91: | ||
|- | |- | ||
|'''Modules''' | |'''Modules''' | ||
| | |The term 'module' is most often referring to a Lua script that provides functionality to the User Interface in combination with Templates. The ''concept'' of a Drupal Module or WordPress Plugin is an Extension. | ||
|A module is an add-on that provides specialized functionality to Drupal. It is not the content itself, but rather the feature that provides the content. | |A module is an add-on that provides specialized functionality to Drupal. It is not the content itself, but rather the feature that provides the content. | ||
|This term is generally associated with plugins and themes in WordPress, not content elements. | |This term is generally associated with plugins and themes in WordPress, not content elements. | ||
| Line 128: | Line 129: | ||
|Used to define the overall content structure, not individual components. | |Used to define the overall content structure, not individual components. | ||
|} | |} | ||
=== How these terms work together === | |||
In many modern systems, the architecture works like this: | In many modern systems, the architecture works like this: | ||