Skip to content

RedwanHaitami/fcc-technical-documentation-page

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Technical Documentation Page

HTML technical documentation webpage project created for freeCodeCamp Responsive Web Design Certification.

Preview

the project preview

Live Demo

Check it out on Github Webpages

Objective

Build technical documentation page to serve as instruction or reference for a topic.

Requirements

  • 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-doc element, I can see several section elements, each with a class of main-section. There should be a minimum of 5.

  • User Story #3: The first element within each .main-section should be a header element which contains text that describes the topic of that section.

  • 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.

  • User Story #5: The .main-section elements should contain at least 10 p elements total (not each).

  • User Story #6: The .main-section elements should contain at least 5 code elements total (not each).

  • User Story #7: The .main-section elements should contain at least 5 li items total (not each).

  • User Story #8: I can see a nav element with a corresponding id="navbar".

  • User Story #9: The navbar element should contain one header element 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-link should 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-doc element.

  • 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.