A free static site generator

Easily transform Markdown files into a static website. Anyone can use it.



Strike3 is a static site generator. Put simply, Strike3 takes a folder of Markdown files and a theme (a collection of HTML files) and uses those to create a completely self-contained website. Strike3 is the name of the engine and strike3 is the name of the command line tool. It’s written in Xojo.


Although Xojo is cross-platform, currently only macOS and Windows (64-bit) are supported. Linux support is planned with installation to be handled by a Snap.


On macOS, you can use the excellent Homebrew package manager to quickly install Strike3:

brew tap gkjpettet/homebrew-strike3
brew install strike3

You can make sure that you’ve always got the latest version of Strike3 by running brew update in the Terminal. You’ll know there’s an update available if you see the following:

==> Updated Formulae
gkjpettet/strike3/strike3 ✔

To install it simply type brew upgrade in the Terminal.


The easiest way to install Strike3 on Windows is with the Scoop package manager.

scoop bucket add strike3
scoop install strike3


Let’s get you up and started with a simple blog. The blog will list posts on the home page and contain just a single page. I’ll assume you’ve already installed Strike3 as described above.

Step 1: Create the basic site framework

Strike3 has a simple command for creating a new site that will create all the required files/folders for you to get working. Navigate the filesystem to where you want your site to be stored and execute the following command:

$ strike3 create site my-blog

If everything is well, you should see something like the following:

Success ✓
Your new site was created in /Users/garry/Desktop
A single post and a simple page have been created in /content. 
A simple default theme called 'primary' has been created for you in /themes.
Feel free to create your own with `strike3 create theme [name]`.

You can check out the contents of your new site with ls:

config.json   content   scripts   storage   themes

As you can see, a Strike3 site has a very simple basic structure: four folders, a configuration file and a SQLite database. Let’s look at them one-by-one:


Every website must have a configuration file at its root in JSON format. The settings within config.json apply to the whole site. Required and valid options are detailed in the configuration section. Additionally, you can provide site-wide data that’s accessible from themes in this file.


As the name suggests, this is where you store the content of your website. Inside content/ you create folders for different sections. Let’s suppose our blog has three types of content: posts, reviews and tutorials. You would then create three folders in content/ titled post/, review/ and tutorial/ (note I’ve used the singular form of the word as it looks better in the resultant URLs). The name of the section is important as it affects not only the final URL but also the styling applied to the page by the theme (as themes can style sections differently from one another if you wish). A simple blog doesn’t require any sections, you can just place Markdown files in the root of the content/ folder too if you wish.


After Strike3 builds your site, it will run any script files that you place in this folder. The scripts must be written in Xojoscript and have the file extension .xojoscript. You can read more about this functionality in the scripting section.

This is a SQLite database which is used to cache your content for faster building. You shouldn’t really ever need to edit this.


Any file or folder you place in here will be copied to /public/storage in the built site. This is a good location to put images, etc.


This is the folder to place themes that you have created or downloaded. They are then applied by specifying their name in config.json (read more about themes here).

Step 2: Add content

Helpfully, when creating a new site, Strike3 also creates some dummy content for us. Strike3 creates a post called Hello in content/ and a simple about page in /content/about/. You can keep and edit these or delete them and add your own content. Just use your favourite editor (I use Sublime Text).

If you open up the sample post created by Strike3 (/content/Hello, you’ll see an example of (optional) frontmatter which looks like this:

"title": "Hello World!"

Note the flanking three semicolons in the frontmatter which separate it from your post content.

Step 3: Set the theme

Every site needs a theme and Strike3 supports a comprehensive theming system. You can either create your own or download one made by our community. Helpfully, Strike3 provides a very simple theme to get you started called primary. Strike3 sets this as your site’s theme when you create a new site. Using a different theme is easy - just copy the theme folder you want to use to themes/ in the site root and set the theme value in config.json to the theme name. You can read more about this here.

Step 4: Build the site

Building your site is quick and easy. Just navigate to the root of your site a Terminal and type: strike3 build:

$ strike3 build
Success ✓
Site built in 200 ms

Step 5: Upload your site

To publish your site just copy the entire contents of the public/ folder created by the build command to the root of your web host.


Strike3 requires the presence of a configuration file in the root of the site directory named config.json. Not only does this contain a number of mandatory values needed by Strike3 to build your site but it can specify additional options and contain arbitrary data for your themes to use.

Below is the configuration file created by Strike3 when you run the strike3 create site command:

  "theme": "primary",
  "description":"My great website",
  "BuildDrafts": false

Omitting any of the values above will cause Strike3 to use its defaults. A list of all values controlling site creation recognised by Strike3 are listed below:

"archives": true
# Whether or not to build the archive listings (set to true if active theme demands it)

"baseURL": "/"
# Hostname (and path) to the root, e.g.

"buildDrafts": false
# Whether posts with `"drafts": true` in their frontmatter should be rendered when building the site

"description": "My great website"
# A description of the site. Used in some themes as a tagline

"longPost": false
# If `true` then the contents of this post will be shortened on list pages to a summary

"postsPerPage": 10
# The number of posts to show on listing pages

"rss": false
# Whether or not to build an RSS feed at /rss.xml

"theme": "primary"
# Theme name to use (this must be set to a valid theme in the themes/ folder)

"title": "My Website"
# Site title

In addition to the values above, you are free to add any other valid JSON key/value and this will be accessible by all template files in the active theme. For instance, you may want to set details about the site author:

"author": "Garry Pettet"

This would then be accessible from a theme template file with the tag {{}}.

Content organisation

Content in a Strike3 site comprises Markdown text files with the extension .md. These files can have optional information at the very beginning called the frontmatter. Strike3 respects the hierarchical file/folder organisation you provide for your content to simplify things.

Strike3 expects your content to be arranged on disk in the same way that you want it to appear in the final rendered website. Without any additional configuration on your part, the following source organisation will just work and provide a functioning website:

  - about
  ---            //
  - post
  --- First       //
  --- Second      //
  --- sub-section
  ------ Third    //
  - review
  --- Die         //

You can nest content at any level but the top level folders within the content/ folder are special and are either sections or pages.


It makes sense that the way you store your files on disk is the way you want them displayed to the user in the final rendered website. As displayed above, the organisation of your source content will be mirrored in the URLs of your site. Notice that the top level /about page URL was created using a directory named about/ with a single file inside. This is the organisation format you should use to create a single page. Creating a top-level folder containing Markdown files without an file creates a section rather than a page. The index.html for that section will be automatically created by Strike3 during the build process.

Sometimes, you need more granular control over your content. In these cases, you can use the frontmatter at the beginning of each Markdown file to do just that.


Frontmatter is great. It not only allows some flexibility to how posts appear and when they are published but it allows provides you with the ability to add custom data to a post that can then be used by themes.

Strike3 supports frontmatter in JSON format. Although optional, if you include frontmatter in your Markdown files, it must occur at the very top of the file. Frontmatter is identified by flanking it with ;;;. Example:

"title": "My first post",
"date": "2016-12-09:10"

Frontmatter variables

Variables can be accessed from within a theme template file simply by enclosing the variable name in double curly braces, like so: {{title}}. There are a few predefined variables that Strike3 uses and will create for you if not specified in the frontmatter or if no frontmatter is defined:


The publication date for the content. Should be in SQL date format. Valid examples include: 2016-12-06 10:40, 2016-12-06 and 2016-12-06 10:40:35. If not specified then Strike3 will use the modification date of the file. If the publication date is in the future then the content will not be rendered.


If true then this post will not be rendered unless the buildDrafts value in the site’s config.json file is set to true.


A post’s slug is automatically created by Strike3 but can be overridden/customised with this variable if desired.


The title for the content. If not specified in the frontmatter then Strike3 will slugify the file name.


As discussed in the content organisation section, how you organise your content in the file system is mirrored in the final built site. With this in mind, Strike3 uses the top level folders within the content/ folder as the section.

The following example site has a static home page and two sections - post and review:

  -              //
  - post
  --- First       //
  --- Second      //
  - review
  --- Die         //
  --- Star        //

Section lists

If a file titled is located within a top-level (section) folder then Strike3 will render that at /section-name/index.html. If no file is present then Strike3 will automatically generate an index page listing all content within that section. It will automatically paginate the index if there are more posts than specified in the postsPerPage variable in the site’s config.json file. For example if postsPerPage = 10 and there are 18 posts in our review section, Strike3 will create a site structure as below:         // listing of first 10 reviews  // listing of reviews 11-18

For more information on how to style these automatically generated lists from a theme, including how to access information on the individual posts in the list, see the list templates section.


Just so we’re all clear, let’s look at an illustration of the terms used to describe both a content path (i.e. a file path within your content/ folder) and a URL. The following file path:


will generate this URL:

Where is the baseURL value in config.json, review is the section (a folder titled review/ in the content/ folder) and die-hard is the slug.

The slug is created automatically by Strike3 from the file name by removing/substituting illegal URL characters. You can specify your own slug for a post by adding it to the post’s frontmatter as described above and as demonstrated below:

"slug": "my-great-slug"

Content example

They say a picture is worth a thousand words. To that effect, below is a basic example of a content file written in Markdown. We’ll assume its file path is my-site/content/review/Die This will result in a final URL of Kudos to Empire for the text.

"title": Die Hard Review,
"date": "2016-12-06 16:39"

## Intro
New York cop _John McClane_ is visiting his estranged wife Holly in LA for
Christmas. Arriving in time for her Christmas party at the Nakatomi Plaza
skyscraper, he is unfortunately also just in time to see terrorists take
everyone there hostage. As the only cop inside the building, McClane does 
his best to sort the situation out.

## About
The smart-mouthed, high-rise thriller which launched [Bruce Willis][hero] as 
an action figure and accidentally rekindled Hollywoods enthusiasm for 
disaster movies (a worthy 80s cousin to The Towering Inferno). Die Hard has 
proved a reliable video fixture for the home and looks great on DVD; just 
dying to be racked alongside its two successors.

## Verdict
John McClane's smartmouthed New York cop was a career-defining turn, mixing 
banter, action heroics and a dirty white vest to stunning effect. Acting up 
to him every step of the way is [Alan Rickman][rickman], at his sneering 
best - but the script and cast are pretty much flawless. The very pinnacle 
of the '80s action movie, and if it's not the greatest action movie ever 
made, then it's damn close.


This would be rendered as below:

<p>New York cop <em>John McClane</em> is visiting his estranged wife Holly in LA for Christmas. 
Arriving in time for her Christmas party at the Nakatomi Plaza skyscraper, he is unfortunately 
also just in time to see terrorists take everyone there hostage. As the only cop inside the building, 
McClane does his best to sort the situation out.</p>

<p>The smart-mouthed, high-rise thriller which launched 
<a href="">Bruce Willis</a> as an action figure and 
accidentally rekindled Hollywoods enthusiasm for disaster movies (a worthy 80s cousin to 
The Towering Inferno). Die Hard has proved a reliable video fixture for the home and looks great 
on DVD; just dying to be racked alongside its two successors.</p>

<p>John McClane’s smartmouthed New York cop was a career-defining turn, mixing banter, 
action heroics and a dirty white vest to stunning effect. Acting up to him every step of the way 
is <a href="">Alan Rickman</a>, at his sneering 
best - but the script and cast are pretty much flawless. The very pinnacle of the ‘80s action 
movie, and if it’s not the greatest action movie ever made, then it’s damn close.</p>

Themes overview

Strike3 has a powerful but simple theming system which is capable of styling both basic and complicated sites. As an example, my personal website is built with Strike3 using a theme I built in an afternoon. This very website is also built with Strike3 (version 1.1.4 to be precise.)

Strike3 themes are powered by Strike3’s Disco engine and are therefore termed Disco themes. Disco themes are deliberately logic-less as their purpose is purely for the display of content. This means that anybody with a basic knowledge of HTML and CSS can create a beautiful theme. Disco themes are structured in a way to reduce code duplication and are ridiculously easy to install and modify.

Strike3 currently ships with a simple default theme called primary to get you started.

Using a theme

Installing a theme

To install a theme someone else has create, simply download the new theme’s folder and place it in the themes/ folder within the root of your site. To activate it, set the value of the theme variable in the site’s config.json file to the name of the theme’s folder and rebuild the site.

Creating your own theme

It is very much encouraged that you create your own theme. Not only will this give you full creative control over how your site looks but it’s really quite straightforwards and requires only a small amount of confidence with HTML and CSS.

Creating a theme

Strike3 can create a new theme for you in your themes/ directory with the create theme command:

$ strike3 create theme [theme-name]

This command will initialise all of the files and folders a basic theme requires. Strike3 themes are written in the Disco templating language which is essentially HTML with a few Strike3 specific tags to inject content-related stuff.

Theme components

A theme comprises template files and static assets (such as CSS and javascript). Below are the files/folders required for a valid theme:

 - 404.html
 - archive.html
 - archives.html
 - home.html
 - list.html
 - page.html
 - post.html
 - tags.html
 -- partials/

This structure is created with the create theme command.


This is the theme’s configuration file in JSON format. There are currently three variables within:

  • name: The name of the theme
  • description: A brief description of the theme
  • minVersion: The minimum version of Strike3 required to use the theme


This is where a theme should store all of its static assets - things like CSS, javascript and image files. After building, they will be copied to public/assets/. Files placed here are accessible from within a theme template file with the tag {{assets}}. For example, if your theme has a stylesheet called styles.css, you might want to organise it as follows:

- assets/
-- css/
--- styles.css

styles.css would then be copied to public/assets/css/styles.css. You can access it from your theme template files with {{assets}}/css/styles.css.


This is the meat of the theme. The layouts/ folder contains the various template files which specify how certain pages are rendered. It contains a single folder, partials/ which contains template files (partial views) that can be injected into other template files. layouts/ also contains the seven template files listed below:

  • 404.html: Detail on how to render the 404 page
  • archive.html: Controls how the /archive/index.html page is rendered
  • archives.html: Specifies how individual archive year and archive month pages are rendered
  • home.html: If a static home page is required, this controls how it’s rendered
  • list.html: How to display the default list of content
  • page.html: Default rendering for a page
  • post.html: Default rendering for a single post

Additionally, a theme can have folders within layouts/ named the same as sections in the site which specifiy how content in those sections is rendered. For example, suppose my content is structured as follows:

- post/
- review/
-- Die
- Another

I can easily style the appearance of a post and a review differently in a theme with the following structure

- theme.json
- assets/
- layouts/
-- partials/
-- post
--- post.html     // will style
--- list.html     // will style
-- review
--- post.html    // will style
--- list.html      // will style
-- 404.html
-- archive.html
-- archives.html
-- home.html         // will style
-- list.html
-- post.html       // will style

You don’t have to specify both a post.html and a list.html file for each section as, if not present, the default layouts/post.html and layouts/list.html files will be used.


Disco is Strike3’s templating language. In essence, it is normal HTML with an optional number of tags that will be transformed by Strike3 during rendering into the required value.

Basic syntax

As mentioned above, Disco template files are normal HTML files with the .html file extension but with the addition of variables and functions known as tags. Tags are enclosed within double curly braces.

Template variables

Each template file has a context object made available to it. Strike3 passes either a post context or a list context to a template file, depending on the type of content being rendered. More detail is available in the variables section.

A variable is accessed by referencing the variable’s name within a tag, e.g. the title variable:



To include the contents of another template file in a template file, we use the {{partial template-name}} tag where template-name is the name of a template file in the partials/ folder (minus the .html extension).

For example, given a file called header.html in partials/ like this:

<!doctype html>

<html lang="en">
  <meta charset="utf-8">
  <link href="{{assets}}/css/bootstrap.min.css" rel="stylesheet">

We can include it in our post.html template file like this:

{{partial header}}



Disco is deliberately logic-less. The only exception is the {{foreach}}...{{endeach}} block. Tags and HTML enclosed within this block are run for each post in the current context. For example, if we assume that the current context has three pages then the following code:

  <p>Posted at {{date.hour}}:{{date.minute}}</p>
  <hr />

Would output the following HTML:

<h2>My first post<h2/>
<p>Posted at 13:15<p/>
<hr />
<h2>My second post<h2/>
<p>Posted at 08:05<p/>
<hr />
<h2>My third post<h2/>
<p>Posted at 20:45<p/>
<hr />

The {{foreach}}...{{endeach}} block only has meaning in list templates.

The context

Every template file is passed a context. There are two types of context that a template file may be passed: a list context or a post context. Each type of context has its own unique variables assigned to it by Strike3 and there are a number of base variables common to both types of context. Additionally, variables defined in a file’s frontmatter are also injected into the context.

Single posts and pages have just one context. However, the context within a list page changes when within an interation of a {{foreach}}...{{endeach}} block. This is because a list page represents a collection of posts, each one having its own context.

For example, in a single post the tag {{title}} returns the title of the post. However in a list post, within a {{foreach}}...{{endeach}} block the {{title}} tag returns the title of the post in the current iteration. Consider the following three Markdown files:

File structure:

content/review/Die    //
content/review/      //
content/review/Star   //


"title": "Die Hard (1988)"
## Yippee ki-yay!

"title": "Avatar (2009)"
## Open Pandora's box


"title": "Star Trek (2009)"
## To boldly go where no one has gone before

When Strike3 renders the page it will call the post.html template file for the theme. Let’s say the contents of that file is:


The output will be:

<h2>Avatar (2009)</h2>

If, however, Strike3 is rendering a list of the all the reviews at it will call the list.html template file. Let’s say the contents of that file is:

  <hr />

The output will be:

<h2>Die Hard (1988)</h2>
<hr />
<h2>Avatar (2009)</h2>
<hr />
<h2>Star Trek (2009)</h2>
<hr />


As mentioned in the context section, Strike3 makes available a number of variables to template files through their context. The following variables are available for use in template files within a theme.

Site variables

The value of any variable in the site’s config.json file can be retrieved from any template file with the tag {{site.variable-name}}, this includes user-defined variables. This is the prefered method to set global data values.

For example, to get the base URL of the entire site from within a template file, simply use the tag {{site.baseURL}}.

All context variables

The following is a list of the variables available to both post contexts and list contexts. In the case of post contexts, all may be overridden in the frontmatter. Remember, these are all accessed by enclosing in double curly braces, e.g: {{variable name}}.

  • {{assets}}: The public URL to the current theme’s assets/ folder
  • {{content}}: The rendered content of the context’s file
  • {{date}}: The date of the content in SQL format
  • {{date.second}}: The second component of the content’s date (two digits)
  • {{date.minute}}: The minute component of the content’s date (two digits)
  • {{date.hour}}: The hour component of the content’s date (two digits)
  • {{}}: The day component of the content’s date (two digits)
  • {{date.month}}: The month component of the content’s date (two digits)
  • {{date.longMonth}}: The month component of the content’s date (e.g. January)
  • {{date.shortMonth}}: The month component of the content’s date (e.g. Jan)
  • {{date.year}}: The year component of the content’s date (four digits)
  • {{feedURL}}: The URL to the site’s RSS feed (if enabled in the site’s configuration)
  • {{navigation}}: Unordered HTML list of the site contents
  • {{permalink}}: The permalink URL to the content
  • {{readingTime}}: Estimated reading time for the content (e.g. “3 min read”)
  • {{storage}}: The public URL to the storage/ folder
  • {{summary}}: A summary of the content (first 55 words)
  • {{tags}}: Unordered HTML list of the content’s tags
  • {{title}}: The title of the content
  • {{wordCount}}: The number of words in the content

List context variables

List pages are automatically created by Strike3 at the root of the site as (unless a static homepage is specified) and at the root of every section (e.g. and are rendered by list.html template files. The following is a list of variables accessible from list.html template files.

  • {{nextPage}}: The URL to the next page in a paginated list of posts
  • {{prevPage}}: The URL to the previous page in a paginated list of posts

It’s worth noting that the value returned to the template of {{content}} can be modified on list pages if the longPost variable in the frontmatter of a post is set to true. If this is the case then a shortened summary of the post will be returned instead of the full contents on list pages only. This is useful if the post is either very long or perhaps contains lots of images that you don’t want to be displayed on the post listing page.

Archive variables

  • {{archives.months}}: HTML list of your site’s content by month (e.g. Jan)
  • {{archives.longMonths}}: HTML list of your site’s content by month (e.g. January)
  • {{archives.url}}: The URL to your site’s archive listing page (e.g.

Helper variables

  • {{}}: The day component of the current date (two digits)
  • {{helper.longMonth}}: The month component of the current date (e.g. January)
  • {{helper.shortMonth}}: The month component of the current date (e.g. Jan)
  • {{helper.month}}: The month component of the current date (two digits)
  • {{helper.year}}: The year component of the current date (four digits)

Strike3 variables

  • {{strike3.generator}}: Meta tag for the version of Strike3 that built the site. I’d be very grateful if you would include it in all theme headers so I can track the usage and popularity of Strike3 as a tool. Example output: <meta name="generator" content="Strike3 1.1.4" />
  • {{strike3.version}}: Strike3’s version number

Single templates

Single content is the term for posts and pages. For every Markdown file in the content/ folder (except the homepage), Strike3 will render it using either a page.html or post.html file from the currently active theme. Which template file is used is decided with this algorithm:

  • Is the file content/ If so then it’s a static homepage so render it with layouts/home.html
  • Is the Markdown file in the root of content/? If yes then use layouts/post.html
  • Is the Markdown file named and the only file in a subfolder of content/?. If yes, it’s a page so render with layouts/page.html
  • Is the Markdown file in a section? If yes then use the post.html file for that section. For example, for the Markdown file content/review/Die Strike3 will look first for layouts/review/post.html and use it. If that doesn’t exist then Strike3 will render the content with the default layouts/post.html file.

Example post.html template file

{{partial header}}

<div class="row">
  <div class="col-12">
    <article class="single">
      <div class="post-meta">
        <h2 class="post-title">{{title}}</h2>
        <p class="post-date">{{date.longMonth}} {{}}, {{date.year}}</p>
      <div class="post-content">

{{partial footer}}

List templates

A list template is used to render multiple pieces of content in a single HTML file. Essentially, it’s used to generate all index.html pages for the site (although optionally a different template can be used to render a static homepage).

For example, suppose I want a standard blog where the index page for the site (let’s say lists all my blog posts in a paginated fashion. I also want a review section, separate from my blog that’ll store my movie reviews. I want that to have a listing too. I will structure my content as follows:

- Post
- Post
- Post
- Post
- review/
--- Review
--- Review
--- Review

This will lead to the site structure below:             // auto-generated      // auto-generated

To render the main index page (, Strike3 will use the default layouts/list.html template file. To render the listing for the reviews, Strike3 will first try to use layouts/review/list.html. If that file doesn’t exist then Strike3 will default to layouts/list.html. This allows themes to style the listing of sections differently.

Example list.html template file

The example list.html template file below is similar to that used to generate the listing of posts on my personal blog:

{{partial header}}

  <div class="row">
    <div class="col-12">
        <article class="list">
          <h3 class="post-title">
            <a href="">{{title}}</a>
            <span class="separator"> · </span>{{date.longMonth}} {{}}, {{date.year}}
  <div class="row">
    <div class="col-12">
      <div class="list-navigation">
        <a class="prev-page" href="{{prevPage}}">← Previous</a>
        <a class="next-page" href="{{nextPage}}">Next →</a>
</div><!--/.container data-sticky-wrap-->

{{partial footer}}


Believe it or not, the inability of a, shall remain nameless, dynamic website generator to create a static homepage was the “straw that broke the camel’s back” and drove me to write my own site generator in the first place.

A static homepage is the site’s landing page (i.e. the main index.html file) that is rendered differently from all the other site pages. Creating one is super easy with Strike3. Put the content you want on your homepage in a Markdown file named in the root of the site (i.e. content/ and style it with the template file layouts/home.html. Job done.


Strike3 supports the tagging of posts. A post can be assigned any number of tags (or none at all) within its frontmatter. To assign a tag or tags to a post simply add them in a JSON array called tags within the frontmatter:

"tags": ["review", "sci-fi"]

Getting a post’s tags

Themes have easy access to a post’s tags with the {{tags}} variable. Calling {{tags}} will output an unordered HTML list of the tags like so:

<ul class="tags">
  <li><a href="/tag/review">review</a></li>
  <li><a href="/tag/sci-fi">sci-fi</a></li>

Listing content by tag

The posts tagged with a particular tag can be found at public/tag/tag-name/index.html. So in the above example we could view all posts tagged “sci-fi” by visiting public/tag/sci-fi/index.html.


Strike3 will automatically add archives for your content. To disable this functionality just set the archives variable in config.json to false.

When archives are enabled, Strike3 will create a top-level section in the built site at /archive. A page will be created at the root of this section (archive/index.html) for you to style how you wish with the layouts/archive.html template file.

Additionally, sub-folders will be created beneath archive/ for each year and month that posts occur. For example, the following content:

- Post     // publish date: Oct 1st 2016
- Post     // publish date: Sep 10th 2016
- Post     // publish date: Jan 22nd 2016
- Post     // publish date: Mar 4th 2015
- Post     // publish date: Feb 8th 2015

Would result in an archive as follows:      // lists all 2016 posts   // lists October 2016 posts    // lists September 2016 posts    // lists January 2016 posts      // lists all 2015 posts    // lists March 2015 posts    // lists February 2015 posts

These listing pages are styled with the layouts/archives.html template file (note archives not archive).

See the variables section for more information on archive-specific template tags.

It’s worth noting that generating archives is computationally expensive. If you don’t need them then set the archives variable in config.json file to false.

Strike3 provides a simple way to include site navigation in your themes. Using the {{navigation}} tag within any template file will output an unordered HTML list of all the sections and sub-sections of your site with permalinks to their roots. For example, given the following content:

- about/
- post/
- review/

The {{navigation}} tag would generate the following HTML:

<ul class="site-nav">
  <li><a href="">about</a></li>
  <li><a href="">post</a></li>
  <li><a href="">review</a></li>

Strike3 has full support for pagination. Whether or not pagination is required for a particular section depends on the postsPerPage variable in the site’s config.json file. For instance, suppose we have a blog with the following structure:

- Post
- Post
- Post
- Post
- Post
- Post

Strike3 will automatically create an index list page (because we have not specified a static homepage) at public/index.html using the rendering information in the list.html template file of the current theme.

If we leave postsPerPage at the default value (10) then Strike3 will not need to paginate the index because we only have 6 posts. If however we change postsPerPage to 3 then Strike3 will not only create public/index.html (which will list the first three posts: Post, Post and Post but it will also create a second page at public/page/2/index.html (which will list the last three posts: Post, Post and Post

Strike3 provides convenient tags to output the URLs of the previous and next pages. These tags are {{nextPage}} and {{prevPage}}. These tags are only valid in list.html and archives.html template files.

Example usage

Here’s how I use these tags in my personal blog, which is built with Strike3:

<div class="list-navigation">
  <a class="prev-page" href="{{prevPage}}">Previous</a>
  <a class="next-page" href="{{nextPage}}">Next</a>

Which would render something like this (assuming we’re on page 2 of the list):

<div class="list-navigation">
  <a class="prev-page" href="">Previous</a>
  <a class="next-page" href="">Next</a>


Strike3 can optionally generate a RSS feed for your site if the rss variable is set to true within the site’s config.json file. The feed adheres to the RSS 2.0 specification.

The feed will be saved to public/rss.xml. You can access the link to it from within a template file with the {{feedURL}} tag.

It’s worth noting that feed XML files can grow quite large. If you don’t want to provide a feed for your site then make sure you set the rss variable to false to reduce build times and reduce the size of the site to upload. It’s false by default.


Sometimes you’ll need to perform some actions after Strike3 has built your site. This can be done quite easily by placing scripts to run after the build into the scripts/ folder. Scripts must have the extension .xojoscript and must be written in Xojo’s scripting language: Xojoscript. Strike3 provides a few global functions that you can call from your scripts:



CopyFromRootToPublic(sourcePath as String)

This function allows you to copy files or folders from the root of your unbuilt site to the public folder after the site has been built. Let’s say we have the following structure to our site:

  - file1.html
  - file2.html

We can use this method to copy file1.html to the public root with the following syntax:


We can also use this method to copy the entire misc/ folder to the public root like this:




CopyFromThemeToPublic(sourcePath as String)

This function allows you to copy a file or folder from a location within the current theme folder to the public folder of the built site. sourcePath is the path relative to the current theme root of the asset to copy. Let’s suppose we have the following theme structure:

My Great Theme/
    - favicon.ico

We can use this method to copy favicon.ico to the public root with the following syntax:


We can also use this method to copy the entire misc/ folder to the public root like this:


I frequently use this function to copy the favicons from the theme folder to the public root of my built site.



GetFileContents(filePath as String) as String

This function returns the contents of the file specified. filePath is relative to the Strike3 site root.



WriteToFile(what as String, filePath as String)

This function writes the passed string what to the file at the path specified. filePath is relative to the Strike3 root.