Jump to content


Photo

Planning a php site


  • Please log in to reply
5 replies to this topic

#1 draco2317

draco2317
  • Members
  • PipPip
  • Member
  • 10 posts

Posted 10 August 2006 - 01:35 AM

I am trying to find information when trying to plan a website.  I have read the tutorial here, but would like something more in depth.  Anyone have any suggestions on where to look?

#2 hitman6003

hitman6003
  • Members
  • PipPipPip
  • Advanced Member
  • 1,807 posts

Posted 10 August 2006 - 01:38 AM

What do you mean "trying to plan a website"?

#3 AndyB

AndyB
  • Staff Alumni
  • Advanced Member
  • 5,465 posts
  • LocationToronto

Posted 10 August 2006 - 01:38 AM

Define 'planning a website'.

I thought that meant deciding what content there was and what interaction (if any) there would be between visitors and content, as well as what content (if any) would be dynamically generated and how.
Legend has it that reading the manual never killed anyone.
My site

#4 draco2317

draco2317
  • Members
  • PipPip
  • Member
  • 10 posts

Posted 10 August 2006 - 02:00 AM

Sorry for any confusion.  Basically, what i mean is, for example lets say i am starting a website like one model place, I want to know about planning the code, files, and folders.  I guess what I am trying to says so i am not just sitting at the computer typing random pieces of code, which might work, but would be difficult to maintain, repair, or upgrade.  Im looking at how to plan the code files and folders to its clean and effinecent. Also is there such a thing as commenting too much?

#5 AndyB

AndyB
  • Staff Alumni
  • Advanced Member
  • 5,465 posts
  • LocationToronto

Posted 10 August 2006 - 02:07 AM

Commenting too much? There's no such thing as you'll find out when you want to modify a piece of code that's six months old  ???

I normally have an organization like this for the root folder:

index.php
robot.txt
.htaccess
... and other files ..

then folders ...
/admin - protected folder for anything to deal with database editing etc.
/includes - for top of page/bottom of page with my 'template'
/support - for CSS files, db-conn file, etc.
/images/core - for images NOT related to content
/images/content - for images related to content
Legend has it that reading the manual never killed anyone.
My site

#6 hitman6003

hitman6003
  • Members
  • PipPipPip
  • Advanced Member
  • 1,807 posts

Posted 10 August 2006 - 02:07 AM

how to plan the code files and folders to its clean and effinecent


This is something that is very subjective...what is "clean and efficient" to me, may not be to you.  Generally, I tell people who work for me to do what is logical to them, and just make sure to document everything clearly, which leads me to your second question...

is there such a thing as commenting too much?


If at any point in the future there is the slightest possibility that someone else that may be less proficient will have to maintain your code, then -- generally -- no, you can not comment to much.  You can always go overboard with anything, just keep it reasonable.  When I code, I usually only comment blocks of code so  in the future I can come back and look through the code and remember what I'm doing.  I don't need to comment each and every line and function that I'm doing...for me or for anyone else that I work with, but that may not always be true.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users