FAQ

A Static Site Generator (SSG) is a tool that generates static HTML pages from templates or components, typically using content written in markdown or other markup languages.

Unlike traditional Content Management Systems (CMS) that generate pages dynamically on the server for each request, SSGs generate all the pages at build time. The static HTML can then be served by a simple file server, resulting in faster load times and increased security.

Installation instructions typically vary by SSG, but most can be installed using package managers like npm (Node.js) or gem (Ruby). Detailed instructions are usually provided in the documentation. If you are looking for the Toucan installation instructions, please visit our corresponding docs section.

Most SSGs require a modern operating system and a working installation of Node.js, Ruby, Python, or another relevant programming environment. However, since Toucan is distributed as an executable binary, there is no need to set up additional tools on your machine.

After installing the SSG, you typically need to create a new project, choose or create a template, add your content, and then build the site. Step-by-step instructions are available in the documentation.

Content is usually added through markdown files or other markup languages, which are then processed by the SSG to generate HTML pages.

Yes, you can create and use your own custom templates. Most SSGs provide a flexible templating system that allows you to define the layout and structure of your pages.

You can customize your site’s appearance by modifying the CSS, using different templates, or integrating a front-end framework.

Media files can be stored in your project’s directory and referenced in your content. Most SSGs have built-in support for handling media assets.

Static sites are generally faster because they consist of pre-built HTML files, which reduces the need for server-side processing and database queries.

Yes, static sites are highly scalable and can handle high traffic volumes efficiently, especially when served through a content delivery network (CDN).

Static sites can be deployed on various platforms such as GitHub Pages, Netlify, Vercel, Amazon S3, or any web server that can serve HTML files.

Yes, dynamic features can be integrated using third-party services and APIs. For example, forms can use services like Formspree, and user authentication can be managed with tools like Auth0.

Yes, headless CMS solutions like Contentful, Sanity, and Strapi can be integrated with SSGs to provide a more user-friendly content management experience.

Static sites can be optimized for better ranking by including metadata, using clean URLs, and generating sitemaps. Many SSGs offer plugins or built-in features to help with SEO.

Check the error message for clues, consult the documentation, and look for solutions in community forums or GitHub issues. Most SSGs have active communities that can help troubleshoot issues.

Support can be found through official documentation, community forums, GitHub repositories, and sometimes dedicated support channels provided by the SSG developers.

Updating typically involves using the package manager’s update commands, such as npm update for Node.js-based SSGs or gem update for Ruby-based SSGs. Always refer to the official documentation for specific instructions.

Regularly update dependencies, backup your content and configuration, use version control (e.g., Git), and monitor performance. Additionally, keep your SSG and any integrated services up to date.