Tell us what’s happening:
hello guys!, my page just passed the test, but I want some ways to improve the structure, it,s obvious that the U/X isnt good, but i would like your help to make it professionally to take my experience to the next level
Your code so far
<!-- file: index.html -->
!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale= 1.0">
<title>Technical documentation project</title>
<link rel="stylesheet" href="styles.css">
</head>
<body>
<nav id="navbar">
<header>Markdown documentation</header>
<ul>
<li>
<a class="nav-link" href="#What_is_Markdown">What is Markdown</a>
</li>
<li>
<a class="nav-link" href="#Why_use_Markdown">Why use Markdown</a>
</li>
<li>
<a class="nav-link" href="#How_Does_it_Work">How Does it Work</a>
</li>
<li>
<a class="nav-link" href="#Flavors_of_Markdown">Flavors of Markdown</a>
</li>
<li>
<a class="nav-link" href="#Additional_Resources">Additional Resources</a>
</li>
</ul>
</nav>
<main id="main-doc">
<section class="main-section" id="What_is_Markdown">
<header >What is Markdown</header>
<article>
<p>
<code>Markdown</code> is a lightweight markup language that you can use to add formatting elements to plaintext text documents. Created by John Gruber in 2004, Markdown is now one of the worlds most popular markup languages.
</p>
<p>
Using <code>Markdown</code> is different than using a WYSIWYG editor. In an application like Microsoft Word, you click buttons to format words and phrases, and the changes are visible immediately. Markdown isnt like that. When you create a Markdown-formatted file, you add Markdown syntax to the text to indicate which words and phrases should look different.
</p>
<p>
For example, to denote a heading, you add a number sign before it (e.g., <code># Heading One</code>). Or to make a phrase bold, you add two asterisks before and after it (e.g., <code>**this text is bold**</code>). It may take a while to get used to seeing Markdown syntax in your text, especially if youre accustomed to WYSIWYG applications
</p>
<p>
You can add <code>Markdown</code> formatting elements to a plaintext file using a text editor application. Or you can use one of the many Markdown applications for macOS, Windows, Linux, iOS, and Android operating systems. There are also several web-based applications specifically designed for writing in Markdown.
</p>
</article>
</section>
<section class="main-section" id="Why_use_Markdown">
<header>Why use Markdown</header>
<article>
<p> You might be wondering why people use Markdown instead of a WYSIWYG editor. Why write with Markdown when you can press buttons in an interface to format your text? As it turns out, there are several reasons why people use Markdown instead of WYSIWYG editors. </p>
<ul>
<li>
Markdown can be used for everything. People use it to create websites, documents, notes, books, presentations, email messages, and technical documentation.
</li>
<li>
Markdown is portable. Files containing Markdown-formatted text can be opened using virtually any application. If you decide you dont like the Markdown application youre currently using, you can import your Markdown files into another Markdown application. That’s in stark contrast to word processing applications like Microsoft Word that lock your content into a proprietary file format.
</li>
<li>
Markdown is platform independent. You can create Markdown-formatted text on any device running any operating system.
</li>
<li>
Markdown is everywhere. Websites like Reddit and GitHub support Markdown, and lots of desktop and web-based applications support it.
</li>
</ul>
</article>
</section>
<section class="main-section" id="How_Does_it_Work">
<header>How Does it Work</header>
<article>
<p>Dillinger makes writing in Markdown easy because it hides the stuff happening behind the scenes, but its worth exploring how the process works in general.</p>
<p>When you write in Markdown, the text is stored in a plaintext file that has an .md or .markdown extension. But then what? How is your Markdown-formatted file converted into HTML or a print-ready document?</p>
<p>The short answer is that you need a Markdown application capable of processing the Markdown file. There are lots of applications available — everything from simple scripts to desktop applications that look like Microsoft Word. Despite their visual differences, all of the applications do the same thing. Like Dillinger, they all convert Markdown-formatted text to HTML so it can be displayed in web browsers.</p>
<p>Markdown applications use something called a Markdown processor (also commonly referred to as a “parser” or an “implementation”) to take the Markdown-formatted text and output it to HTML format. At that point, your document can be viewed in a web browser or combined with a style sheet and printed. You can see a visual representation of this process below.</p>
</article>
</section>
<section id="Flavors_of_Markdown" class="main-section">
<header>Flavors of Markdown</header>
<article>
p>One of the most confusing aspects of using Markdown is that practically every Markdown application implements a slightly different version of Markdown. These variants of Markdown are commonly referred to as flavors. Its your job to master whatever flavor of Markdown your application has implemented.</p>
<p>To wrap your head around the concept of Markdown flavors, it might help to think of them as language dialects. People in New York City speak English just like the people in London, but there are substantial differences between the dialects used in both cities. The same is true for people using different Markdown applications. Using Dillinger to write with Markdown is a vastly different experience than using Ulysses.</P>
<p>Practically speaking, this means you never know exactly what a company means when they say they support “Markdown.” Are they talking about only the basic syntax elements, or all of the basic and extended syntax elements combined, or some arbitrary combination of syntax elements? You wont know until you read the documentation or start using the application.</p>
<p>If youre just starting out, the best advice I can give you is to pick a Markdown application with good Markdown support. That’ll go a long way towards maintaining the portability of your Markdown files. You might want to store and use your Markdown files in other applications, and to do that you need to start with an application that provides good support. You can use the tool directory to find an application that fits the bill.</p>
</article>
</section>
<section id="Additional_Resources" class="main-section">
<header>Additional Resources</header>
<article>
<p>There are lots of resources you can use to learn Markdown. Here are some other introductory resources:</p>
<ul>
<li>John Grubers Markdown documentation. The original guide written by the creator of Markdown</li>
<li>Markdown Tutorial. An open source website that allows you to try Markdown in your web browser.</li>
<li>Awesome Markdown. A list of Markdown tools and learning resources.</li>
<li>Typesetting Markdown. A multi-part series that describes an ecosystem for typesetting Markdown documents using pandoc and ConTeXt.</li>
</ul>
</article>
</section>
</main>
</body>
</html>
/* file: styles.css */
html, body{
font-family: Tahoma, sans-serif;
background-color: black;
color: white;
min-width: 300px;
font-size: 62.5%;
}
#navbar{
position: fixed;
min-width: 300px;
width: 20vw;
top:0;
left:0;
height: 100%;
border:2px solid white;
border-top: 0;
}
nav ul {
height: 90%;
overflow-x: hidden;
overflow-y: auto;
padding: 0;
}
nav li {
width: 100%;
position: relative;
border-top: 2px solid white;
}
#navbar a {
display: block;
padding: 1rem 3rem;
cursor: crosshair;
font-size: 14px;
}
#navbar header{
padding-bottom: 20px;
}
main {
margin-left: 35rem ;
margin-bottom: 10vh;
padding: 1rem;
text-align: justify;
}
header{
font-size: 20px;
text-align: center;
}
article {
font-size: 16px;
}
@media (maxwidth: 800px){
main{
color: black;
background-color: white;
}
Your browser information:
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36
Challenge Information:
Technical Documentation Page - Build a Technical Documentation Page