Resoudre un problème, page documentations technique

bonjour, il me signale un problème dans mon code je ne sais pas c’est quoi exactement aidez moi svp, sachant que je suis dans le projet page de documentation technique. Merci d’avance .

https://codepen.io/siham_sissa/pen/vYXJjYV
voila exactement ou j’ai du problème:

there is something wrong with codepen, it seems that the codepen analyzer has blown up

do not worry, you can for example use this one:
https://validator.w3.org/ for your html

and this one https://jigsaw.w3.org/css-validator/validator.html.en for your css

use “validate by direct input” and paste your code there

for the html you can ignore the first 3 things it says, as those are satisfied by the codepen boilerplate

about the boilerplate: remove the body tags as those are already included by codepen

@ilenia, merci de m’avoir répondre,
d’accord merci beaucoup

salut @ilenia,
toujours le même problème j’arrive pas a le résoudre :pensive:

code pen is not working, use the other validators

codepen ne fonctionne pas, utilisez les autres validateurs

juste pour moi ou bien pour tout le monde??

tout le monde

same thing:

d’accord , mille merci a vous. donc on va utiliser les autres validateurs c’est tous.
bon courage .

1 Like

bonjour, il me signale un problème dans mon code je ne sais pas c’est quoi exactement aide moi svp, sachant que je suis dans le projet page de documentation technique. Merci d’avance .

https://codepen.io/siham_sissa/pen/vYXJjYV

1 Like

Hi @siham!

When I run the test suite it says you are failing these four tests.

User Story #4: Each section element with the class of main-section should also have an id that corresponds with the text of each header contained within it. Any spaces should be replaced with underscores (e.g. The section that contains the header “JavaScript and Java” should have a corresponding id="JavaScript_and_Java" ).

User Story #10: Additionally, the navbar should contain link ( a ) elements with the class of nav-link . There should be one for every element with the class main-section .

User Story #12: Each element with the class of nav-link should contain text that corresponds to the header text within each section (e.g. if you have a “Hello world” section/header, your navbar should have an element which contains the text “Hello world”).

User Story #13: When I click on a navbar element, the page should navigate to the corresponding section of the main-doc element (e.g. If I click on a nav-link element that contains the text “Hello world”, the page navigates to a section element that has that id and contains the corresponding header .

The test gives explanations for why each test is failing and how to fix the issue. Open up the test suite to see those errors.

For example:
User story 4 error
Some “main-section” elements are missing the following ids (don’t forget to replace spaces with underscores!)

salut @jwilkins.oboe,
je pense que ce n’est pas ca le problème , parce que au début tout mon code s’exécute normalement, mais toujours ya le meme probleme sur html et en plus pour toutes mes projet . je ne peux pas analyser mes code sur codepen et je ne sais pas c’est quoi le probleme

Oh you didn’t mention the analyzer in your first post.

Codepen is acting weird right now. So you are going to have to run your code through the html validate instead https://validator.w3.org/