Frisco

Frisco is a Jekyll template designed to promote a mobile app and increase its web presence, built by CloudCannon with a focus on CMS-friendly editing. It turns site details from _config.yml into a static marketing site with pre-built pages, a paginated blog, staff profiles, and a configurable contact form.

What is Frisco?

Frisco is a Jekyll-based website template for app promotion. It takes configuration from _config.yml (site and author details, Google Analytics key, Disqus key) and generates a static website with pre-built pages, a blog with pagination, post category pages, and a staff author system. The template was created by CloudCannon, the cloud CMS for Jekyll, and is available on GitHub with a one-click deploy option to CloudCannon.

Key Features

• Contact form — A preconfigured form that works with CloudCannon out of the box and can be switched to another provider such as FormSpree.
• Blog with pagination — Posts are organized by category, with generated category pages and pagination for long-running blogs.
• Staff and author system — A Staff Members collection is reused around the site, and posts link to authors through a Staff Author field.
• Disqus comments — Each post can display comments via Disqus; only a Disqus key in _config.yml is needed.
• Configurable footer — Footer content is exposed as a data file in the Data section of CloudCannon, giving clients an easy way to edit navigation and footer elements.
• CMS-optimized — Pre-built pages and pre-styled components are structured for adding, updating, or removing content in CloudCannon without touching code.
• RSS/Atom feed — The site automatically generates an RSS/Atom feed for blog subscribers.
• SEO tags and Google Analytics — Includes SEO meta tags and a Google Analytics integration keyed through _config.yml.

Who is it for?

• App developers and startups — Get a professional marketing site for a mobile app launched quickly, with a landing page, blog, and contact capabilities.
• Content editors and marketers — Manage site content, blog posts, staff bios, and footer items through the CloudCannon CMS instead of editing code directly.
• Jekyll users — Use this template as a starting point for any project needing a blog with authors, categories, and comments, and run it locally with bundle exec jekyll serve.

What can you do with it?

• Launch an app landing page: Assemble a polished web presence with pre-built pages, a contact form, and a customizable footer to collect leads.
• Publish a blog: Write posts that appear in a paginated blog with category pages, Disqus comments, and an RSS feed to keep visitors engaged.
• Showcase a team: Create staff member profiles in the Staff Members collection and attach authors to blog posts, reusing that data across the site.

How does it work?

1. Add your site and author details in _config.yml.
2. Add your Google Analytics and Disqus keys to _config.yml.
3. Install dependencies with Bundler using bundle install, then run bundle exec jekyll serve locally, or deploy to CloudCannon with the provided connect button.

FAQ

Is Frisco free to use?

Frisco is an open-source template available on GitHub, with repository metadata indicating a Jekyll theme. There is no pricing information listed on the template page, and it can be used freely as a Jekyll template.

What version of Jekyll does Frisco use?

Frisco was built with Jekyll version 3.3.1, but the template states it should support newer versions as well. Dependencies are managed with Bundler to keep versions consistent.

Can I use my own contact form service?

Yes. The contact form is preconfigured to work with CloudCannon, but the template notes it can be easily changed to another provider such as FormSpree.

How do I set up comments on my blog posts?

Enable Disqus by adding your Disqus key to _config.yml. Each post will then display a Disqus comment thread.

Does Frisco work without CloudCannon?

Yes. Frisco is a standard Jekyll template, so you can run it locally with bundle exec jekyll serve or deploy it to any Jekyll-compatible hosting. The CloudCannon integration is optional but recommended for the CMS editing experience.