The goal of the final project is to make a Content Management System that will dynamically build the website for you, and let you manage it in an easy and convenient way. Obviously, you need to think about the end product - the website - to decide what project you wish to pursue. Will it be a catalog or a journal or a knowledge base? But don't let that final vision distract you from understanding that the project isn't the final website: it is the Content Management System that builds the final website

Website type : TRAVEL BLOG

• What data will your concepts involve?
  • Identify the specific information your site would need to collect, manage and present. For example, a site that will catalog the books in your personal library might need to track title, author, publisher, publication date, isbn number, genre, maybe a keyword field, abstract or summary to aid in searches, etc. An e-commerce site that will provide a catalog of computer parts might need to track categories, manufacturer, model name, model number, price, number in stock, minimum stock number at which you should reorder, etc.
• Identify what functionality, structure and formatting your CMS will need to provide to transform that raw data into content, into useful information.
  • When you are entering your data into the system, what data validation functionality will it require?
  • What management tools will you need?
  • Will there be any workflow functionality, so that submitted data must get approval before being published?
  • Will you need any management reports, for example a list of items with an in-stock number below the re-order threshold?
  • Will data become obsolete and need to be removed or archived?
  • What presentation systems will you use? Which data elements will be presented in the CMS' display sub-system? How will it be organized: alphabetical, categorized, etc.?