I should write a manual or two...
2007-02-25 10:24 pmI've been a productive and good little webmistress for the shire today. I had previously fixed it up so our shire page could handle different kind of activities in a sort of calendar like thing. Today I entered the dates of the spring and summer sewing circles and made a mistake with the typecasting of one of them.
This meant that I now had to sort out the editing and deleting functions which I had previously, err, not done. Because they were boring. Well, I have implemented pretty much the same functionality once before with our Tuesday meetings, so I just had to duplicate my flow and it worked. Didn't take too long.
Now, we can create events, edit and delete them. Hurrah! And by we I mean me (webminister) and the shire Seneschal. Although he has yet to use this functionality. He did do a few Tuesday meetings though.
Anyway, I am now looking again at how I display the contents, and to be frank, I'm not entirely happy. I've got some ideas and have left comments in my code where I meant to add some nifty stuff. Right now, I botched together one little thing that makes things clearer in one sense, but works wierdly for other uses. Clear as mud, I know.
There are times when I hit myself over the head - why do I create misery by insisting on coding this all from scratch when I could have picked a perfectly decent CMS and let it do the work for me. But, doing it myself means I get to control everything, and can tailor it to behave any way I want. It also means I have to write down what I do so someone else can take over at some point.
Ahahahahaha... aaah. I crack myself up.
I haven't done that. I have a few pages written of flows and datastructures and such, in helping me program it, but I don't know how much of that is readily understandable, or readable what with my handwriting. The code itself isn't very complicated though, anyone with half a brain should be able to work it out, and I have commented it - though not exhaustively.
Of course, that's documentation for the code itself, what about user guides? Yeah, even less of that, but hopefully the interface should be simple enough that anyone can use it. So far, the first seneschal who had access to it was able to use it without very much computer savvy, the current one is a former sys-admin so doesn't need much babysitting. But in future? I don't know. Maybe I should test it on some of my non-nerd friends.
I think the biggest problem there is that to update the page you do need to know your way around html. I honestly don't think I can be arsed to code a WYSIWYG editor for the site. And since I myself use a simple text editor (TextPad) for all my webpage mucking-about, my pages aren't really optimized for editor use. Maybe it's time I take the plunge and check out like ... *shudder* FrontP... No, I can't even say it. Let's just drop that line of thought.
This meant that I now had to sort out the editing and deleting functions which I had previously, err, not done. Because they were boring. Well, I have implemented pretty much the same functionality once before with our Tuesday meetings, so I just had to duplicate my flow and it worked. Didn't take too long.
Now, we can create events, edit and delete them. Hurrah! And by we I mean me (webminister) and the shire Seneschal. Although he has yet to use this functionality. He did do a few Tuesday meetings though.
Anyway, I am now looking again at how I display the contents, and to be frank, I'm not entirely happy. I've got some ideas and have left comments in my code where I meant to add some nifty stuff. Right now, I botched together one little thing that makes things clearer in one sense, but works wierdly for other uses. Clear as mud, I know.
There are times when I hit myself over the head - why do I create misery by insisting on coding this all from scratch when I could have picked a perfectly decent CMS and let it do the work for me. But, doing it myself means I get to control everything, and can tailor it to behave any way I want. It also means I have to write down what I do so someone else can take over at some point.
Ahahahahaha... aaah. I crack myself up.
I haven't done that. I have a few pages written of flows and datastructures and such, in helping me program it, but I don't know how much of that is readily understandable, or readable what with my handwriting. The code itself isn't very complicated though, anyone with half a brain should be able to work it out, and I have commented it - though not exhaustively.
Of course, that's documentation for the code itself, what about user guides? Yeah, even less of that, but hopefully the interface should be simple enough that anyone can use it. So far, the first seneschal who had access to it was able to use it without very much computer savvy, the current one is a former sys-admin so doesn't need much babysitting. But in future? I don't know. Maybe I should test it on some of my non-nerd friends.
I think the biggest problem there is that to update the page you do need to know your way around html. I honestly don't think I can be arsed to code a WYSIWYG editor for the site. And since I myself use a simple text editor (TextPad) for all my webpage mucking-about, my pages aren't really optimized for editor use. Maybe it's time I take the plunge and check out like ... *shudder* FrontP... No, I can't even say it. Let's just drop that line of thought.
no subject
Date: 2007-02-25 11:24 pm (UTC)no subject
Date: 2007-02-25 11:28 pm (UTC)no subject
Date: 2007-02-26 01:09 am (UTC)Friends don't let friends use FrontPage!
I use vi myself ....
no subject
Date: 2007-02-26 01:40 am (UTC)I'm sure it's a very useful thing to have. For some. I mean, it surely must be.
I don't know why, but it always warms the cockles of my heart to hear tell of webmasters using a text editor, rather than a website editor. It horrifies me in equal magnitude to see a page using the blink tag. Oh, how I wish that tag would die, die, DIE!
*cough* Right, sorry. Let's move right along...
no subject
Date: 2007-02-26 01:57 am (UTC)I tried a WebPage Editor (tm) once -- it produced Really Crappy HTML which I subsequently re-wrote!
Oh, yeah. I'm so with you on that one.
Oh, look, a CSS script .....