View on GitHub


Remake uses Handlebars.js to render every template. All templates are server-rendered.

Template Variables

These are all the possible template variables you'll have access to in a Handlebars template:

  • appName
    • This is only relevant if you're deploying using Remake's deploy service. It's your unique app name.
  • data
    • This is only loaded on a page that's preceded by a username. so /john or /john/tasks or /john/tasks/3456. It will contain all the data that's in the database for the user that matches the username in the current route.
  • globalData
    • This is static data shared by all templates and all users (loaded from the file app/data/global-app-data.json). It's useful for defining page names for global navigation items or static page titles you want to use for everyone.
  • params
    • These are the url parameters. For example, you can get the username, the pageName, the itemId from here.
  • query
    • This is an object with the all the query parameters in the url.
  • pathname
    • This is the current url's pathname.
  • currentItem
    • If you're at a route like /john/tasks/3456, this will be the item in john's data that matches the id 3456. If no item matching this id is found or you're not at that type of route, this variable will be undefined.
  • parentItem
    • This is the object that's above currentItem in the data. This is useful if you are letting the user browse their data hierarchically and you need to go up a level to the previous item.
  • flashErrors
    • If there are any errors from the previous interaction (e.g. wrong password when signing in), they'll be stored in this array so they can be displayed on the page.
  • flashSuccesses
    • If there are any success messages from the previous interaction, they'll be stored in this array so they can be displayed on the page.
  • currentUser
    • This is an object with the current user's details in it. You can find their username like this: currentUser.details.username and their app data like this: currentUser.appData.
  • pageAuthor
    • This is available only if you're at route like /john or /kate, with a username in it. If you are, this variable will contain the data of user that matches this username. It may be equal to the currentUser.
  • isPageAuthor
    • This is true if the currentUser is also the pageAuthor.
  • pageHasAppData
    • This is true if you're on a page like /john or /kate. Data is loaded from their JSON file database, so it's available on this page. If there's a pageAuthor variable, this will be set to true.

Extra helpers

Remake also ships with all 188 Handlebars Helpers, so you can have lots of flexibility with how you render your data.

Custom #for loop

You may have noticed that the #for loop we use in the tutorial video doesn't use a standard Handlebars block helpers syntax.

We did this for two reasons:

  1. We hook into this custom #for loop in order to make the data-i-new attribute work with it
  2. We prefer #for todo in todos over something like #for todos item="todo" (which would've been more standard).
View on GitHub
☰ Menu