public
Description: A simple file-based wiki using markdown
Homepage: http://midhack.co.uk/markdown.php
Clone URL: git://github.com/isofarro/php5-markdown-wiki.git
name age message
file .gitignore Tue May 19 12:22:34 -0700 2009 Absolute barebones show a markdown page [isofarro]
file README.markdown Wed Jun 03 10:36:47 -0700 2009 scope creeping [isofarro]
file index-sample.php Mon Jun 01 11:52:25 -0700 2009 refactoring the request parsing using. partial [isofarro]
file markdown-wiki.php Mon Jun 08 10:18:54 -0700 2009 Fixed case sensitivity in isMarkdownLink method [isofarro]
file markdown.php Tue Jun 02 23:59:03 -0700 2009 Working objectified wikilink callback [isofarro]
directory pages/ Mon Jun 08 10:18:54 -0700 2009 Fixed case sensitivity in isMarkdownLink method [isofarro]
directory tests/ Mon Jun 01 12:55:10 -0700 2009 Got display response working [isofarro]
README.markdown

PHP5 Markdown

A simple wiki built around the standard PHP Markdown class.

Wiki links

Currently I've hacked the link handling methods in the markdown class so that relative paths are treated as wiki page references, but in all cases this relative path is treated as fixed from the wiki root. This hacking should probably be done by extending the Markdown class and overriding or wrapping the necessary methods.

So a link syntax of [My page](myDir/myPage) will be treated as a wiki link and linked to the page {$wikibase}/myDir/myPage}, so looking for a file called myPage.markdown in the directory myDir which is a sub-directory of the document directory.


To-do:

  • Specifying a stylesheet
  • Extract topmost header in document for use as a title
  • Error message handling
  • Documentation of install
  • Version control. Choice between git and self-versioning
  • Override layout rendering with templates
  • Solve mod_rewrite baseUrl - maybe an extra config?
  • History and rollback
  • Allow translations of interface (how are we doing UTF-8 wise?)
  • Search
  • Recent changes page
  • Meta information: categorising, tagging, document title, author
  • Improve test coverage of MarkdownWiki class
  • Tighter/more secure file-update/conflict checking
  • Documentation of layout templates / accessible data structures

Wish list:

  • REST-based API that deals with raw markdown
  • Figure out a better way of extending the base markdown class.

Things to consider:

  • Authentication / login
  • Export/import markdown documents
  • sub-content / shared modules
  • Navigation items
  • Other text-format types ( textframe or textile )