This is a starter template for creating a beautiful, customizable documentation site for your project with minimal effort. You’ll only have to change a few settings and you’re ready to go.
As with all Jigsaw sites, configuration settings can be found in
config.php; you can update the variables in that file with settings specific to your project. You can also add new configuration variables there to use across your site; take a look at the Jigsaw documentation to learn more.
// config.php return [ 'baseUrl' => 'https://my-awesome-jigsaw-site.com/', 'production' => false, 'siteName' => 'My Site', 'siteDescription' => 'Give your documentation a boost with Jigsaw.', 'docsearchApiKey' => '', 'docsearchIndexName' => '', 'navigation' => require_once('navigation.php'), ];
Tip: This configuration file is also where you’ll define any "collections" (for example, a collection of the contributors to your site, or a collection of blog posts). Check out the official Jigsaw documentation to learn more.
You can write your content using a variety of file types. By default, this starter template expects your content to be located in the
source/docs folder. If you change this, be sure to update the URL references in navigation.php.
The first section of each content page contains a YAML header that specifies how it should be rendered. The
title attribute is used to dynamically generate HTML
title and OpenGraph tags for each page. The
extends attribute defines which parent Blade layout this content file will render with (e.g.
_layouts.documentation will render with
source/_layouts/documentation.blade.php), and the
section attribute defines the Blade "section" that expects this content to be placed into it.
--- title: Navigation description: Building a navigation menu for your site extends: _layouts.documentation section: content ---
source/_assets/ directory, and Laravel Mix will process them when running
npm run local or
npm run production. The processed assets will be stored in
/source/assets/build/ (note there is no underscore on this second
Then, when Jigsaw builds your site, the entire
/source/assets/ directory containing your built files (and any other directories containing static assets, such as images or fonts, that you choose to store there) will be copied to the destination build folders (
build_local, on your local machine).
Files that don't require processing (such as images and fonts) can be added directly to
Building Your Site
Now that you’ve edited your configuration variables and know how to customize your styles and content, let’s build the site.
# build static files with Jigsaw ./vendor/bin/jigsaw build # compile assets with Laravel Mix # options: dev, staging, production npm run dev