More about the unnamed Killer App

Alright, since Mr. “I’m Published” Sanders asked…

One of the core features of the app is LDAP authentication. It’s not that hard to do in PHP, but instead of maintaining a robust set of read/write/edit/delete permissions I’m letting LDAP take over. We have a well maintained user directory and I fully intend to utilize it.

The app is a wiki in the sense that any member of the OU has full control over their OU’s site. I’m a member of the Information Services OU, I have full permissions to edit any page on Information Service’s site.

That’s where accountability comes in – the app records who made the last revisions and keeps a copy of the previous state of the site. I’m debating on keeping the last N revisions, just to make it uber accountable.

Other features: Lots and lots of AJAX and a very popping user interface (in terms of response). I’m also offering users file uploads ALA GMail’s file attachment (add another/remove). I’m using the lethal scriptaculous/prototype/behaviour combination. Some screenshots:

app1.png app2.png

The WYSIWYG engine I’m using is FCKeditor with some custom configuration.

Re: WordPress MU

WordPress MU does not have reliable LDAP support that I know of although it’s offered in plugin format. It also does not meet my needs because I will need to integrate it across several domains and combine it with several apps. Basically, each department I work with will have a “stock” set of static pages that are occaisionally updated along with a couple of custom apps that I develop as we go that will need to be integrated into their site. MU also doesn’t have the accountability built in that I desire (that I know of).

I’m not married to the idea of the “Killer App” yet. If there’s something better out there that will meet my very specific needs, let me know.

Advertisements

About andyhillky
I'm cool.

6 Responses to More about the unnamed Killer App

  1. I like the idea of keeping n number of previous versions….maybe just two or three. Have you thought about adding in a more robust workflow, i.e. some sort of approval process?

    I know that has been a big issue with some clients.

  2. bofe says:

    scott,

    Re: Robust Workflow

    I’m not sure the approval process would meet our needs. The VAST majority of the ones updating the sites are the ones who would approve it in the first place. Maybe e-mail notification that a change has occured to someone in the OU would be useful, with links to the changes.

  3. Thats right…what Chris Sanders wants, Chris Sanders gets. Now I want you to put it on a web server accessible from outside your network and make me an account I can play around with ๐Ÿ˜€

    PS. Craig I am going to look into the thing you showed me. I guess the main thing I am concerned about is ease of use by the teachers, ease of administration and setup, and reliability. LDAP authentication isn’t a must, but is pretty nice. I’m not asking too much am I? ๐Ÿ™‚

  4. bofe says:

    Just to update you Scott, the app now sends the administrator an e-mail notifying who revised what, and it keeps N copies around. I’m just writing to an archives folder with a timestamp- for instance

    /archives/site-id/page-name.324974988965

    Chris,

    I would look into WordPress MU if the LDAP auth isn’t a must. It’s pretty easy to use and there’s a lot of training/support material already out there.

  5. poptatr says:

    Wow… looks great. I think that everyone will be quite impressed. FCK is already in use in a few places and with the toolbars we used when I was there, its almost like a web version of Word. I think most people will use it. You might want to figure out a way to clean up code since some people will inevitably paste from Word.

    All in all though, very nice.

  6. bofe says:

    Thanks, poptatr. When I start training people on how to use the app, I will hopefully coach them into using the “Paste from Word” button, which does about as good of a job as any with regards to stripping MS-Word-HTML cruft.

%d bloggers like this: