Essential CSS
JavaScript Roadmap
Learn JavaScript
Mastering Web Typography
Practical Astro
Understanding Async JS
Unorthodox Tailwind
API Masterclass
Build and Deploy
The Beginner Freelancer
Real World Node
Profile Billing Logout
Learn JavaScript
Lesson Plan
  1. JavaScript and its ecosystem
    1. Welcome to Learn JavaScript!
    2. What is JavaScript used for?
    3. The JavaScript ecosystem
    4. Varying versions of JavaScript
  2. JS Basics
    1. Linking your JavaScript file
    2. Preparing your text editor
    3. The Console
    4. Comments
    5. On semicolons
    6. Strings, numbers and booleans
    7. Understanding Variables
    8. Understanding Functions
    9. The Flow of a Function
    10. Arrow functions
    11. Intro to objects
    12. If/else statements
    13. Comparing Objects
    14. The NOT operator
    15. Null and Undefined
    16. The BOM and the DOM
    17. Selecting an Element
    18. Changing Classes
    19. Listening to events
    20. Callbacks
  3. Building simple components
    1. How to think like a developer
    2. Starter files and Source codes
    3. Do this for every component
    4. ๐Ÿ›  Off-canvas menu: Building an off-canvas menu
    5. ๐Ÿ›  Modal: Building a Modal
    6. Lessons from the building process
    7. Debugging errors
    8. How to use a linter
  4. Arrays and loops
    1. Introduction to Arrays
    2. Array methods
    3. For loops
    4. The forEach loop
    5. Selecting multiple elements
    6. Nodes vs Elements
    7. ๐Ÿ›  Accordion: Building an accordion
  5. Dom basics
    1. Id, classes, attributes, and tags
    2. Changing CSS with JavaScript
    3. Getting CSS with JavaScript
    4. Changing Attributes
    5. Finding an element's size and position
    6. DOM Traversals
    7. ๐Ÿ›  Tabby: Building Tabby (A Tabbed component)
    8. ๐Ÿ›  Carousel: HTML and CSS
    9. ๐Ÿ›  Carousel: Switching slides with JavaScript
    10. ๐Ÿ›  Carousel: Working the dots
    11. ๐Ÿ›  Carousel: Positioning slides with JavaScript
  6. Events deep dive
    1. The listening element
    2. Default Behaviors
    3. Event propagation
    4. Event delegation
    5. Removing Event Listeners
    6. ๐Ÿ›  Modal: Closing the modal
    7. ๐Ÿ›  Accordion: Event delegation
    8. ๐Ÿ›  Tabby: Event delegation
    9. ๐Ÿ›  Carousel: Event delegation
  7. Transitions and Animations
    1. CSS Transitions
    2. CSS Animations
    3. Silky-smooth animations
    4. Integrating CSS transitions and animations with JavaScript
    5. Animating with JavaScript
    6. GreenSock Animation API (GSAP)
    7. ๐Ÿ›  Off-canvas menu: Animations
    8. ๐Ÿ›  Modal: Animating the modal
    9. ๐Ÿ›  Modal: Animating the pointing hand
    10. ๐Ÿ›  Modal: Animating the waving hand
    11. ๐Ÿ›  Modal: Wave hand animation with JavaScript (using GSAP)
    12. ๐Ÿ›  Accordion: Animations
    13. ๐Ÿ›  Carousel: Animations
  8. Useful JS features
    1. Ternary operators
    2. AND and OR operators
    3. Early returns
    4. Template Literals
    5. Destructuring
    6. Default parameters
    7. Enhanced Object Literals
    8. Rest and Spread
    9. Useful array methods
    10. Looping through objects
    11. Returning objects with implicit return
    12. ๐Ÿ›  Accordion: Using useful JavaScript features
    13. ๐Ÿ›  Tabby: Using useful JavaScript features
    14. ๐Ÿ›  Carousel: Useful JavaScript features
  9. JS Best practices
    1. Write declarative code
    2. Functions with a purpose
    3. Manage scope
    4. Reduce state changes
    5. Don't reassign
    6. Don't mutate
    7. Preventing Objects from mutating
    8. Preventing Arrays from mutating
    9. Write pure functions
    10. ๐Ÿ›  Accordion: Refactor
    11. ๐Ÿ›  Carousel: First refactor
    12. ๐Ÿ›  Carousel: Refactoring the dots part
    13. ๐Ÿ›  Carousel: Previous and next buttons
    14. ๐Ÿ›  Carousel: Second refactor
  10. Manipulating text and content
    1. Changing Text and HTML
    2. Creating HTML Elements
    3. Adding multiple elements to the DOM
    4. Removing Elements from the DOM
    5. ๐Ÿ›  Carousel: Creating dots with JavaScript
    6. ๐Ÿ› ๏ธ Calculator: HTML and CSS
    7. ๐Ÿ› ๏ธ Calculator: Happy Path
    8. ๐Ÿ› ๏ธ Calculator: Testing the Happy Path
    9. ๐Ÿ› ๏ธ Calculator: Easy Edge Cases
    10. ๐Ÿ› ๏ธ Calculator: Difficult Edge Cases
    11. ๐Ÿ› ๏ธ Calculator: Refactoring
    12. The switch statement
    13. ๐Ÿ› ๏ธ Calculator: Refactoring (Part 2)
    14. ๐Ÿ› ๏ธ Popover: Making one popover
    15. ๐Ÿ› ๏ธ Popover: Making four popovers
    16. ๐Ÿ› ๏ธ Popover: Making popovers with JavaScript
  11. Handling Forms
    1. Intro to forms
    2. Selecting form fields with JavaScript
    3. Form fields and their events
    4. Sanitize your output
    5. Generating unique IDs
    6. ๐Ÿ› ๏ธ Popover: Dynamic ID
    7. ๐Ÿ› ๏ธ Todolist: The HTML and CSS
    8. ๐Ÿ› ๏ธ Todolist: Creating tasks with JavaScript
    9. ๐Ÿ› ๏ธ Todolist: Deleting tasks with JavaScript
    10. ๐Ÿ› ๏ธ Typeahead: The HTML and CSS
    11. ๐Ÿ› ๏ธ Typeahead: Displaying predictions
    12. ๐Ÿ› ๏ธ Typeahead: Selecting a prediction
    13. ๐Ÿ› ๏ธ Typeahead: Bolding search terms
  12. Handling Dates
    1. The Date object
    2. Getting a formatted date
    3. Getting the time
    4. Local time and UTC Time
    5. Setting a specific date
    6. Setting a date with Date methods
    7. Adding (or subtracting) date and time
    8. Comparing Dates and times
    9. ๐Ÿ› ๏ธ Datepicker: HTML and CSS
    10. ๐Ÿ› ๏ธ Datepicker: Building the calendar
    11. ๐Ÿ› ๏ธ Datepicker: Building the datepicker with JavaScript
    12. ๐Ÿ› ๏ธ Datepicker: Previous and Next buttons
    13. ๐Ÿ› ๏ธ Datepicker: Selecting a date
    14. ๐Ÿ› ๏ธ Datepicker: Positioning the datepicker
    15. ๐Ÿ› ๏ธ Datepicker: Showing and hiding
    16. Formatting a date with toLocaleString
    17. setTimeout
    18. setInterval
    19. ๐Ÿ› ๏ธ Countdown timer: HTML and CSS
    20. ๐Ÿ› ๏ธ Countdown timer: JavaScript
    21. ๐Ÿ› ๏ธ Countdown timer: Counting Months
    22. ๐Ÿ› ๏ธ Countdown timer: Daylight Saving Time
    23. ๐Ÿ› ๏ธ Countdown timer: Counting Years
  13. Async JS
    1. Introduction to Ajax
    2. Understanding JSON
    3. The Fetch API
    4. Possible data types
    5. JavaScript Promises
    6. Requests and responses
    7. Sending a POST request
    8. Authentication
    9. Handling errors
    10. Viewing response headers
    11. CORS and JSONP
    12. XHR vs Fetch
    13. Using an Ajax library
    14. Reading API documentation
    15. Understanding curl
    16. ๐Ÿ› ๏ธ Todolist: The Todolist API
    17. ๐Ÿ› ๏ธ Todolist: Fetching tasks
    18. ๐Ÿ› ๏ธ Todolist: Creating tasks
    19. ๐Ÿ› ๏ธ Todolist: Editing tasks
    20. ๐Ÿ› ๏ธ Todolist: Deleting tasks
    21. ๐Ÿ› ๏ธ Todolist: Creating tasks with Optimistic UI
    22. ๐Ÿ› ๏ธ Todolist: Handling Optimistic UI errors
    23. ๐Ÿ› ๏ธ Todolist: Editing tasks with Optimistic UI
    24. ๐Ÿ› ๏ธ Todolist: Deleting tasks with Optimistic UI
    25. ๐Ÿ› ๏ธ Todolist: Refactor
    26. ๐Ÿ› ๏ธ Typeahead: How to add Ajax
    27. ๐Ÿ› ๏ธ Typeahead: Adding Ajax
    28. ๐Ÿ› ๏ธ Typeahead: Handling errors
    29. ๐Ÿ› ๏ธ Google Maps Clone: Creating your first Google Map
    30. ๐Ÿ› ๏ธ Google Maps Clone: Fetching JSONP via JavaScript
    31. ๐Ÿ› ๏ธ Google Maps Clone: Drawing directions
    32. ๐Ÿ› ๏ธ Google Maps Clone: Driving directions
    33. ๐Ÿ› ๏ธ Google Maps Clone: Handling errors
    34. ๐Ÿ› ๏ธ Google Maps Clone: Adding stopovers
    35. ๐Ÿ› ๏ธ Google Maps Clone: Refactor
  14. Advanced Async JS
    1. Requesting many resources at once
    2. Asynchronous functions
    3. Handling multiple awaits
    4. Asynchronous loops
    5. ๐Ÿ› ๏ธ Dota Heroes: Listing heroes
    6. ๐Ÿ› ๏ธ Dota Heroes: Filtering heroes (Part 1)
    7. ๐Ÿ› ๏ธ Dota Heroes: Filtering heroes (Part 2)
    8. ๐Ÿ› ๏ธ Dota Heroes: Refactoring
    9. ๐Ÿ› ๏ธ Dota Heroes: Hero Page
    10. ๐Ÿ› ๏ธ Dota Heroes: Making the hero page robust
    11. ๐Ÿ› ๏ธ Dota Heroes: Heroes page refactor
  15. Handling Keyboard Events
    1. Keyboard users
    2. Handling commonly used keys
    3. Keyboard events
    4. Understanding Tabindex
    5. Detecting the focused element
    6. Directing focus
    7. Preventing people from tabbing into elements
    8. How to choose keyboard shortcuts
    9. Creating single-key shortcuts
    10. ๐Ÿ› ๏ธ Off-canvas: Adding keyboard interaction
    11. ๐Ÿ› ๏ธ Modal: Adding keyboard interaction
    12. ๐Ÿ› ๏ธ Accordion: Adding keyboard interaction
    13. ๐Ÿ› ๏ธ Tabby: Adding keyboard interaction
    14. ๐Ÿ› ๏ธ Tabby: Refactoring
    15. ๐Ÿ› ๏ธ Carousel: Adding keyboard interaction
    16. ๐Ÿ› ๏ธ Carousel: Displaying help text
    17. ๐Ÿ› ๏ธ Calculator: Adding keyboard interaction
    18. ๐Ÿ› ๏ธ Popover: Keyboard
    19. ๐Ÿ› ๏ธ Popover: Refactor
    20. Keyboard shortcuts with Command and Control modifiers
    21. ๐Ÿ› ๏ธ Todolist: Keyboard
    22. ๐Ÿ› ๏ธ Typeahead: Keyboard
    23. ๐Ÿ› ๏ธ Typeahead: Selecting a prediction with the keyboard
    24. ๐Ÿ› ๏ธ Google Maps Clone: Keyboard
    25. ๐Ÿ› ๏ธ Dota Heroes: Keyboard
    26. ๐Ÿ› ๏ธ Datepicker: Tabbing in and out
    27. ๐Ÿ› ๏ธ Datepicker: Keyboard shortcuts
  16. Screen reader accessibility
    1. What is accessibility?
    2. How to use a screen reader
    3. Using NVDA
    4. Using Voiceover
    5. Aria roles
    6. Landmark roles
    7. Document structure roles
    8. Live region roles
    9. Widget roles
    10. Window and Abstract roles
    11. Accessible names and descriptions
    12. Hiding content
    13. ARIA properties and ARIA states
    14. ARIA for expandable widgets
    15. ๐Ÿ› ๏ธ Off-canvas: Accessibility
    16. ARIA for modal dialogs
    17. ๐Ÿ› ๏ธ Modal: Screen reader accessibility
    18. ๐Ÿ› ๏ธ Accordion: Screen reader accessibility
    19. ARIA for Tabbed components
    20. ๐Ÿ› ๏ธ Tabby: Screen reader accessibility
    21. ๐Ÿ› ๏ธ Tabby: Refactor
    22. ๐Ÿ› ๏ธ Carousel: Screen reader accessibility
    23. Roles that trigger Forms and Application modes
    24. What's next for accessibility?
  17. Handling Scroll
    1. The Scroll event
    2. ๐Ÿ› ๏ธ Auto-hiding Sticky-nav: HTML and CSS
    3. ๐Ÿ› ๏ธ Auto-hiding Sticky-nav: JavaScript
    4. ๐Ÿ› ๏ธ Auto-hiding Sticky-nav: Natural reveal
    5. Intersection Observer API
    6. Intersection Observer Options
    7. ๐Ÿ› ๏ธ Slide & Reveal
    8. ๐Ÿ› ๏ธ Slide & Reveal: Always fade-in when you scroll down
    9. ๐Ÿ› ๏ธ Slide & Reveal: Fine-tuning the animation
    10. ๐Ÿ› ๏ธ Infinite Scroll: Anatomy
    11. ๐Ÿ› ๏ธ Infinite Scroll: Infinite load
    12. ๐Ÿ› ๏ธ Infinite Scroll: Refactor
    13. ๐Ÿ› ๏ธ Infinite Scroll: Implementing the Infinite Scroll
  18. Mouse, Touch, and Pointer events
    1. Mouse Events
    2. ๐Ÿ› ๏ธ Spinning Pacman: HTML and CSS
    3. ๐Ÿ› ๏ธ Spinning Pacman: JavaScript
    4. Touch events
    5. Pointer events
    6. Touch-action
    7. ๐Ÿ› ๏ธ Spinning Pacman: Supporting Touch
    8. Cloning elements
    9. ๐Ÿ› ๏ธ DragDrop: HTML and CSS
    10. ๐Ÿ› ๏ธ DragDrop: JavaScript
    11. ๐Ÿ› ๏ธ DragDrop: Creating a drop preview
    12. ๐Ÿ› ๏ธ DragDrop: Sortable drop preview
    13. ๐Ÿ› ๏ธ DragDrop: Robustness
    14. ๐Ÿ› ๏ธ DragDrop: Refactor
  19. Object Oriented Programming
    1. Before we begin
    2. What is Object Oriented Programming?
    3. Four Flavours of Object Oriented Programming
    4. Inheritance
    5. This in JavaScript
    6. Call, bind, apply
    7. Creating Derivative Objects
    8. Composition vs Inheritance
    9. Polymorphism
    10. Encapsulation
    11. Closures
    12. Encapsulation in Object Oriented Programming
    13. Getters and Setters
    14. What OOP flavour to use
    15. When to use Object Oriented Programming
  20. Writing reusable code
    1. Creating reusable code by writing libraries
    2. Two Types of libraries
    3. Including libraries with Script tags
    4. Including libraries with ES6 Modules
    5. Dynamic imports
    6. ๐Ÿ› ๏ธ Off Canvas: Building a Library
    7. ๐Ÿ› ๏ธ Modal: Library setup
    8. ๐Ÿ› ๏ธ Modal: Opening the Modal
    9. ๐Ÿ› ๏ธ Modal: Closing the modal
    10. ๐Ÿ› ๏ธ Modal: Inheritance and Polymorphism
    11. ๐Ÿ› ๏ธ Modal: Resolving differences between subclasses
    12. ๐Ÿ› ๏ธ Modal: Exposing properties and methods
    13. ๐Ÿ› ๏ธ Accordion: Building a library
    14. ๐Ÿ› ๏ธ Tabby: Building a library
    15. ๐Ÿ› ๏ธ Carousel: Building a library
    16. ๐Ÿ› ๏ธ Calculator: Library
    17. ๐Ÿ› ๏ธ Calculator: Fixing the Clear Key
    18. ๐Ÿ› ๏ธ Calculator: Handling other keys
    19. ๐Ÿ› ๏ธ Calculator: State
    20. ๐Ÿ› ๏ธ Popover: Library
    21. ๐Ÿ› ๏ธ Popover: Adding event listeners
    22. ๐Ÿ› ๏ธ Typeahead: Library
    23. ๐Ÿ› ๏ธ DatePicker: Library
  21. Going from Vanilla JS to JS Frameworks
    1. ๐Ÿ› ๏ธ Building a Tiny framework
    2. ๐Ÿ› ๏ธ Tiny: Add event listeners
    3. ๐Ÿ› ๏ธ Tiny: Updating state
    4. ๐Ÿ› ๏ธ Tiny: Rendering Child Components
    5. ๐Ÿ› ๏ธ Tiny: Changing Parent State
    6. ๐Ÿ› ๏ธ Tiny: Passing Props
    7. ๐Ÿ› ๏ธ Tiny: Multiple Props
    8. ๐Ÿ› ๏ธ Tiny: Passing values from sibling components
    9. ๐Ÿ› ๏ธ Tiny: Mounting
    10. ๐Ÿ› ๏ธ Tiny: Passing props to descendants
    11. ๐Ÿ› ๏ธ Tiny: A tiny refactor
  22. Single Page Apps
    1. What is a Single Page App?
    2. Simple SPA using only CSS
    3. The Location Interface
    4. The History Interface
    5. Minimum viable server for a SPA
    6. ๐Ÿ› ๏ธ Dota SPA: Introduction
    7. ๐Ÿ› ๏ธ Dota SPA: Building The Heroes List
    8. ๐Ÿ› ๏ธ Dota SPA: Building the filters
    9. ๐Ÿ› ๏ธ Dota SPA: Filtering heroes
    10. ๐Ÿ› ๏ธ Dota SPA: Displaying filtered heroes
    11. ๐Ÿ› ๏ธ Dota SPA: Getting Ready to build the Hero Page
    12. ๐Ÿ› ๏ธ Dota SPA: Building the hero page
    13. ๐Ÿ› ๏ธ Dota SPA: Lore and abilities
    14. ๐Ÿ› ๏ธ Dota SPA: Routing for Single-page apps

๐Ÿ› ๏ธ Dota SPA: Building the hero page

When a user clicks on a hero in Heroes List, we want to direct the user to the heroโ€™s page. This is what we want:

We do this by adding a href that links to the heroโ€™s name, like this:

HeroesList.js
export default Tiny({
// ...
template() {
return `
<!-- Header -->
<main tiny-listener="[filter-heroes, filterHeroes]">
<div class="wrap">
<!-- Title -->
<div class="sidebar-content">
<!-- Filters -->
<div class="content">
<ul class="heroes-list">
${heroes
.map(hero => {
return `
<li>
<!-- Links to each hero here -->
<a href="/heroes/${hero.npcHeroName}">
<span class="hero__name"> ${hero.name} </span>
<img src="${hero.image}" alt="${hero.name} image">
</a>
</li>
`
})
.join('')}
</ul>
</div>
</div>
</div>
</main>
`
},
})

Pay attention to the URL in the href property. We need this URL for the heroโ€™s page to work.

Quick Note about the URL

For the URL, notice we used a url like /heroes/axe instead of /hero/axe? We used a plural form, not a singular form.

We do this because the API convention works this way. Itโ€™s usually a plural verb, followed by a singlular verb. Examples include:

  • /users/:username
  • /posts/:postid

This is why weโ€™re using /heroes/:heroname instead of the singular version. Just highlighting this cause I thought itโ€™s something important you should know.

Detecting and displaying the Hero Page

If the URL is /, we know we should display the Heroes List. If the URL contains /heroes, we know we should display the Hero Page.

We can do this with a simple if statement.

main.js
Tiny({
// ...
template() {
const path = location.pathname
if (path === '/') {
return '<div tiny-component="HeroesList"></div>'
}
if (path.includes('/heroes/')) {
return 'Hero Page!'
}
},
})

When you click on a hero, you should see the hero page content now.

Weโ€™re ready to make the Hero Page Component now.

Making the Hero Page component

The Hero Page Component can be pretty complex, so weโ€™l start by creating a HeroPage folder. Weโ€™ll create a HeroPage.js file and put it inside this folder.

We have to do the usual stuff at this point:

  • Import Tiny into HeroPage.js
  • Export HeroPageso we can use it in main.js
  • Import HeroPage into main.js
HeroPage.js
import Tiny from '../Tiny/tiny.js'
export default Tiny({
template() {
return 'Hero Page!'
},
})
main.js
import HeroPage from './HeroPage/HeroPage.js'
Tiny({
// ...
components: {
HeroesList,
HeroPage,
},
template() {
const path = location.pathname
// ...
if (path.includes('/heroes/')) {
return '<div tiny-component="HeroPage"></div>'
}
},
})

Creating Structure

We already have the HTML for the hero page, so the next step is to put the entire HTML into HeroPage.js.

While doing so, the first thing I noticed is the <body> element has the hero-page class.

<body class="hero-page">
...
</body>

We cannot change the <body> class easily with Tiny, so we will wrap the entire component with a <div> with the same class.

HeroPage.js
export default Tiny({
template() {
return `
<div class="hero-page"></div>
`
},
})

We can now add the header. Make sure to change the image to an absolute URL by adding a / in front of the images/logo.png.

HeroPage.js
export default Tiny({
template() {
return `
<div class="hero-page">
<header class="site-header">
<div class="wrap">
<div class="single-column">
<a href="/">
<img src="/src/assets/learn-javascript/logo.png" alt="Dota 2 Logo" />
</a>
</div>
</div>
</header>
</div>
`
},
})

We can also add the main content which looks like this.

HeroPage.js
export default Tiny({
template() {
return `
<div class="hero-page">
<!-- Header -->
<main>
<div class="wrap">
<div class="single-column flow-2">
<div class="clear site-title">
<h1 data-hero-name></h1>
<img
class="hero__img"
data-hero-image
src="/src/assets/learn-javascript/transparent.png"
/>
<p data-hero-description></p>
</div>
<section hidden>
<h2>Abilities</h2>
<ul class="abilities flow" data-hero-abilities></ul>
</section>
</div>
</div>
</main>
</div>
`
},
})

Nothing will show up for the content because we havenโ€™t added data into it yet. We need to fetch the required data.

Fetching the required data

The Hero Page needs four kinds of data:

  1. Heroes
  2. Hero lore
  3. Abilities
  4. Hero abilities

We already retrieved the first data (heroes) in HeroesList. It makes sense to share this data with HeroPage. An ideal way is to fetch heroes data upfront in main.js, then pass this data into both HeroPage and HeroesList.

Passing Hero Data to HeroesList

We can shift the fetch request from HeroesList.js into main.js.

// Remove this from HeroesList.js.
// Paste this in main.js
async afterMount () {
const dotaApi = 'https://api.opendota.com/api'
const response = await zlFetch(`${dotaApi}/constants/heroes`)
const heroes = Object.values(response.body).map(hero => {
return {
name: hero.localized_name,
npcHeroName: hero.name.replace('npc_dota_hero_', ''),
attackType: hero.attack_type.toLowerCase(),
primaryAttribute: hero.primary_attr,
roles: hero.roles.map(role => role.toLowerCase()),
image: `https://api.opendota.com${hero.img}`
}
})
this.setState({
heroes,
displayedHeroes: heroes
})
}

Weโ€™ll remove displayedHeroes since the parent component in main.js doesnโ€™t need it.

main.js
Tiny({
// ...
async afterMount() {
// ...
this.setState({
heroes,
// Remove this line
displayedHeroes: heroes,
})
},
})

We can pass the state.heroes into HeroesList like this:

main.js
Tiny ({
// ...
template () {
const path = location.pathname
if (path === '/') {
return '<div tiny-component="HeroesList" tiny-props="[heroes, state.heroes]"></div>'
}
// ...
})

We can now get heroes inside HeroesList with prop.

HeroesList.js
export default Tiny({
// ...
template () {
console.log(this.props.heroes)
// ...
}
}

The undefined log shows up because we did not initialize state.heroes inside main.js. Letโ€™s initialize it to an empty array as before.

main.js
Tiny({
// ...
state: {
heroes: [],
},
// ...
})

We need to show the list of heroes in HeroesList now. We can show the initial list using this.props.heroes.

export default Tiny({
// ...
template() {
return `
<!-- Header -->
<main tiny-listener="[filter-heroes, filterHeroes]">
<div class="wrap">
<!-- Site Title -->
<div class="sidebar-content">
<!-- Filters -->
<div class="content">
<ul class="heroes-list">
${this.props.heroes
.map(hero => {
// ...
})
.join('')}
</ul>
</div>
</div>
</div>
</main>
`
},
})

Filtering heroes

To filter heroes, we need to pass props.heroes instead of state.heroes downwards into the Filter component.

HeroesList.js
export default Tiny({
// ...
template() {
return `
<!-- Header -->
<main tiny-listener="[filter-heroes, filterHeroes]">
<div class="wrap">
<!-- Site Title -->
<div class="sidebar-content">
<div class="sidebar flow">
<div tiny-component="Filters" tiny-props="[heroes, props.heroes]"></div>
</div>
<div class="content">
<!-- Heroes List -->
</div>
</div>
</div>
</main>
`
},
})

After filtering, we want to display the filtered heroes. We currently store these inside a state.displayedHeroes.

We know state.displayedHeroes can have one following:

  • 0 heroes โ€” before heroes are fetched
  • Max heroes โ€” if no filters are checked
  • A number between 0 to max heroes โ€” if some filters are checked.

This tell us we can use state.displayedHeroes over props.heroes. But we need to make sure we display all heroes when state.displayedHeroes is 0.

One simple way to do this is create a new variable to store the correct array of heroes we want to display:

export default Tiny({
// ...
template() {
const heroes =
this.state.displayedHeroes.length > 0
? this.state.displayedHeroes
: this.props.heroes
// ...
},
})

We can then use this heroes variable to display heroes.

export default Tiny({
// ...
template() {
// ...
return `
<!-- Header -->
<main tiny-listener="[filter-heroes, filterHeroes]">
<div class="wrap">
<!-- Site Title -->
<div class="sidebar-content">
<!-- Filters -->
<div class="content">
<ul class="heroes-list">
${heroes
.map(hero => {
// ...
})
.join('')}
</ul>
</div>
</div>
</div>
</main>
`
},
})

Phew! Thatโ€™s a lot of refactoring! At this point, the filters should work properly again.

Passing heroes data into Hero Page

We can pass heroes data into Hero Page with tiny-props. This step should be easy for you:

main.js
Tiny({
// ...
template() {
// ...
if (path.includes('/heroes/')) {
return '<div tiny-component="HeroPage" tiny-props="[heroes, state.heroes]"></div>'
}
},
})

We can finally render the heroโ€™s name and image into the Hero Page!

Rendering the heroโ€™s name and image

To render the heroโ€™s name and image, we need to know which hero page weโ€™re on. We can get this information from the URL.

The URL has the following format:

/heroes/:npcHeroName

We need the npcHeroName part from the URL. We can pass /heroes/ into split to split this URL into two. The second portion is what we want.

HeroPage.js
export default Tiny({
template() {
const npcName = location.pathname.split('/heroes/')[1]
// ...
},
})

Once we have npcName, we can find the heroโ€™s information from this.props.heroes.

Now that we have the hero data, we can finally render the heroโ€™s name and image. We do this by extracting the correct data from this.props.heroes

export default Tiny({
template() {
const npcName = location.pathname.split('/heroes/')[1]
const hero = this.props.heroes.find(h => h.npcHeroName === npcName)
console.log(hero)
// ...
},
})

Once we have hero, we can render the heroโ€™s name and image.

export default Tiny({
template() {
const npcName = location.pathname.split('/heroes/')[1]
const hero = this.props.heroes.find(h => h.npcHeroName === npcName)
return `
<div class="hero-page">
<!-- Header -->
<main>
<div class="wrap">
<div class="single-column flow-2">
<div class="clear site-title">
<h1 data-hero-name>${hero.name}</h1>
<img
class="hero__img"
data-hero-image
src="${hero.image}"
/>
<!-- Description -->
</div>
<!-- Abilities -->
</div>
</div>
</main>
</div>
`
},
})

If you refresh the browser now youโ€™ll get an error:

This error happens because hero is undefined. We cannot get a property of an undefined object. The easiest way to circumvent this error is render nothing if โ€˜heroโ€™ is not found.

export default Tiny({
template() {
const npcName = location.pathname.split('/heroes/')[1]
const hero = this.props.heroes.find(h => h.npcHeroName === npcName)
if (!hero) return ''
// ...
},
})

Improving load performance

The Hero Page is empty when we canโ€™t find a hero right now. On a real site, we should still show information (like the logo) even when there is nothing to show.

What we can do is create a function that handles the creation of hero data. This function returns a string that can be used in template. Weโ€™ll call it heroHTML

export default Tiny({
heroHTML(hero) {
return `<div class="single-column flow-2">
<div class="clear site-title">
<h1 data-hero-name>${hero.name}</h1>
<img
class="hero__img"
data-hero-image
src="${hero.image}"
/>
<p data-hero-description></p>
</div>
<section hidden>
<h2>Abilities</h2>
<ul class="abilities flow" data-hero-abilities></ul>
</section>
</div>`
},
// ...
})

If no heroes are found, we simply return an empty string from heroHTML

export default Tiny({
heroHTML(hero) {
if (!hero) return ''
// ...
},
// ...
})

We can use heroHTML like this:

export default Tiny({
template() {
// ...
return `
<div class="hero-page">
<!-- Header -->
<main>
<div class="wrap"> ${this.heroHTML(hero)} </div>
</main>
</div>
`
},
})

Further improvements

We donโ€™t use hero in template at this point โ€” only in heroHTML โ€” so itโ€™s okay to create hero inside heroHTML. If we do this, we donโ€™t have to pass the hero variable into heroHTML.

export default Tiny({
heroHTML() {
const npcName = location.pathname.split('/heroes/')[1]
const hero = this.props.heroes.find(h => h.npcHeroName === npcName)
// ...
},
template() {
return `
<div class="hero-page">
<!-- Header -->
<main>
<div class="wrap"> ${this.heroHTML()} </div>
</main>
</div>
`
},
})

Thatโ€™s it for this lesson!