HTML technical documentation webpage project created for freeCodeCamp Responsive Web Design Certification.
Check it out on Github Webpages
Build technical documentation page to serve as instruction or reference for a topic.
-
User Story #1: I can see a main element with a corresponding
id="main-doc", which contains the page's main content (technical documentation). -
User Story #2: Within the
#main-docelement, I can see several section elements, each with a class ofmain-section. There should be a minimum of 5. -
User Story #3: The first element within each
.main-sectionshould be aheaderelement which contains text that describes the topic of that section. -
User Story #4: Each section element with the class of
main-sectionshould also have an id that corresponds with the text of each header contained within it. -
User Story #5: The
.main-sectionelements should contain at least 10pelements total (not each). -
User Story #6: The
.main-sectionelements should contain at least 5codeelements total (not each). -
User Story #7: The
.main-sectionelements should contain at least 5liitems total (not each). -
User Story #8: I can see a
navelement with a correspondingid="navbar". -
User Story #9: The navbar element should contain one
headerelement which contains text that describes the topic of the technical documentation. -
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 #11: The header element in the navbar must come before any link (a) elements in the navbar.
-
User Story #12: Each element with the class of
nav-linkshould contain text that corresponds to the header text within each section. -
User Story #13: When I click on a navbar element, the page should navigate to the corresponding section of the
main-docelement. -
User Story #14: On regular sized devices (laptops, desktops), the element with
id="navbar"should be shown on the left side of the screen and should always be visible to the user. -
User Story #15: My Technical Documentation page should use at least one media query.
