Spamfunet Nanny Forum

Hey!

We should do something about Nanny's web page.
Or if we cannot due to the security policies, how about creating a new un-official webpage that
could attract new players?

Mats, Carrion, others? What do you think?

Yes, we should make the current work for starters ... Haven't come around to that yet, figured Vulcan and Astrodeath would bring the subject up ...

No idea what has to be done ...

It's a tough subject, a good webpage could help, the current one looks like the whole thing's been abandoned.
If I would know how to, and would have the opportunity I'd also update the design (It is very 90s now. It's ok to not use any modern CMS and keep it all static, but colours, menu items, buttons are probably not forbidden.) and would take a good look on what useful or interesting content can be added (with the least work possible - involve players or use info already existing in the mud).
But then, a site requires constant maintenance as well, the lack of it leads to where we are now. An admin that likes tinkering with web sites would be cool :)

Maybe something like this could work:
- collect ideas for features, layout, content (you admins, then maybe players, although it's tough to say how many will take the time to look at the current page and think about what would be nice)
- make a final list of what's feasible
- maybe prioritize it
- find people to do it.. if it's something that doesn't require admin maybe other wizards/mortals can do it as well. We're just as responsible of this mud as you guys. I'm thinking of the man page xml conversion project for example, that worked. :)
- bug people to finish their work, collect it, correct it, implement it :)

If my post is useless it's ok, I didn't add any less than you two did so far. :) Just saying, as with everything, it will be only done if someone starts doing it, and for minimizing the work 10-20 minutes of planning it wouldn't hurt.

Technology depends on features wanted, about the security concerns, having the server in the right network segment (which is surely already done), maybe chrooting the web server (I also assume this is already done with the mud), and having daily remote backups with perhaps remote syslog would go a long way in minimizing Lysator's risks... if any of this causes a resource problem I'm sure that can be handled as well.