snuurtje wrote:I really hope you guys can get me started on this!
grtz, Snuurtje
You want us to come over and poke you with something? 😉
Seriously, you can accomplish this. However, it's a bit of a stretch if you're an absolute newb. What you are trying to create is called a "CMS" (Content Management System). There are plenty of those already (PHPNuke, for example), but it you want to build one, you can. It probably won't be as cool as some of the others, but you can do it.
Break the task up into steps. Here are some of the most basic ones:
Decide about storage. Basically, it's either flat files, or a database. You'll need to learn how to manipulate one or the other, so start practicing.
A protected login. I'd suggest using a session variable to hold a "verified" value once the login is accomplished; the credentials are stored in either the database or a flat file, as noted above. No one can access the following pages unless they have been "logged in".
A "writer" page. This is a form in which you will fill out the information about the article/story/text/content you are adding to the site. The fields on the form will correspond to the values to be written to the database or flat file.
3a. A handler script for #3. This receives the values, verifies them, and places them in the storage system. Optionally, this can be included in the script for #3, but it's a tad more complex in the logic.
An "editor" page. This is where you see what stories/content is in the database or filesystem, can make changes, can delete old stories (or simply "unpublish" or "archive" them), etc. Optionally, this could also be combined with #3, again, adding complexity.
A display page. This page displays the stories in the storage system.
A logout.
I'd suggest that you do some planning, and then come back to the forums when you have specific questions related to the mechanics, or more specific design questions. Good luck, and HTH!