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

CSS

Willie Suggs
PLUS
Willie Suggs
Courses Plus Student 5,879 Points
Posted by Willie Suggs
Willie Suggs
Courses Plus Student 5,879 Points

should i fix issues with css & or html code now or wait until project is done & try to sort issues out during debugging

I'm currently on the How to build a website track & all was going well, until i noticed that my page doesn't look like it is shown in the video. My webpage looks very similar but it's not exact, though thus far it seems to function the same. Me being so new to this I'm concerned that if i don't fix theses issues now they my lead to bigger issues later. what would a developer do? I attempted to go back & find the problem but i can't seem to find any difference in the code from the introduction video & my own. I would hate to have to start over from scratch but it seems like it may be my only choice Problems include:

  • bullet points won't leave my images
  • my navigation elements have moved from under my title
  • image caption won't change when new css is applied
  • video shows 6 images in two rows, 3 in each row, but my page has one row with 6 images going straight down

3 Answers

Steven Parker
Steven Parker
229,644 Points
Steven Parker
Steven Parker
229,644 Points

It's a personal workstyle preference, but I find fixing things as I notice them more productive than waiting for a big pile of errors to fix.

The kinds of things you are seeing might be caused by simple typo's. You might try downloading the project code from the course and using a side-by-side text comparison tool to help spot them.

Willie Suggs
Willie Suggs
Courses Plus Student 5,879 Points
Willie Suggs
Willie Suggs
Courses Plus Student 5,879 Points

i found the project code for the css but can't seem to find it for the html...

Andrew Stelmach
Andrew Stelmach
12,583 Points
Andrew Stelmach
Andrew Stelmach
12,583 Points

In a professional environment, many companies (well, the best ones anyway ;-) ) use the Agile methodology; new features are built and considered as one task and isn't considered complete until it is done to a satisfactory standard.

So, one of your features might be "add an About page" - the 'Acceptance Criteria' would likely be the page exists and is styled correctly, and has a link in the nav bar (also styled correctly, according to the Designers' wishes) etc etc. The task would not be considered complete until the acceptance criteria have been satisfied.

So, basically, generally speaking, it's best not to commit something to your git master branch until it is 100% done correctly.