Original Post
🔒 Locked
Website help
Advertisement
The first thing that comes to mind is using PHP and MySQL. This would involve setting up a database with a table containing records of upcoming events. Your PHP script would basically connect to the database, select the appropriate table, query 'X' number of rows and then display the content with whatever formatting neccessary.
To have the teachers be able to add their own content you would need to first setup a seperate page with a form containing however many fields you need. From here you'd take the data after it's submitted and run a query to store the new events each in their own record.
Some Googling and a little study and you'll be rolling in an "A+" in no time.
To have the teachers be able to add their own content you would need to first setup a seperate page with a form containing however many fields you need. From here you'd take the data after it's submitted and run a query to store the new events each in their own record.
Some Googling and a little study and you'll be rolling in an "A+" in no time.
Thanks!
I asked my dad (network administrator) and he basically said "MySQL and ASP or PHP"
I asked my dad (network administrator) and he basically said "MySQL and ASP or PHP"
How frequently is the content updated? If it's infrequent (e.g. once or twice a day at most) and done purely from one side of the network (i.e. only from on campus) then the best performance would be from writing network-internal tools that generate static pages. Those tools might use an SQL-based database along with a web scripting language like PHP to work, but if the site isn't fully dynamic and has a limited page count then there's no need to fetch and format data every time anyone makes a request.
The security and maintenance work on having a dynamic website sounds like a pain in the butt if you're going to take off and dump it on someone else's lap.
If the content doesn't change that much, then you should be OK with just static pages; they're also much easier for non-programmers to edit.
If you're going dynamic, consider using something like Drupal or Joomla instead of coding everything by hand.
If the content doesn't change that much, then you should be OK with just static pages; they're also much easier for non-programmers to edit.
If you're going dynamic, consider using something like Drupal or Joomla instead of coding everything by hand.
Just felt I should chip this in. If you intend to go with the PHP/MySQL route, try to make use of a framework, as this will keep things very neat. You do not want to be dealing with spaghetti code, and this is very easy to achieve in PHP. Trust me.
There're several frameworks out there, but I'd recommend CakePHP.
Good luck.
There're several frameworks out there, but I'd recommend CakePHP.
Good luck.
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement