User:Limiki

Front End/Accessibility dev

=Getting Started with Skins=

Resources

 * http://blog.redwerks.org/2012/02/08/mediawiki-skinning-tutorial/
 * https://www.mediawiki.org/wiki/MediaWiki:Common.css
 * https://www.mediawiki.org/wiki/Manual:$wgDefaultSkin

Notes on Skins
At first look it seems conceptually similar to the LJ s2 system, but php. What do the most successful skins (monobook and vector) have in common? What do they lack?

Taxonomy Notes
Outline taxonomy. Daniel Friesen highlights the elements: body, title hierarchy, notifications, search, personal tools, actions, toolbox, language links, footer.

Supertypes:
 * Object: ENTRY, USER
 * Category: hierarchy and organisation
 * Actions: buttons, making changes

ZONE: SEARCH/BROWSE/EXPLORE
 * Search/browse: search box, category navigation, wikilinks

ZONE: CONTENT note: versions, revisions, history: key feature of wiki for power users, almost invisible to casual user
 * Read Content (front facing)
 * Edit/Create content
 * Navigate *versions* (back facing "under the hood")

ZONE: USER
 * a user page is an entry
 * Modifiers (prefs and on-page)

ZONE: SYSTEM
 * a huge amount of screen estate is devoted to all this stuff, power user/admin oriented design

=Misc Notes= 17/02/12: just storing some random notes here as I explore

Misc

 * An error occurred while changing your watchlist settings for "Extension:Metrics". (jS?)
 * look for Selenium patterns

CSS

 * editing common.css looking for link to css and page diagram: could link go to a page with template?
 * https://www.mediawiki.org/wiki/MediaWiki:Common.css
 * pos external editor? how likely is it that skins writers are not already writing with dummies in externals

HTML

 * class="mw-editTools" figure out if this html can be updated, if not to lovely lists then at least with some navigable headings/role addition (this is rampant throughout - make list, broach question)
 * can accesskeys be stripped on pref []