Now, anyone can change layout (see HelpOnThemes and ThemeMarket), even having more that one option for each wiki, and giving it's users chance to select them personally (see UserPreferences).

Contents

  1. Goals
  2. Browser support
  3. Element categories
    1. System messages
    2. Content metainfo
    3. Content navigation
    4. Content actions
  4. Category rankings
  5. Top-level containers
  6. Sidebar
    1. Navigational
  7. Content
  8. Footer
  9. Thoughts
  10. Audience
  11. Resources

Goals

What are the goals for a new default skin?

Browser support

Which technology and to what extent to use it is a governing factor when setting about to create a new default skin. Currently, MoinMoin seems to be using HTML4, CSS1 and JavaScript. Preferably we could use these technologies in a fashion that will let the design degrade gracefully for text-based browsers, etc. XHTML-strict may be tempting (structure/presentation separation, valid xml) but I'm not sure it's worth upping the requirements for baseline access to the site. HTML4.01-strict could accomplish something similiar. How about a baseline of html 4.01 and enhanced using CSS1 and JavaScript 1.2?

Element categories

This makes it pretty much clear that we need to have a split global/content-view

  1. System messages: Your edit has been saved

  2. Content metainfo: Page title, Last modification time, Last user to modify, Size of page

  3. Content navigation: Navigation history, Up one level, Inter-page navigation

  4. Content

  5. Content actions: Refresh, Print display, XML display, Subscribe to page, Edit page, Detailed metainfo, Diff from last edit, Search interface, Attach file, Delete page, Find related pages, Local site map, Run spell check

  6. Global navigation: Shortcut to FrontPage, Customizable navibar, Help, UserPreferences

  7. Global information: Powered by Python, Wiki version, Wiki run timings

System messages

A message box showing the result of the last action of the user, such as saving an edit, obtaining the lock for an edit, etc. This can potentially be errors, and should be clearly visible right at the top with a distinct color -- one alternative would be a JavaScript alert. It would be really nice if we could color it differently depending on the result, or use an icon. Layout-wise it would probably be best if this is kept to one line.

Content metainfo

Telling the user where she currently is. The page title, and what time and by who the last edit was made. Why is the size of the page interesting? Clicking the title finds all pages linking to this page. The timestamp could be a link to the detailed revision history? Or have an shorcut to the detailed MetaData page? An option to have the full MetaData here by default?

Content navigation

Tell the user what she can find on this page. The navigational history doesn't really belong here. The "up one level"-shortcut. Links within this page and headings within this page would be useful for really large pages. This could also be a good place to stick all the "find related"-stuff.

Content actions

Tell the user what she can do with this page.

Category rankings

  1. System messages (what was the result of my last action?)

  2. Content metainfo (where am I?)

  3. Content navigation (what can I find within this page?)

  4. Content

  5. Content actions (what can I do with this content?)

  6. Global navigation (where can I go from here?)

  7. Global information (where and how am I reading this?)

Top-level containers

  1. Sidebar
  2. Content
  3. Footer

possible-moin.gif

This a possible layout that can be done in HTML 4.01 strict and completely decorated (and rearranged) using external CSS stylesheets. If everybody agrees (more or less) I can do the markup so it can be incorporated in the code.
EduardoMercovich 30/04/04.

Sidebar

What do we do with "Find with similar names" & "Find pages who link to this one". I think finding links is the most useful one. I think sticking 'up one level' would be better to stick in the name somewhere in the content area. Use the "..." to signify menu choices that lead to another dialog? What is the point of "Format as XML" in the UI?

{{{Find Related (Backlinks) Show all Links (LocalSiteMap, name is a bit misleading) Advanced Search (Better name for this one? leads to FindPage)

Edit this Page (EditPage) Attach File Check Spelling Subscribe Show last Changes (Diff) Show Details (info) Format for Printing Format as XML Delete

Help contents Recent changes User preferences

<Custom navilinks> }}}

Content

Content location in format WikiName -> Page -> SubPage WikiName leads to frontpage Provides link to parent in the case of a subpage Otherwise, provides the traditional backlinks mode

What to do with the navigational history?

Box with MetaData summary: Last edited by NiklasAldergren at 2003-07-25 16:06:10 User-defined format for date formatting, possibly relative timestamping (two hours ago, etc.) Page size is XXX bytes (why is this so interesting again? move to detailed MetaData page!)

Format all content with sane widths to increase readability (maybe make it user-definable?) Format paragraphs so that fixed-format paragraphs don't ruin the layout (i.e. code passages)

Needs room for access control text (You cannot edit this page, etc)

Footer

Thoughts

Audience

Resources

MoinMoin: MoinMoinIdeas/BetterDefaultTheme (last edited 2007-10-29 19:06:15 by localhost)