Technical Documentation Page - Build a Technical Documentation Page

Tell us what’s happening:

Describe your issue in detail here.

Your code so far

<!-- file: index.html -->
<!DOCTYPE html>
<html lang="en">
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=0.1">
    <link rel="stylesheet" href="stles.css">
    <title>Technical Documentation Page</titel>
    <main id="main_doc">
      <nav id="navbar"></nav>
      <header>Data Analysis</header>
          <section class="main-section" id="Data_1">
            <header>Data 1</header>
            <p>Information 1</p>
            <p>Information 2</p>
          <section class="main-section" id="Data_2">
            <header>Data 2</header>
            <p>Information 3</p>
            <p>Information 4</p>
          <section class="main-section" id="Data_3">
            <header>Data 3</header>
            <p>Information 5</p>
            <p>Information 6</p>
          <section class="main-section" id="Data_4">
            <header>Data 4</header>
            <p>Information 7</p>
            <p>Information 8</p>
           <section class="main-section" id="Data_5">
             <header>Data 5</header>
             <p>Information 9</p>
            <p>Information 10</p>
/* file: styles.css */

Your browser information:

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36

Challenge Information:

Technical Documentation Page - Build a Technical Documentation Page

Hello @ochayi !

Please tell us what the problem is in your own words.

Learning to describe problems is hard, but it is an important part of learning how to code.

Also, the more you say, the more we can help!

Could you please post the css code, too?


Happy coding!

A small typing error that could happen to all of us.

titel should be title.

Keep up the good progress!

Code has various issues: typo in “styles.css,” incorrect HTML structure, improper use of

  • tags. Review syntax and structure.

  • 1 Like

    @TravisHead5 has provide more detailed guidance.

    Though I noticed other issues, I only addressed your concern on the other post about not being able to see the code.
    My guidance was so you could see the code, as you were concerned you could not see it.
    My mistake.

    Happy coding!

    This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.