You'll learn how different concepts of Gustwind go together on this page. It's self-similar in many ways and if you are familiar with technologies such as HTML, Tailwind, or React, likely you'll get used to it fast.

At its core, the page engine is an interpolating template interpreter that allows data binding. That means there's special syntax for connecting data with your pages and components. The data binding itself happens at routing level and here we focus on the component and layout level.


To give you a simple example of a component, consider the following example for a link that is able to bold itself if it's matching to the path of the current page:


  &visibleIf="(get props href)"
  &class="(concat underline ' ' (pick (equals (trim (get props href) /) (trim (get context url) /)) font-bold))"
  &href="(validateUrl (get props href))"
  &children="(render (get props children))"


import type { Routes } from "../../types.ts";

function init({ routes }: { routes: Routes }) {
  function validateUrl(url: string) {
    if (!url) {

    const [urlRoot, anchor] = url.split("#");

    if (Object.keys(routes).includes(urlRoot)) {
      return urlRoot === "/"
        ? url
        : `/${urlRoot}${anchor ? "#" + anchor : "/"}`;

    // TODO: This would be a good spot to check the url doesn't 404
    // To keep this fast, some kind of local, time-based cache would
    // be good to have to avoid hitting the urls all the time.
    if (url.startsWith("http")) {
      return url;

    throw new Error(
      `Failed to find matching url for "${url}" from ${
        Object.keys(routes).join(", ")

  return { validateUrl };

export { init };

A navigation component built on top of SiteLink could look like this:


<SiteLink href="modes">Modes</SiteLink>
<SiteLink href="configuration">Configuration</SiteLink>
<SiteLink href="routing">Routing</SiteLink>
<SiteLink href="concepts">Concepts</SiteLink>
<SiteLink href="templating">Templating</SiteLink>
<SiteLink href="deployment">Deployment</SiteLink>


The following example illustrates the usage of utilities:


  <slot name="content">
    <div class="md:mx-auto px-4 md:px-0 w-full lg:max-w-3xl prose lg:prose-xl">
      <ul &foreach="(get context blogPosts)">
        <li class="inline">
            &children="(get props data.title)"
            &href="(urlJoin blog (get props data.slug))"


Gustwind layouts are technically components:


  <slot name="content">
    <header class="bg-gradient-to-br from-purple-200 to-emerald-100 py-8">
      <div class="sm:mx-auto px-4 py-4 sm:py-8 max-w-3xl flex">
        <div class="flex flex-col gap-8">
          <Heading level="1" class="text-4xl md:text-8xl">
            <span class="whitespace-nowrap pr-4">🐳💨</span>
          <Heading level="2" class="text-xl md:text-4xl font-extralight">
            Deno powered website creator
      class="md:mx-auto my-8 px-4 md:px-0 w-full lg:max-w-3xl prose lg:prose-xl"
      &children="(get context readme.content)"

The same idea can be used to implement an RSS feed.


<?xml version="1.0" encoding="utf-8" ?>
  <title &children="(get context meta.siteName)"></title>
  <id &children="(get context meta.url)"></id>
  <link rel="alternate" &href="(get context meta.url)" />
  <link rel="self" &href="(urlJoin (get context meta.url) atom.xml)" />
  <updated &children="(dateToISO (get context meta.built))"></updated>
  <noop &foreach="(get context blogPosts)">
      <title &children="(get props data.title)"></title>
        &href="(urlJoin (get context meta.url) blog (get props data.slug))"
      <id &children="(get props data.slug)"></id>
      <published &children="(dateToISO (get props"></published>
      <content type="html" &children="(get props data.description)"></content>


function init() {
  function dateToISO(date: string) {
    return (new Date(date)).toISOString();

  return { dateToISO };

export { init };