DokuWiki Installer

:

This page assists in the first time installation and configuration of Dokuwiki. More info on this installer is available on it's own documentation page.

DokuWiki uses ordinary files for the storage of wiki pages and other information associated with those pages (e.g. images, search indexes, old revisions, etc). In order to operate successfully DokuWiki must have write access to the directories that hold those files. This installer is not capable of setting up directory permissions. That normally needs to be done directly on a command shell or if you are using hosting, through FTP or your hosting control panel (e.g. cPanel).

This installer will setup your DokuWiki configuration for ACL, which in turn allows administrator login and access to DokuWiki's admin menu for installing plugins, managing users, managing access to wiki pages and alteration of configuration settings. It isn't required for DokuWiki to operate, however it will make Dokuwiki easier to administer.

Experienced users or users with special setup requirements should use these links for details concerning installation instructions and configuration settings.

For security reasons this script will only work with a new and unmodified Dokuwiki installation. You should either re-extract the files from the downloaded package or consult the complete Dokuwiki installation instructions

driven by DokuWiki powered by PHP
Style Guide (DRAFT) [Mantis Bug Tracker Wiki]

User Tools

Site Tools


mantisbt:style_guide

Style Guide (DRAFT)

HTML

  • Do use HTML5
  • Do not use tables for layout. Tables may only be used when the content is actually table data.
  • Do not put business logic in the templates - Using PHPTAL templating engine will assist with security (automatically escaping strings to prevent XSS attacks), internationalisation and ease of template maintenance. The templates are valid XML documents and can be rendered directly in a web browser without needing to be parsed through the templating engine.

CSS

  • The only method allowed for including CSS styling is via including an external CSS stylesheet in the <head> of the document.
  • Do use a fluid layout
  • Do use css styles to make adjustments for browser widths
    • Investigate media queries for determining width
  • Do support a print stylesheet which emphasizes legibility, clarity and efficient printing
  • Do support mobile devices screen sizes (iPhone/Android/Windows Phone 7)
    • Must be optional
    • Must support screen rotation
    • Must not require a separate url
  • Do design stylesheets with rebranding in mind so that users may change colours and text effects without breaking the layouts
  • Do not use inline CSS styling in any HTML output.
  • Do not use html style attributes
  • Do not use inline <style>..</style> blocks in the body

Javascript

  • The only method allowed for including Javascript is via including an external script file in the <head> of the document (or by placing all script tags just before the body closing tag as this seems to be the standard now)
  • The pages must be able to fully function without Javascript enabled. If Javascript is available then it can be used to replace parts of the DOM with more advanced functionality (in the same way jQuery UI operates)
  • Use jQuery exclusively for any javascript based features
  • Use only jQuery plugins with high rates of usage and active, healthy development
  • Do not use inline Javascript in any HTML output
    • No onclick, onmouseover, etc. attributes
    • No inline <script..>something();</script> blocks
    • Do not use javascript:something() in hyperlink hrefs.

Accessibility and Localization

  • Maintain support for right-to-left (RLT) languages in the redesign (related to CSS)
  • Investigate accessibility concerns in depth to determine how the pages will work in screen readers, on browsers with extra large font sizes, for colour blind users, etc.

User Interface

  • Don't make life hard for power users. Clean up the interface but keep the functionality readily accessible
  • Workflow must be as efficient as possible

Questions for discussion

  1. App Mode – several browsers are now supporting App Mode, do we have any requirements for that? Are there standards around this?
  2. Any requirements to have MantisBT grease monkey friendly to allow users to easily customize the page? Not sure what that means, does it mean naming fields? divs, etc?
  3. Supported browsers / versions? What is the cut off?
    1. Firefox 3.0+
    2. Recent versions of Opera, Chromium, Konqueror, Safari (should almost come for free from I)
    3. IE7+
    4. IE6 support, if needed, can come through community contributions
  4. Come to some sort of arrangement on how plugins will manipulate the HTML to insert their own buttons, widgets, etc as required.
mantisbt/style_guide.txt · Last modified: 2013/04/30 05:54 by dregad