Good start, need more guidance now!

ClaytonBellmor

I finished zend.com's PHP 101. It was very helpful.

I figure now I should start working on a project and I have something in mind, so now I need some guidance on where to begin.

I want to create a website that will allow users to register and create schedules.

So how should I begin this endeavor? I'd like to not use a huge CMS program and add my own module inside for my purpose.

Again, I'm very new to this. I have a little experience and some basic knowledge.

Thanks,

Clayton

NogDog

I would start by thinking about what data will need to be stored and manipulated in your database, and how to organize and structure it. If you get the data design right, much of the rest of the project is easier to design and implement.

ClaytonBellmor

I've put together the different fields I'll need to use. I've been working on this for a few months now from a design pov so I know what I'll need.

Now, should I be looking at this from a mysql stand-point of what tables I'll need or from a PHP view of what functions, arrays, variables and other things I might need?

I'm feeling very uneasy about the transition from "think about how it should work" to "start coding". I guess I really don't know how to jump in yet.

I've created a horrifyingly demented and ugly beast of a PDF to perhaps help explain phase one of my first php project. I can't stress the 8 minutes of work that went into it. It should show what information I'll need to store, not the steps in between. http://claytonbellmor.com/phpbuilder/phaseone.pdf

-Clayton

PS I really am appreciate of the immense help I've been receiving. Thanks for taking your time to help.

dougal85

Yes, think about how you will store the information in a database so that it makes the most sense.

Also make sure you have a clear plan of the website layout in your head. Something like this tool might help to visualize this: http://www.writemaps.com/

If this is a personal project try to make very clear, strict and achievable goals. I know from my experience and the experience of others that I often start to wander from my original goal. I keep thinking 'oh i can add this, that would be cool' and before you know it the website never gets finished and eventually you get sick of it. If its for somebody else or has a specific deadline this can help.

In terms of planning your code, how do you want to do it? Object oriented or procedural? Start to think about all the things you want to be able to do.

Say for example you have a News section you will want to be able to add, update, delete news.

ClaytonBellmor

That website you sent me to, writemaps.com, is almost exactly what I'm trying to create.

To me, writemaps.com has two sections: the registration/session saving and the actual application of creating website maps (which looks like javascript to me).

So here's a new question: If you were recreating writemaps.com would you start with creating the registration page and session-saving code or with the actual application?

This should help me ease into the coding process.

-Clayton

bpat1434

When I personally develop sites (for myself or at work) I take it through this process:

Conceptual talks :: What they want, how they want it to look, no idea too out there.
Workable Design :: I tell them what is and isn't possible (design wise or code-wise)
Clearly defined Goals :: Defined check-points are in place so that they know where I am, and I know where I'm expected to be.
Templating :: I usually have a good idea of what's to be done, so here it's just a matter of making sure the design will work.
Code Conceptualization :: Work out what functions you'll want to use (and what names) and how users will authenticate and carry themselves from page to page.
Basic User Interface :: I start with what everyone (non-authenticated) users will see. This is the very basic stuff.
Authenticated Users :: I then move on to when users are logged in and add functionality.
Extra Frills / Last Minute Changes :: I add in some padding for extra frills (like some nifty AJAX work) or last minute changes (like using sha1 instead of md5 for password hashing).

That's just me personally. But it sounds to me like you know what you want. You just need to decide where to start. I say start with something easy that you know you can get done. Like perhaps if you're going to use a templating system, you create your templates and templating code first. Get that done and out of the way. Then move on to other things. If you're not using a templating system, I'd start with what everyone will see from your site. Unless you have good reason, you're not going to expect everyone to log in from your main index.php site 😉 So develop what you need for users to see news, upcoming items, product information and the like. Then move on to the users sections where they create the schedules, and then move into the area where you add the content. But that's just my personal preference.

Hope it helps in some way.

ClaytonBellmor

Thanks for the post, it helped a lot.

I like your idea and it makes sense looking down the road. Good thing this website is just for me as a project.

I guess I'll build the non-authenticated user sections: front page, product tour, etc.

Next time you hear from me it will be able where to start with the coding. Thanks again.