'Certification project complete' but CSS not done


I’d like to know why the Certification Projects say ‘project completed’ when only the html is done and not the CSS?

Many thanks

Please give an example of what you mean. Which project (provide the link) and which code was used (copy the code here)

For example, the Technical Documentation page (although it’s happened with the Tribute page and Survey).
The certification is acccepted without any CSS styling.

<!DOCTYPE html>
<html lang="en">
    <meta charset="UTF-8">
    <link rel="stylesheet" href="styles.css">
    <title>Technical Document</title>
    @media (min-width: 769px) and (max-width: 1024px){
      body {
        font-size: 14px;
      <main id="main-doc">
       <nav id="navbar"><header id="js_documentation">JS Documentation</header>     
  <a class="nav-link" href="#introduction">Introduction</a>    
  <a class="nav-link" href="#what_you_should_already_know" >What you should already know</a>  
<a class="nav-link" href="#java_and_javascript">Java and Javascript</a>
 <a class="nav-link" href="#hello_world">Hello World</a>
 <a class="nav-link" href="#variables">Variables</a>  
<section class="main-section" id="introduction">
  <header id="introduction_header">Introduction</header>
<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>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></ul>
<section class="main-section" id="what_you_should_already_know">
   <header id="what_you_should_already_know_header">What you should already know</header>
<p>This guide assumes you have the following basic background:</p>
<ul><li>A general understanding of the Internet and the World Wide Web (WWW).
<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></ul>
<section class="main-section" id="java_and_javascript">
  <header id="java_and_javascript_header">Java and Javascript</header> 
  <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.</header>Java and Javascript</p>
<section class="main-section" id="hello_world">
   <header id="hello_world_header">Hello World</header>
  <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); }
<p>Select the code in the pad and hit Ctrl+R to watch it unfold in your browser!</p>
<section class="main-section" id="variables">
  <header id="variables_header">Variables</header>
   <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>

This is the css styling.
You included it inline instead of moving it to the css file.
This is still valid code (though not matching the requirement officially).
That is why it was accepted.

I have moved it to CSS, but project still accepted as complete with only media query in CSS code.

The idea behind the certification projects is:

  • For Campers to satisfy the user stories. One of the user stories being:

    • Your Technical Documentation project should use at least one media query.
  • For Campers to add their own personal touch to a project of their own

With that in mind, what problem do you see with the behaviour of the page?

I see the user stories as the skeleton of the project. I build the project around these bare bones, my first objective being to pass all of the requirements, so that I know I’m building it correctly. That’s the easy bit. The tricky bit is then taking the time to flesh it out and make it look as slick as possible.

No problem, thank you

Thanks for the clarification- understood

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