- Keep the test script when forking the pen (
<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>) (if not forking the pen the instructions have the CDN link to use)
- The test script should be included, with all tests passing, when you submit your projects.
- When a test fails click the red button to see which test(s) are failing and text to help you correct the issue. (Be sure and read more than just the first line of the failing message.)
The first failing error message says;
I can see a title with id="title" in H1 sized text.
There should be an element with id="title" : expected null to not equal null
AssertionError: There should be an element with id="title" : expected null to not equal null
Do you understand what the message is telling you and how to correct it?
The rest of the failing messages are just as helpful.
When all the tests are passing you’ll notice the JS you have is not needed.
What do you hate? Really the only difference from not coding locally is that in the HTML editor you only need to add the code that goes between the
body tags. Codepen has a place for you to add
The CSS editor allows choosing a preprocessor, if needed, just from a dropdown, allow setting a base, if needed, by selecting a radio button.
And you don’t have to use codepen. You can use repl.it, codesandbox, yada, yada
A couple of hints about your form;
- do not use the
<br> element to force line breaks or spacing. That’s what CSS is for.
- Run your HTML code through the W3C validator.