Geb is a powerful and intuitive static website manager and builder named after the ancient Egyptian god Geb, the deity of the Earth. Just as Geb provides a stable foundation for the world, our software offers a robust and essential foundation for building and managing static websites, which form the very bedrock of the web.

Geb provides a seamless command line interface, making it easy to create, build, and manage your static websites with efficiency and ease. Whether you are a seasoned developer or a beginner, Geb provides the tools and templates to help you get started quickly and effectively.

With Geb, you can harness the power of site templates to streamline your workflow, ensuring your websites are not only beautiful but also maintainable. Our built-in templates, along with the ability to use previous projects as templates, provide unparalleled flexibility and reusability, enabling you to focus on what matters most: creating amazing content and user experiences.

• Installation
• Usage
• Geb Site Configuration
• Site Templates
  • Built-in site templates
  • Previous project as a template
  • Publishing and using templates
• Basic Site Structure
• Pages, Templates and Partials
  • Page Example
  • Template Example
  • Partial Example
  • Result Page
  • Discussion and key takeaways
• Site Variables
• Command Reference
• Roadmap
• Development
• Contributing
• License
• Code of Conduct

Installing geb is as simple as installing a Ruby Gem

$ gem install geb

If you would like to install geb from source, follow the following steps

# clone the repository
$ git clone https://github.com/mainfram-work/geb.git
$ cd geb

# install dependencies
$ bundle install

# make sure everything works
$ rake test

# build and install the geb gem
$ rake build
$ rake install

Geb has several commands to help you manage your site. running "geb help" will list the available commands.

$ geb help
Commands:
  geb build                    # Build the full site, includes pages and assets
  geb init SITE_PATH           # Initialize geb site, creates folder locations, git repository and initial file structures
  geb release                  # Builds the release version of the site (pages and assets)
  geb remote                   # Launch remote ssh session using the config file settings
  geb server                   # Start a local server to view the site output (runs build first), uses webrick
  geb upload                   # Upload the site to the remote server
  geb version                  # Print version

To get help for a particular command simply run.

$ geb [command] --help

The basic geb workflow is as follows.

# initialize a new site in the directory nexthing
$ geb init nexthing
$ cd nexthing

# build the site
$ geb build

# start a local web server to access your built site
$ geb server

# build a release version of the site
$ geb release

# upload the released site to your remote server
$ geb upload

All geb commands (other than the geb init command) are executed with the project directory. Geb looks for the site root by finding the geb.config.yml file up the directory tree.

Every Geb site has a configuration file at the root of the site. The file is called geb.config.yml The geb command will use values in the configuration file over the default values in almost all cases.

Check out a sample geb configuration file for a detailed description of all configuration items.

Geb has a concept of site templates. Think of it as a way to share site designs, libraries and content. Geb comes with a set of site templates, distributed with the geb gem. These are:

• basic - this is a default template, that provides a simple site structure and placeholders for various concepts such as headers, footers, javascript and CSS and so on.
• bootstrap_jquery - a site template with Bootstrap 5 and JQuery 3.7, along with example pages.

To use one of the built-in templates, simply pass the name to the geb init command

$ geb init new_site --template bootstrap_jquery

If you do not specify a site template, geb will use the basic template that comes bundled with the geb gem.

Site templates can also be other sites you have developed. To use a previous project as a basis for some new project, you will need the following.

First, the project you wish to use as a template needs to have template_paths configured within its geb.config.yml file. Here is an example.

# if you want to share the site as a template site, specify which files and directories 
# are part of the template.
template_paths: ["assets", "shared", "*.html", "site.webmanifest"]

To use a previous project as a site template, simply pass it to the geb init command

$ geb init new_site --template ~/projects/other_site

To publish the site template along with your site, you will need to specify the template_paths configuration within the geb.config.yml file and package the template using the geb release command

$ cd ~/projects/new_site
$ geb release --with_template

Geb will generate geb-template.tar.gz within the site release directory, which you can then upload using geb upload command or whatever other mechanisms you plan to use to deploy the finished site.

To use an already published template, simply pass the site URL to geb init command.

$ geb init new_site --template https://www.some_website.com/

You can either pass the URL to the geb-template.tar.gz. Geb will try the URL first and if it doesn't find geb-template.tar.gz it will append the filename and try again.

You can structure a Geb site however you want. The only required directories are assets and output with local and release sub-directories. geb init command will create these directories.

new_site
  ├── assets                    # [required] assets directory for images, css, js, etc.
    ├── images                  # images directory
      ├── css                   # css directory
      ├── js                    # js directory
  ├── blog                      # just a directory to hold blog posts 
    ├── index.html              # the blog index page
    ├── blog_post_1.html        # a sample blog post
  ├── geb.config.yml            # [required] the site configuration file   
  ├── index.html                # site index pag, this page
  ├── page.html                 # another page
  ├── output                    # [required] the directory where the built site is output
    ├── local                   # [required] local build directory, server command uses this as root
    ├── release                 # [required] release build directory, upload command uploads from here
  ├── shared                    # shared directory for partials, templates, etc.
    ├── partials                # partials directory
      ├── _analytics.html       # partial with site analytics
      ├── _footer.html          # footer partial
      ├── _global_assets.html   # global assets partial (js and css references)
      ├── _header.html          # header partial
      ├── _meta_tags.html       # site meta tags partial
    ├── templates               # templates directory
      ├── _blog_post.html       # template for blog pages
      ├── _site.html            # template for general site pages
  ├── site.webmanifest          # site webmanifest file

All references to assets (image, css, js, etc) as well as links should be relative to the site's root

Files that start with _ are partials or templates and are not meant to be served directly. You won't see these files in the output directory.

It is possible to configure geb to use different directories for assets or output. However, geb.config.yml must be updated to reflect these changes and be located in the site root. Check the sample geb configuration file for more information.

The rest is up to you. We like the convention of putting partials and templates in the shared directory, but you can put them anywhere. You can create any directory structure that makes sense for your site.

Below are some examples of how to use pages, templates and partials with Geb. Read the examples first, then the discussion located after the examples.

Here is a simple page example, in the above site structure this might be index.html file

<% template: shared/templates/_site.html %>

<% start: title %>
 Page Title
<% end: title %>

<% start: content %>
 This is page content
 <%= partial: shared/partials/_featured_product.html %>
<% end: content %>

This is a page template example, in the above site structure this might be shared/templates/_site.html

<!DOCTYPE html>
<html>
 <head>
   <title><%= insert: title %></title>
   <%= partial: shared/partials/_analytics.html %>
   <%= partial: shared/partials/_meta_tags.html %>
   <%= partial: shared/partials/_global_assets.html %>
  </head>
 <body>
   <%= partial: shared/partials/_header.html %>
   <%= insert: content %>
   <%= partial: shared/partials/_footer.html %>
 </body>
</html>

This is a page partial example, in the above site structure it could be any file in the shared/partials directory.

<h1>Best Product Ever<h1>
<p>This is the best product ever</p>
<%= partial: shared/partials/_product_analytics.html %>

Below is the Page Example above, processed by geb build command.

 <!DOCTYPE html>
<html>
  <head>
    <title>Page Title</title>
    <!-- content from shared/partials/_analytics.html -->
    <!-- content from shared/partials/_meta_tags.html -->
    <!-- content from shared/partials/_global_assets.html -->
  </head>
  <body>
    <!-- content from shared/partials/_header.html -->
    This is page content
    <h1>Best Product Ever<h1>
    <p>This is the best product ever</p>
    <!-- content from shared/partials/_product_analytics.html -->
    <!-- content from shared/partials/_footer.html -->
  </body>
</html>

• Pages are the actual content of the site. They are the only files that are served directly.
• The example page above uses a template found in /shared/templates/_site.html
• Templates are used to wrap pages in a common structure. They are not served directly.
• The example template above has two content blocks, title and content.
• The page above has those content areas filled in with whatever is required
• Page start: what_ever_name and template insert: what_ever_name must have matching "names"
• If a page uses a template, the template must be defined at the top of the page.
• If a page uses a template, any content not in a "start: what_ever_name" -> "end: what_ever_name" block is ignored.
• Obviously, the "start: what_ever_name" -> "end: what_ever_name" must have matching "names"
• Partials are used to include common content in pages and templates. They are not served directly.
• Partials can be nested, but be careful not to create circular references.
• A note on tags, <%= partial ... %> and <%= insert ... %> have and equal sign, while <% template ... %>, <% start ... %>, <% end ... %> do not. The reason is partials and inserts change content where they are, while other tags are instructions.
• That's about it... happy coding!

Geb supports the concept of site variables. In the geb configuration file, you can specify site variables that are merged into the pages once templates and partials have been parsed.

Here is an example of what geb.config.yml may contain:

site_variables:
  local:
    title: "My Local Site"
    site_url: "https://localhost:4000"
  release:
    title: "My Site"
    site_url: "https://example.com"

Geb will select the appropriate variables depending if you are building the site using geb build or releasing the site using geb release. Logically, geb build uses local variables, while geb release uses release variables.

To use the variables within templates, partials or pages, simply enclose the site variable name in _{...}_

<html>
  <head>
    <title>_{title}_>/title>
    <meta name="twitter:image" content="_{site_url}_/assets/images/og-thumb.png" />
  </head>
</html>

Geb also has four special variables that are available during both geb build and geb release. These are:

• page_title - Extracted from the page <title></title> tag
• page_relative_path - Page path relative to the site URL
• site_name - Geb site name (either from configuration or development folder name)
• geb_version - Geb version number

Build the full site, includes pages and assets.

$ geb build [--skip_assets] [--skip_pages]

• --skip_assets: Skip building assets (images, css, js)
• --skip_pages: Skip building pages

Initialise geb site, creates folder locations, git repository and initial file structures.

$ geb init SITE_PATH [--template=VALUE] [--skip-template] [--skip-git] [--force]

• --template=VALUE: Template site, either a path or one of the following: bootstrap_jquery, basic
• --[no-]skip-template: Skip generating a site from a template
• --[no-]skip-git: Skip initializing the git repository
• --[no-]force: Force overwrite of existing files and git repository

Builds the release version of the site (pages and assets).

$ geb release [--with_template]

• --with_template: Build the release site with a template archive

Launch remote ssh session using the config file settings.

$ geb remote

Start a local server to view the site output (runs build first), uses webrick.

$ geb server [--port=PORT] [--skip-build] [--skip-auto-build]

• --port=PORT: Port to run the server on
• --[no-]skip-build: Skip building the site before starting the server
• --[no-]skip-auto-build: Don't automatically rebuild the site when a file changes
• --[no-]debug: Enable full output during site rebuild

Upload the site to the remote server.

$ geb upload

Print the current version of Geb.

$ geb version

This roadmap outlines the planned features and improvements for future versions of Geb. The timeline and features are subject to change based on feedback and development priorities.

Target Release Date: Sometime in September 2024

Planned Features

• Template Enhancements: Improve the existing templates and add more templates for various types of websites.
• Plugin Support: Introduce a plugin system to extend Geb's functionality.
• Improved Documentation: Expand the documentation with more examples and tutorials.

Improvements

• Windows Support: Test and build Geb on Windows operating system
• Better Testing: Ability to better test geb upload and geb remote commands.

After checking out the repo, run bin/setup which just runs bundle install to install dependencies. Then, run rake test to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

Gab has the following dependencies

• Ruby >= 3.0.0
• dry/cli - a general-purpose framework for developing Command Line Interface (CLI) applications.
• Webrick - an HTTP server toolkit that can be configured as an HTTPS server, a proxy server, and a virtual-host server.
• Listen - gem listens to file modifications and notifies you about the changes.

The development environment has the following dependencies:

• Rake - a Make-like program implemented in Ruby.
• minitest - provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking.
• webmock - library for stubbing and setting expectations on HTTP requests in Ruby.
• mocha - a Ruby library for mocking and stubbing.
• simplecov - a code coverage analysis tool for Ruby.
• yard - a Ruby documentation tool.

To install this gem onto your local machine, run bundle exec rake build and then bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and the created tag, and push the .gem file to rubygems.org.

You can generate documentation by running yard doc and then using yard server to view the documentation. Running rake test will also generate a coverage report. To view the coverage report, just open coverage/index.html from the project directory.

Happy hacking :)

Bug reports and pull requests are welcome on GitHub at https://github.com/mainfram-work/geb. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

The gem is available as open source under the terms of the MIT License.

Everyone interacting in the Geb project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.