and do different things. But what i'm thinking is simply putting them all in a class called something like Website so they are on one single page rather than individual pages to make the structure cleaner.

Question is though, is this bad practice? Am I using OO properly here or am I just chucking a load of functions into a class (which some people do and others frown upon this) to make things easier for myself?

How would you guys handle a small project like this? Is it wrong to just set up a single class called Website for something like this? Any feedback welcome

How would you guys handle a small project like this? Is it wrong to just set up a single class called Website for something like this? Any feedback welcomeThanks

These are currently separate pages and you want to keep them as separate pages or put everything all on one page?

If you want separate pages, you will either need to rewrite the URL using mod_rewrite and them create a short bit of code to determine which resource is being requested then display that content. Or you will need to create stub files which will then load the appropriate script.

What I started doing is the basic model-view-controller paradigm of sorts. I have two classes, one for the logic and one to display the content, or a template class. The controller part of my script is so short I didn't put it in a class. I also have a separate class for all database accessing.

The request comes in. If it is rewritten, it passes through the controller code to determine which resource is being requested. Then it loads a logic class and then calls the appropriate logic function. Then the logic class loads the template class which outputs the HTML.

Question is though, is this bad practice? Am I using OO properly here or am I just chucking a load of functions into a class (which some people do and others frown upon this) to make things easier for myself?

How would you guys handle a small project like this? Is it wrong to just set up a single class called Website for something like this? Any feedback welcome

It misses the point of OOP entirely. OOP in php is largely about identifying and defining the different aspects of your website (of which there are many) into reusable objects, separating responsibilities, and making future development changes easier. Having one giant 'website' class does not accomplish any of those goals.