Wiki Site TODO

From PC-BSD Wiki
Revision as of 19:20, 5 March 2012 by Tigersharke (Talk | contribs)

Jump to: navigation, search

Contents

This page is a list of things that need to be added/changed in relation or in addition to an update of the wiki software.
Note: There have been recent updates; applied changes checked and listed below.

Site Specific

These things are external to the use or running of the Wiki Software. Adjustments in this section may affect access or function of the wiki site as a whole.

Add

  1. HTTPS connections & HTTPS site login
    Banks and lending institutions, email services, and social media, have all turned toward greater security. There is little reason why we should not also protect the logins of our users similarly. It should at least be an option for those users who choose to take advantage of it.

Tweak

  1. Software Updates ✓
    The elephant in the room :)
    If you peek at Special:Version you will discover how out of date things have become.
    Newer versions tend to eliminate bugs and enhance or add features.
    • Extension:Translate ✔
      According to the MediaWiki Extension:Translate page, Translate extension is using continuous development model, which means we are not doing any releases. You should get the latest version from svn and update from time to time to get new features and bug fixes.
  2. Add or fix the website favicon ✓
    Currently Firefox shows a dashed-line empty box, and Chrome substitutes a generic world icon. It will be good to assist recognition by having a similar icon as the PC-BSD forums site.


Wiki Software

These things affect the user experience as directly related to MediaWiki.

Add

Extensions

  1. CentralAuth
    At the very least, this may be useful for accounts between FreeNAS and PC-BSD, and would also mean the chance for common block/ban lists.
    According to the MediaWiki Extension:CentralAuth page, allows global/shared accounts between projects. This extension adds seven new special pages — Special:AutoLogin (unlisted special page), Special:CentralAuth, Special:GlobalGroupMembership, Special:GlobalGroupPermissions, Special:WikiSets, Special:GlobalUsers and Special:MergeAccount.
  2. DoubleWiki ✔
    This would be quite helpful for the translators.
    According to the MediaWiki Extension:DoubleWiki page, Allows you to compare wikis in two separate languages side by side. For an example, see http://fr.wikisource.org/wiki/Criton_(trad._Cousin)?match=en
  3. Cite ✔
    This may help to speed publishing of the wiki into the handbook formats, by using this function for URL footnotes.
    According to the MediaWiki Extension:Cite page, allows a user to create footnotes. Cite includes several extensions which can be installed independently and operate independently of each other.
  4. Collection
    This seems to allow more flexibility for publishing/export on a per user basis.
    According to the MediaWiki Extension:Collection page, This extension allows a user to organize personal selections of pages in a collection. Collections can be (some features require additional extensions) edited and structured using chapters, persisted, loaded and shared, rendered as PDF, exported as ODF Text Document, exported as DocBook XML, ordered as a printed book at http://pediapress.com/, exported as ZIM file.
  5. ParserFunctions ✔
    This would allow for more complex/functional templates which could also automate some parts and obviate some assignments when the template is transcluded, such as: {{tbl-cell|bg=ee|align=left|content=This is the text in a table cell}} Our spiffy tables have alternating white/grey rows which in the prior example with use of parser functions, could be determined by the row number (a detail also helpful when viewing the source), instead of assigning the color every time the template is called.
    According to the MediaWiki Extension:ParserFunctions page, enhances parser with logical functions. Starting with revision 50997 it also incorporates most (but not all) features of the StringFunctions extension, which may be enabled or disabled.

Remove

Parser

  1. Automatic URL recognition
    A URL of whichever type, should require the proper wiki syntax surrounding it. (ie. [http://freebsd.org] instead of http://freebsd.org )
    If this can be adjusted with the help of an extension or if it is simply a minor tweak of the parser, is not known, but it makes sense to limit/constrain function of URL entities.

Configuration

  1. Remove some wiki skins - Proposal
    It may reduce the time it takes to maintain a consistent site if there are fewer skins.
    For each skin it may be necessary to verify the function and appearance of site revisions.
    Which of the following?
    • Chick
    • Classic
    • Cologne Blue
    • Modern
    • MonoBook ⇦ Current default
    • MySkin
    • Nostalgia
    • Simple
    • Vector

Tweak

CSS

  1. Add class for NavHeader and/or other headers
    It may be nice to have a stylesheet item which enables the shift of the page title where NavHeader is used.
    This would avoid the kludge that we are using currently which is simply a negative margin shift, and is certainly imperfect- if you notice the Java, Flash & Fonts page, it doesn't cover all of the 'J' and for redirects, it causes another problem, as well as trying to traverse history of a page.

Configuration

  1. Reduce the number of available 'skins'
    Vector is the nicest/sharpest skin, but the default (MonoBook) is also reasonable and uses the same general format, which means that CSS designed for use with one, should work with the other, and the NavHeader 'kludge' is effective for both.
    Not all skins include the PC-BSD Logo as shown in the upper left corner in MonoBook or Vector.
  2. Make Vector the default skin
    As the sharpest-looking skin, it would present the best image to the public.
  3. Allow user-defined CSS
    This will help those who desire something other than the reduced selection of skins proposed. It may also aid with testing future css layout changes (as suggested above for NavHeader).
    Further investigation of this may be needed, in order to be sure it is not something that might enable an exploit of anything.
  4. E-mail authentication
    This may help to reduce the amount of spam on the wiki, and facilitate a level of automatic accountability.
    Except for password reminder e-mails, e-mail functions only work for authenticated e-mail ($wgEmailAuthentication = true) This is already true.
  5. Restrict editing
    This may help to reduce the amount of spam on the wiki, and facilitate a level of automatic accountability.
    Require e-mail verification before editing certain pages ($wgEmailConfirmToEdit = true).

Recent Changes

Update: 03-05-2012

  • Media Wiki has been updated to version 1.18.1
  • Translate extension for MediaWiki has been updated to version: ‘2012-02-26’
  • Added:
    • favicion from forums.pcbsd.org
    • DoubleWiki
    • Cite
    • ParserFunctions