Tell us what’s happening:
Almost passed all the tests except for this one about nav-links. Not sure what the issue is ?!
- Each
.main-sectionshould have anidthat matches the text of its first child, having any spaces in the child’s text replaced with underscores (_) for the id’s.
Your code so far
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title> JS Documentation </title>
<link rel="stylesheet" href="styles.css">
</head>
<body>
<main id="main-doc">
<section class="main-section" id="Introduction">
<header>
<h1>Introduction</h1>
</header>
<div class="underline"> </div>
<p>JavaScript is a cross-platform, object-oriented scripting language. It is a small and lightweight language. Inside a host environment (for example, a web browser), JavaScript can be connected to the objects of its environment to provide programmatic control over them.</p>
<p> JavaScript contains a standard library of objects, such as Array, Date, and Math, and a core set of language elements such as operators, control structures, and statements. Core JavaScript can be extended for a variety of purposes by supplementing it with additional objects; for example:</p>
<ul>
<li> Client-side JavaScript extends the core language by supplying objects to control a browser and its Document Object Model (DOM). For example, client-side extensions allow an application to place elements on an HTML form and respond to user events such as mouse clicks, form input, and page navigation. </li>
<br>
<li> Server-side JavaScript extends the core language by supplying objects relevant to running JavaScript on a server. For example, server-side extensions allow an application to communicate with a database, provide continuity of information from one invocation to another of the application, or perform file manipulations on a server. </li>
</section>
<section class="main-section" id="What_you_should_already_know">
<header>
<h1>What you should already know</header>
<div class="underline"> </div>
<p> This guide assumes you have the following basic background: </p>
<p>
<ul>
<li> A general understanding of the Internet and the World Wide Web (WWW). </li>
<li> Good working knowledge of HyperText Markup Language (HTML).</li>
<li> Some programming experience. If you are new to programming, try one of the tutorials linked on the main page about JavaScript. </li>
<li> A big brain </li>
<li> Some snacks to see you through </li>
</p>
<img src="https://www.tamingtwins.com/wp-content/uploads/2019/07/popcorn-movie-snack-platter-2-500x500.jpg">
</section>
<section class="main-section" id="JavaScript_and_Java">
<header>
<h1>JavaScript and Java</h1>
</header>
<div class="underline"> </div>
<p> JavaScript and Java are similar in some ways but fundamentally different in some others. The JavaScript language resembles Java but does not have Java's static typing and strong type checking. JavaScript follows most Java expression syntax, naming conventions and basic control-flow constructs which was the reason why it was renamed from LiveScript to JavaScript. </p>
<p> In contrast to Java's compile-time system of classes built by declarations, JavaScript supports a runtime system based on a small number of data types representing numeric, Boolean, and string values. JavaScript has a prototype-based object model instead of the more common class-based object model. The prototype-based model provides dynamic inheritance; that is, what is inherited can vary for individual objects. JavaScript also supports functions without any special declarative requirements. Functions can be properties of objects, executing as loosely typed methods. </p>
<p> JavaScript is a very free-form language compared to Java. You do not have to declare all variables, classes, and methods. You do not have to be concerned with whether methods are public, private, or protected, and you do not have to implement interfaces. Variables, parameters, and function return types are not explicitly typed. </p>
</section>
<section class="main-section" id="Hello_world">
<header>
<h1>Hello world</h1>
</header>
<div class="underline"> </div>
<p> To get started with writing JavaScript, open the Scratchpad and write your first "Hello world" JavaScript code: </p>
<code> function greetMe(yourName) { alert("Hello " + yourName); } greetMe("World"); </code>
<p> Select the code in the pad and hit Ctrl+R to watch it unfold in your browser! </p>
</section>
<section class="main-section" id="Variables">
<header>
<h1>Variables</h1>
</header>
<div class="underline"> </div>
<p> You use variables as symbolic names for values in your application. The names of variables, called identifiers, conform to certain rules. </p>
<p> A JavaScript identifier must start with a letter, underscore (_), or dollar sign ($); subsequent characters can also be digits (0-9). Because JavaScript is case sensitive, letters include the characters "A" through "Z" (uppercase) and the characters "a" through "z" (lowercase). </p>
<p>You can use ISO 8859-1 or Unicode letters such as å and ü in identifiers. You can also use the Unicode escape sequences as characters in identifiers. Some examples of legal names are Number_hits, temp99, and _name.</p>
<p> You can declare a variable in three ways. <br> <br> With the keyword var, for example:</p>
<code> var x = 42. </code>
<p> By simply assigning it a value, for example: </p>
<code> x = 42. </code>
<p> Or with they keyword let, for example:</p>
<code> let y= 13.</code>
<p> Here's a little bit more code to help me pass the test</p>
<code> let me = pass.</code>
<br> <br>
</section>
<nav id="navbar">
<header>Technical Documentation Page</header>
<a href="#Introduction" class="nav-link">Introduction</a>
<a href="#What_you_should_already_know" class="nav-link">What you should already know</a>
<a class="nav-link" href="#JavaScript_and_Java">JavaScript and Java</a>
<a href="#Hello_world" class="nav-link">Hello world</a>
<a href="#Variables" class="nav-link">Variables</a>
</nav>
</main>
</body>
</html>
main {
font-family: 'Helvetica';
position: relative;
width: 750px;
min-width: 500px;
max-width: 1000px;
}
body {
background: #cefccc;
}
#navbar {
position: absolute;
top: 0;
border: 2px black solid;
height: 532px;
width: 150px;
background: #cefccc;
}
#navbar header {
font-family: sans-serif;
font-size: 22px;
text-align: left;
font-style: bold;
background-color: #000;
color: #cefccc;
padding-top: 15px;
padding-bottom: 15px;
}
.main-section {
margin-left: 205px;
width: 750px;
border: black 1px solid;
}
p, ul {
font-size: 14px;
background: white;
width: 600px;
max-width: 750px;
text-align: justify;
margin-left: 20px;
}
.nav-link {
display: block;
padding-top: 15px;
background-color: #cefccc;
font-family: 'Courier';
color: #000;
font-style: normal;
text-decoration: none;
}
code {
background-color: #cefccc;
border-radius: 3px;
color: #000;
margin-left: 20px;
}
section {
background-color: white;
}
img {
width: 250px;
border-radius: 10px;
}
h1{
font-family: 'Courier';
font-size: 32px;
margin-left: 20px;
margin-bottom: -2px;
}
.underline {
width: 550px;
border-bottom: 3px #cefccc solid;
margin-left: 20px;
}
@media (max-width: 960px) {
.main-section {
padding: 2rem;
}
}
Your browser information:
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.5 Safari/605.1.15
Challenge: Technical Documentation Page - Build a Technical Documentation Page
Link to the challenge: