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 trialA X
12,842 PointsPlanning and Anticipating a Project When You're New to Programming
I'm watching Andrew's jQuery video series, and he sets up the steps to "solve" the practice site's problems, but if I was just handed this project and told to "Come up with ways to improve upon the site" I wouldn't have come up with the overlay idea or the alt text and captioning for accessibility (I assume that's what that's for).
So for those more experienced with doing such a project, how does one make sure that you're "covering all your bases"? Like is there a typical/standardized checklist that you reference to make sure a site is improved in a best practices fashion like making sure the JS script is added last to the HTML file, making sure the site is accessible, making sure that your site is built to be viewed in many screen resolutions etc.
I know that the answer is in part practice and experience, but I suppose I'm wondering how one at least makes sure that you have a minimal foundation that you're working off of to build or improve a website.
Adam Fields
Full Stack JavaScript Techdegree Graduate 37,838 PointsAdam Fields
Full Stack JavaScript Techdegree Graduate 37,838 PointsHi Nekilof,
Have you done the HTML and CSS courses on Treehouse before diving into JavaScript? They are worth checking out if you're a beginner.
In most professions, many of the tips and tricks are learned on the job, over years of experience. Some of the best practices you've listed are the core ones, but you should know why you're doing them. For example, you load your scripts at the bottom of your HTML file because you want the page to load before the scripts are run. You can't manipulate the DOM if the DOM hasn't been rendered yet.
Don't get overwhelmed by focusing on what you don't know. Just keep following the courses and taking notes. The biggest takeaway for me from this course is the importance of pseudo code. If you can't write out the steps to solve your problem in plain English, you can't possibly solve it using code. At the end of the day, that's what this is all about - creative problem solving.
Good luck!