You are viewing Revision 6 of Future

I will use this page to discuss things that I want to add to Aneuch in the future. Think of this as a "wish list" of sorts.

ACL's

Eventually I want to add site-wide and per page ACL's (Access Control List). This is important to me, personally, because I want to use Aneuch for my personal wiki (which is currently a dokuwiki site). I say it's important, because there are several pages within that wiki that have stuff on them that I don't want the public to see, but that I want to see (work related stuff, mostly).

Additionally, ACL's could be useful in locking a page for editing by anyone. I'm not entirely convinced that there is a practical use for this, but hey, why not. — AaronGraves

Markup

While the Markup engine works, it's quite ugly. Ultimately, I'd like to re-write the markup engine as a state machine. Until I do this, the engine will not be 100% compatible with Creole syntax. (See CreoleTest) — AaronGraves

Admin Section Plugins

I should rewrite the way DoAdmin handles calls to it, so that the Administration back end can be extended via plugins. This will open the doors to new avenues for plugin authors.

This has been done, and it's relatively easy for one to hook into the administration section now (documentation to come). That said, I should do the same now for the way sub Posting handles "POST" data, which will allow plugins to hook in to the post method of the script. This, too, will open up avenues of development. DoPosting has been rewritten to use %PostingActions, which allows us to hook in here as well.

Authentication

Presently Aneuch uses a very rudimentary system for authenticating. There is basically a list of passwords stored in the configuration file. If someone knows any of those passwords, they can log in to the site and do any number of things.

I'd like to change this to use a user+pass combo. This won't be the easiest thing in the world to do, as I'll have to create a system for users to be able to change their own password as well. But I do have some ideas in mind.

Also, I'd like to look at the possibility of using a "tiered access" system. As it is now, if you have a valid password, you can do any number of administrative features to an Aneuch site that some admins may not want all users to be able to do. So I can introduce an "admin" and "editor" level, or something similar. This allows those who have authenticated as an admin to do admin stuffs, and those who are editors will be denied this ability.

Theme Framework

Applying a theme is fairly easy in Aneuch, simply set $Header and $Footer. However, it would be nice to have an actual "framework" which allows a theme to be installed and activated, alongside other themes.

An idea is to have a theme directory under $DataDir, and each theme will then have its own directory within that. A variable can be set in the config file which tells Aneuch which theme to use. Within the folder can be a "Header" and "Footer" file.

Spam

See Spam