8614db7a32
* feat: use legacy flag chore: reorder challenges fix: linter revert: server change feat: unblock new editor fix: proper order fix: 0-based order fix: broke the order feat: move tribute certification to its own block feat: split the old projects block into 4 fix: put all blocks in order chore: add intro text refactor: use block, not blockName in query fix: project progress indicator * fix: reorder new challenges/certs * fix: reorder legacy challenges * fix: reintroduce legacy certs * feat: add showNewCurriculum flag to env * chore: forgot sample.env * feat: use feature flag for display * fix: rename meta + dirs to match new blocks * fix: add new blocks to help-category-map * fix: update completion-modal for new GQL schema * test: duplicate title/id errors -> warnings * fix: update completion-modal to new GQL schema Mk2 * chore: re-order metas (again) * fix: revert super-block-intro changes The intro needs to show both legacy and new content. We need to decide which pages are created, rather than than what a page shows when rendered. * feat: move upcoming curriculum into own superblock * fix: handle one certification with two superBlocks * fix: remove duplicated intros * fix: remove duplicate projects from /settings * fix: drop 'two' from Responsive Web Design Two * chore: rename slug suffix from two to v2 * feat: control display of new curriculum * feat: control project paths shown on /settings * fix: use new project order for /settings This does mean that /settings will change before the release, but I don't think it's serious. All the projects are there, just not in the legacy order. * fix: claim/show cert button * chore: remove isLegacy Since we have legacy superblocks, we don't currently need individual blocks to be legacy * test: fix utils.test * fix: verifyCanClaim needs certification If Shaun removes the cert claim cards, maybe we can remove this entirely * fix: add hasEditableBoundaries flags where needed * chore: remove isUpcomingChange * chore: v2 -> 22 Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
105 lines
2.5 KiB
Markdown
105 lines
2.5 KiB
Markdown
---
|
|
id: 6165d3b702a5d92ad970b30c
|
|
title: Step 5
|
|
challengeType: 0
|
|
dashedName: step-5
|
|
---
|
|
|
|
# --description--
|
|
|
|
After your `img` element, add an `h1` element with the `class` set to `hero-title` and the text set to `OUR NEW CURRICULUM`, followed by a `p` element with the `class` set to `hero-subtitle` and the text set to `Our efforts to restructure our curriculum with a more project-based focus`.
|
|
|
|
# --hints--
|
|
|
|
You should create an `h1` element.
|
|
|
|
```js
|
|
assert.exists(document.querySelector('h1'));
|
|
```
|
|
|
|
Your `h1` element should come after your `img` element.
|
|
|
|
```js
|
|
assert(document.querySelector('h1')?.previousElementSibling?.localName === 'img');
|
|
```
|
|
|
|
Your `h1` element should have the `class` set to `hero-title`.
|
|
|
|
```js
|
|
assert(document.querySelector('h1')?.className === 'hero-title');
|
|
```
|
|
|
|
Your `h1` element should have the text set to `OUR NEW CURRICULUM`.
|
|
|
|
```js
|
|
assert(document.querySelector('h1')?.textContent === 'OUR NEW CURRICULUM');
|
|
```
|
|
|
|
You should create a new `p` element.
|
|
|
|
```js
|
|
assert.exists(document.querySelector('p'));
|
|
```
|
|
|
|
Your `p` element should come after your `h1` element.
|
|
|
|
```js
|
|
assert(document.querySelector('p')?.previousElementSibling?.localName === 'h1');
|
|
```
|
|
|
|
Your `p` element should have the `class` set to `hero-subtitle`.
|
|
|
|
```js
|
|
assert(document.querySelector('p')?.className === 'hero-subtitle');
|
|
```
|
|
|
|
Your `p` element should have the text set to `Our efforts to restructure our curriculum with a more project-based focus`.
|
|
|
|
```js
|
|
assert(document.querySelector('p')?.textContent === 'Our efforts to restructure our curriculum with a more project-based focus');
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta charset="UTF-8" />
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
|
<title>CSS Grid Magazine</title>
|
|
<link
|
|
href="https://fonts.googleapis.com/css?family=Anton|Baskervville|Raleway&display=swap"
|
|
rel="stylesheet"
|
|
/>
|
|
<link
|
|
rel="stylesheet"
|
|
href="https://use.fontawesome.com/releases/v5.8.2/css/all.css"
|
|
/>
|
|
<link rel="stylesheet" href="styles.css" />
|
|
</head>
|
|
<body>
|
|
--fcc-editable-region--
|
|
<main>
|
|
<section class="heading">
|
|
<header class="hero">
|
|
<img
|
|
src="https://cdn.freecodecamp.org/platform/universal/fcc_meta_1920X1080-indigo.png"
|
|
alt="freecodecamp logo"
|
|
loading="lazy"
|
|
class="hero-img"
|
|
/>
|
|
</header>
|
|
</section>
|
|
</main>
|
|
--fcc-editable-region--
|
|
</body>
|
|
</html>
|
|
```
|
|
|
|
```css
|
|
|
|
```
|