Change Details

== Problem == Extension developers and even core MediaWiki developers want to, or should want to, use a standardized design. Even if we don't like the standard itself, by using a standard we can then inherit improvements to the standard with little to no additional work. OOjs UI is the standard. However, it is difficult to work with, owing to poor documentation. This discourages its use and adoption as a standard. Compare this to other frameworks such as Semantic UI that make it very easy to use its design. You can use its JavaScript widgets for specialized features, or just use the CSS to get the look and feel if you are dealing with static HTML. == Who would benefit == People developing new extensions and those working on improvements to MediaWiki core and existing extensions. The Wikimedia Foundation would benefit from less time wasted on figuring out this system. == Proposed solution == Better documentation that makes it easier for developers to integrate OOjs UI.

== Problem == Extension developers and even core MediaWiki developers want to, or should want to, use a standardized design. Even if we don't like the standard itself, by using a standard we can then inherit improvements to the standard with little to no additional work. [[https://www.mediawiki.org/wiki/OOjs_UI|OOjs UI]] is the standard. However, it is difficult to work with, owing to poor documentation. This discourages its use and adoption as a standard. Compare this to other frameworks such as Semantic UI that make it very easy to use its design. You can use its JavaScript widgets for specialized features, or just use the CSS to get the look and feel if you are dealing with static HTML. == Who would benefit == People developing new extensions and those working on improvements to MediaWiki core and existing extensions. The Wikimedia Foundation would benefit from less time wasted on figuring out this system. == Proposed solution == Better documentation that makes it easier for developers to integrate OOjs UI.

== Problem == Extension developers and even core MediaWiki developers want to, or should want to, use a standardized design. Even if we don't like the standard itself, by using a standard we can then inherit improvements to the standard with little to no additional work. [[https://www.mediawiki.org/wiki/OOjs_UI|OOjs UI]] is the standard. However, it is difficult to work with, owing to poor documentation. This discourages its use and adoption as a standard. Compare this to other frameworks such as Semantic UI that make it very easy to use its design. You can use its JavaScript widgets for specialized features, or just use the CSS to get the look and feel if you are dealing with static HTML. == Who would benefit == People developing new extensions and those working on improvements to MediaWiki core and existing extensions. The Wikimedia Foundation would benefit from less time wasted on figuring out this system. == Proposed solution == Better documentation that makes it easier for developers to integrate OOjs UI.