liamoc/dixi

A wiki based on firm theoretical foundations

dixi's Issues

Proper wikilinks support.

Let's do what gitit does and use blank targets for wikilinks.

Also have to make mediawiki wikilinks work etc. Right now they lead to broken links.

Make a hackage release

Latest dixi code allows aeson 0.11, but it's not on hackage it seems. Please make a release.

Customisable stylesheet

dixi-0.6.0.3 build failure with the new base-orphans-0.5.0

Note this can only happen with the old-base flag set to False, which leaves base-orphans unconstrained. base-orphans is required by some of dixi's dependencies, so it is brought into the compilation process either way.

Dixi/Database/Orphans.hs:33:1:
    Duplicate instance declarations:
      instance Foldable Last -- Defined at Dixi/Database/Orphans.hs:33:1
      instance Foldable Last
        -- Defined in ‘base-orphans-0.5.0:Data.Orphans’

Dixi/Database/Orphans.hs:34:1:
    Duplicate instance declarations:
      instance Traversable Last
        -- Defined at Dixi/Database/Orphans.hs:34:1
      instance Traversable Last
        -- Defined in ‘base-orphans-0.5.0:Data.Orphans’

Dixi/Database/Orphans.hs:39:1:
    Duplicate instance declarations:
      instance Data a => Data (Last a)
        -- Defined at Dixi/Database/Orphans.hs:39:1
      instance Data a => Data (Last a)
        -- Defined in ‘base-orphans-0.5.0:Data.Orphans’

Saw this on the 2016-01-18 nightly stackage build, reproduced locally.
Also seen here: http://matrix.hackage.haskell.org/package/dixi#GHC-7.10/dixi-0.6.0.3

Customisable pandoc format (i.e support non-orgmode)

1. Need to add a config setting.
2. Need to figure out how to thread that neatly into the markup generation.

I may want to move the pandoc logic into the server code.

Timestamps

Should be associated with each change, in the Page datatype.

Timezone should be configurable.

Document the JSON API

Configurable timezones

Should have a default for the whole wiki, and a per-user setting once accounts are added.

is there any live instance for users to poke at? :)

Administrator control

Should have the ability to:

• Squash commits
• Kill recent changes from history
• Delete whole pages

LaTeX math

Should check that a version exists before applying a patch to it

Technically the behaviour now is not wrong but it is probably not intended.

JSON API

Using servant, this should be trivial, although I'll definitely need to move the pandoc logic into the server first.

Users and Authentication

It'd be nice to have.

Would require:

• Changes to Page to say who did what changes.
• The addition of sessions, login, authentication (Servant will have this Real Soon Now™).
• Stretch goal: User pages.

Move Pandoc logic into server, out of markup

A bit of technical debt.