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>
140 lines
3.8 KiB
Markdown
140 lines
3.8 KiB
Markdown
---
|
|
id: 61438b5b66d76a6264430f2a
|
|
title: Step 10
|
|
challengeType: 0
|
|
dashedName: step-10
|
|
---
|
|
|
|
# --description--
|
|
|
|
Within each of your new `a` elements, add an `i` element and give them the following classes:
|
|
|
|
- Your first `i` element should have the class `fab fa-facebook-f`
|
|
- Your second `i` element should have the class `fab fa-twitter`
|
|
- Your third `i` element should have the class `fab fa-instagram`
|
|
- Your fourth `i` element should have the class `fab fa-linkedin-in`
|
|
- Your fifth `i` element should have the class `fab fa-youtube`
|
|
|
|
# --hints--
|
|
|
|
You should have five `i` elements.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('i')?.length === 5);
|
|
```
|
|
|
|
Each `a` element should only have one `i` element.
|
|
|
|
```js
|
|
const aaaaa = [...document.querySelectorAll('.social-icons a')];
|
|
assert(aaaaa?.every(a => a?.children?.length === 1 && a?.children?.[0]?.localName === 'i'));
|
|
```
|
|
|
|
Each `i` element should have a `class` attribute which includes `fab`.
|
|
|
|
```js
|
|
const iiiii = [...document.querySelectorAll('i')];
|
|
assert(iiiii?.every(i => i?.classList?.contains('fab')));
|
|
```
|
|
|
|
The first `i` element should have a `class` attribute which includes `fa-facebook-f`.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('i')?.[0]?.classList?.contains('fa-facebook-f'));
|
|
```
|
|
|
|
The second `i` element should have a `class` attribute which includes `fa-twitter`.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('i')?.[1]?.classList?.contains('fa-twitter'));
|
|
```
|
|
|
|
The third `i` element should have a `class` attribute which includes `fa-instagram`.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('i')?.[2]?.classList?.contains('fa-instagram'));
|
|
```
|
|
|
|
The fourth `i` element should have a `class` attribute which includes `fa-linkedin-in`.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('i')?.[3]?.classList?.contains('fa-linkedin-in'));
|
|
```
|
|
|
|
The fifth `i` element should have a `class` attribute which includes `fa-youtube`.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('i')?.[4]?.classList?.contains('fa-youtube'));
|
|
```
|
|
|
|
# --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>
|
|
<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"
|
|
width="400"
|
|
/>
|
|
<h1 class="hero-title">OUR NEW CURRICULUM</h1>
|
|
<p class="hero-subtitle">
|
|
Our efforts to restructure our curriculum with a more project-based
|
|
focus
|
|
</p>
|
|
</header>
|
|
<div class="author">
|
|
<p class="author-name">
|
|
By
|
|
<a href="https://freecodecamp.org" target="_blank" rel="noreferrer"
|
|
>freeCodeCamp</a
|
|
>
|
|
</p>
|
|
<p class="publish-date">March 7, 2019</p>
|
|
</div>
|
|
--fcc-editable-region--
|
|
<div class="social-icons">
|
|
<a href="https://www.facebook.com/freecodecamp/">
|
|
</a>
|
|
<a href="https://twitter.com/freecodecamp/">
|
|
</a>
|
|
<a href="https://instagram.com/freecodecamp">
|
|
</a>
|
|
<a href="https://www.linkedin.com/school/free-code-camp/">
|
|
</a>
|
|
<a href="https://www.youtube.com/freecodecamp">
|
|
</a>
|
|
</div>
|
|
--fcc-editable-region--
|
|
</section>
|
|
</main>
|
|
</body>
|
|
</html>
|
|
```
|
|
|
|
```css
|
|
|
|
```
|