My projects feedback

Hey,
I’ve done my projects on HTML and CSS , I’ve seen that people got reviews on your projects.
how long does it take to get a review?
I’ve done those projects a few weeks ago, but I just made it public and got my
first certification.

edit: my projects -
https://codepen.io/Ayamir/pens/public (this is where all my projects are, can’t put them in separate link because I can put up to 2 links)
https://codepen.io/Ayamir/pen/abZJoqe (with this specific one, I had a problem with my video that I still not sure how to fix)

As well, I do not know how my projects pass even tho I know I have a lot of mistakes there that I need to fix.
When I do the projects there’s the specific tasks that I need to do and I dont see anywhere what I did right and what is wrong.

Thank you!

You have to post the mentioned projects here with link(s) to visit.

i have edited it, thanks!

1 Like

Welcome to the forums @Dya.
To get reviews of their projects user’s open a new topic, put in a link to their project and ask for feedback. It’s not something that is done automatically.
As an aside, this link that you provided (https://codepen.io/your-work) will take user’s to their codepen work, not yours. It’s a generic link.
For people to see your pens they need a link like;
https://codepen.io/Ayamir/pens/public

You should address the concerns below especially the one about getting all the user stories to pass because your projects do not meet the minimum criteria.

Some things to revisit on your pages;

tribute

  • Keep the test script when forking the pen (<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>).
    • The test script should be included, with all tests passing, when you submit your projects.
    • Your page passes 6/10 user stories. Click the red button to see which test(s) are failing and text to help you correct the issue.
  • Codepen provides the boilerplate for you. It only expects the code you’d put within the body element in HTML. (No need to include the body tags). For anything you want to add to the <head> element click on the ‘Settings’ button, then HTML and add it into the ‘Stuff for <head>’ box.
  • Run your HTML code through the W3C validator.
    • There are HTML coding errors you should be aware of and address.
  • Do not use the <br> element to force line breaks or spacing. That’s what CSS is for.
    • if you want multiple paragraphs, use multiple paragraph elements
  • Accessibility is about being accessible to all users. Review the lesson about giving meaningful text to links.
  • Make your page responsive. Remember, the R in RWD stands for Responsive.
    • There’s always a horizontal scrollbar and on smaller screens elements fall out of the container.

survey

  • Again, keep the test script when forking the pen.
    • The test script should be included, with all tests passing, when you submit your projects.
    • Your page passes 8/17 user stories. Click the red button to see which test(s) are failing and text to help you correct the issue.
  • Again, codepen provides the boilerplate
    • The link to the font goes in the box labeled ‘Stuff for <head>’
  • Again, run your HTML code through the W3C validator and clean up the errors
  • Codepen provides validators for HTML, CSS and JS. Click on the down arrow in the upper right of each section and then click on the respective ‘Analyze’ link.
    • The one for CSS is good. Use it, there’s something to clean up.
      • It’s minor but be wary of duplicating properties
    • (The one for HTML misses things which is why I recommend W3C)
  • Do not use the <br> element to force line breaks or spacing. That’s what CSS is for.
  • User’s should be able to click on the label to toggle a selection, not just the radio button / checkbox.
    • this is not working for your radio buttons. Remember, an id must be unique within the document.
  • Change the cursor to a pointer when hovering over the submit button
  • Make your page responsive. Remember, the R in RWD stands for Responsive.

prod landing

  • Keep the test script when forking the pen (<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>).
    • The test script should be included, with all tests passing, when you submit your projects.
    • Your page passes 13/16 user stories. Click the red button to see which test(s) are failing and text to help you correct the issue.
  • Use the W3C validator and clean up the coding errors
  • Make your page responsive. Remember, the R in RWD stands for Responsive.

tech doc

  • Keep the test script when forking the pen (<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>).
    • The test script should be included, with all tests passing, when you submit your projects.
    • Your page passes 13/16 user stories. Click the red button to see which test(s) are failing and text to help you correct the issue.
  • Use the W3C validator and correct the errors
  • Make your page responsive. Remember, the R in RWD stands for Responsive.

portfolio

  • Keep the test script when forking the pen (<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>).
    • The test script should be included, with all tests passing, when you submit your projects.
    • Your page passes 7/12 user stories. Click the red button to see which test(s) are failing and text to help you correct the issue.
  • Use the W3C validator, correct the errors
  • Codepen provides validators for HTML, CSS and JS. Click on the down arrow in the upper right of each section and then click on the respective ‘Analyze’ link.
    • The one for CSS is good. Use it.
2 Likes

Thank you so much for the long reply!
Yeah I’m very new to this and got confused with a lot of things, so I really appreciate it.

I’ve got only 1 question tho, about the test script. I dont really know what it is, or when I’m supposed to use it. I’m trying to google about it and nothing is really clear to me.

The test script is something that FCC has that tests the projects to ensure the user stories have been met. For each of the project you could have;

  1. forked the pen. that would have opened up a blank codepen project for you that contained the test script in the HTML section.
  2. if you chose to do the project in an IDE on your computer, each of the project gave the CDN link to run the test script.

In my feedback I gave the test script. Just copy that whole thing (without the parens of course) and paste it as the first line in the HTML section of your pen. When you do you’ll see a hamburger menu in the upper left. Click to expand it and then select the appropriate project from the dropdown. Run the test. If any tests fail, the button will be red. Click the red button to see which test(s) are failing and text to help you correct the issue. Be sure to read the entire failing message, not just the first line.

Hope that helps.

1 Like