Webmasters Stack Exchange is a question and answer site for pro webmasters. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When developing with object oriented code you use an UML diagram to describe all the classes of the program. What about websites?

I have a prototype made with justinmind prototyper so I know how the program looks like and roughly how many webpages I will have, but I will probably have some sort of database in the website, I will also take/receive calls from outside sources.

So how would you model a website, with what method, what is best practice?

share|improve this question

closed as not constructive by John Conde Apr 18 '13 at 11:44

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

I don't think a website is necessarily any different. You can have an OOP/class structure just like a conventional app. – w3dk Apr 18 '13 at 8:10