Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Steve Seebart
Courses Plus Student 11,897 PointsSeparation of content and presentation
The framework approach appears to violate the basics we learned earlier: the separation of content and presentation. Many of the elements in this sample site define color, margins, padding and even display properties right in the html. In some cases, like the call to action button in these lessons, this leads to long strings of classes to position the element on the page. In others, like the columns, identical code is copied and pasted among the many div elements for padding, margin and layout. For a single page, I guess that's ok, but for a larger site, wouldn't maintenance and updates be virtually impossible?
2 Answers
varlevi
8,113 PointsGood question! I really think it all boils down to, like you touched on, what the framework is being used on. If you are developing a large website, frameworks are probably a bad idea. On the other hand, a smaller page or a page with a time-sensitive deadline would be much better uses of a framework. Frameworks are also great for prototyping or creating early versions of a project with. For example, you may be wanting to start an open source project. Chances are, you won't be being paid until the project is better-established. Until that time, it might be a good idea to save time and use a framework - unless, of course, you actually find it is causing more trouble than is worth it.
This is just my take on the topic.. If you want a more in-depth answer, I highly recommend this article from the Mozilla website. Hope this helps!
Steve Seebart
Courses Plus Student 11,897 PointsThanks for the article link--it points out much that I was thinking during this course. Many years ago, MS FrontPage played the same role as today's frameworks. It promised fast, easy development, but also resulted in clunky, heavy, heard to maintain sites. I'll stick with rolling my own (though I appreciate this course for introducing me to the topic).
varlevi
8,113 PointsI came to the same conclusion. Plain old HTML, CSS, and JavaScript for me!