More About Project

As I described in the tasks, your site (AT THE END) should have all your programming technologies that you will be learning in some form. But… this will be achieved gradually, by adding new elements with these technologies to your site. At this point, having a front page from any free template site (like the one I showed in W5tasks) and tweaking its content will satisfy week 5 tasks. Do not worry about what is on the Project site now. Just choose the Project concept and what it will be about (some form of e-commerce may be will be easier to fit). You will be more closely working with the site in the following weeks using special Project tasks that will be telling you what elements should be added to your site.

For example, the next week you will have to add at least one of the pages connected to the front page menus that uses embedded and external CSS files (or show how you tweak the css file that came with the template site). Then you will have to show some use of javascript on at least one of the connected to the menu pages (could be the same that shows CSS use). And then in a similar fashion you will be adding technologies learned in the following week. Do not try to design it all now. It will be a dynamically growing project along with your learning of the new material (this is a modern way of designing complex web systems). The requirements/tasks of what technologies should be added to your site (in any from you will choose) will be given each week.

For those who do AWD and TEB projects together – do not try to integrate both parts too tight. It is more work (but, of course, more elaborate integration will be worth more). Best is keeping them separately as supporting resources for each other and simplify the integration like having a menu link from ASP page to the page sitting on the TEB site and vice versa. The user shouldn’t care where the pages are coming from as long as links work. All the code should also work when called from proper pages and the visual presentation of pages should relate to the same Project topic and preferably using similar style. Then it will look like really One Project. But, of course, you might choose to do the same Project Idea as two different sites (for AWD and for TEB) with two different types of technologies (and this might be not that much more work too, and may be even easier to implement).

But, again, my advice is to keep the development, AT THIS point, separately in terms of technologies and just watch for the content and functionality supplementing each other to be used for cross-references later. For example, you will learn Master Pages in ASP.NET, that will do similar stuff as template pages in TEB. These should be kept separately to show that you can use both methods.

You will learn down the road that the site/page that you use on your screen could actually be a bunch of pieces coming from different places and updating themselves at different times, but… this is later not to overwhelm you now.