History

Typo Admin Interface Proposal

The purpose of this document

WARNING: This document is out of date! (see TypoWishlist) This begs the question, do we add to the wishlist here, or on the more current page?

Sitemap/Navigation Structure

  • Dashboard
  • Settings/Configuration
    • General
    • Blacklist Patterns (Spam Control?)
  • Content
    • Articles
    • Aggregations
    • Static
    • Links
    • Files/Images
  • Presentation
    • Templates/Stylesheets

Navigation

Primary Nav Secondary Nav/Sidebar
  • Retractable Menu
    I really like this idea. It would be nice if users could store 'Favorite/Quick Links' for performing
    common admin task in a retractable sidebar.

FWIW--
IMHO the problem w/all of these nav options is that they typically rely on java/ecma scripts, wh/lieads to browser compatibility issues. One of the cool things about Typo is that it keeps things simple. Navigability always presents a problem but I'd prefer an emphasis on simplicity rather than "cool wizbang just because Apple does it" features.

I'm pretty sure JS are considered ok for all things typo - what with it's heavy use of AJAX and all. I'm sure it wouldn't be too difficult to make things degrade gracefully though (as it probably already does).

Wishlist

Please add your wishlist items here.
  • An Item -- A description of your item if applicable.
  • *Syntax Highlighting* -- Via code blocks, etc. Come up with an easy way to insert a code block. and specify the syntax via CSS, etc. Do it in the Ruby Way. Preliminary patch available on Issue #37 - Vince r565
  • How about putting a link to the blog from the admin screen! submitted patch -jon
  • multiple language management -- see features I use on my WP blog in this post: http://climbtothestars.org/archives/2005/01/23/basic-bilingual-plugin/ -- Steph aka bunnywabbit_
  • Bayesian Sorting of Categories
  • Changes to the Admin interface when listing Articles or Categories:
    • -Add a class of underline to the tr of each row and then apply the css rule: -
    • Fix the column headers so they don't scroll with the data
  • Sidebar/limited templating - at least the ability to turn the sidebar off on some pages (or use different layout for pages vs. articles). Basically we have readme style pages that don't fit as well into the narrow confines of the column as post does, but I bet other users would have other uses for it (of course it introduced inconsitent navigation, so maybe it's bad).
  • Sidebar - adding unique ids or classes to the different items, so they can be styled individually.
  • Sidebar - make the search a sidebar item

Also available in: HTML TXT