Bridgetown works best as part of a version-controlled repository powered by Git. You can centrally store your repository on a service like GitHub so that you and everyone else working on the website (plus your hosting provider) all have direct, secure access to the latest website content and design files.
During the development process, you will likely be running Bridgetown from the command line on your local developer machine (or perhaps a remote staging server). Once content is ready to publish, you would commit your website codebase to the Git repository and use an automated build tool to generate and upload the final output to a server or CDN (Content Delivery Network). Render is a popular service for this, but there are many others. You can also just literally copy the generated files contained in the
output folder to any HTTP web server and it should Just Work. 😊
For more background on this development approach, read up on our Jamstack primer.
For a succinct overview of how the Bridgetown build process works and what goes into creating a site, read our Core Concepts guide.
Read requirements for more information on what you’ll need to have set up in advance.
The basic installation process is as follows:
Install a Ruby development environment which is supported by Bridgetown.
Install Node and Yarn to handle frontend assets and spin up a live-reload development server.
- Install Bridgetown and related gems:
$ gem install bundler bridgetown -N
- Create a new Bridgetown site at
$ bridgetown new mysite
- Change into your new directory.
$ cd mysite
- Build the site and run a live-reload development server:
$ bin/bridgetown start
Browse to http://localhost:4000
- And you’re done! (That’s the goal at least 😊)
If you encounter any errors during this process, try revisiting your installation and setup steps, and if all else fails, reach out to the Bridgetown community for support. Also, make sure you’ve installed the development headers and other prerequisites as mentioned in the Requirements section.
Bridgetown comes with the
bridgetown CLI tool as well as several Yarn scripts,
so be sure to read up on the command line usage documentation.
Also read up on Bridgetown’s Core Concepts to gain familiarity with the basic building blocks and workflow of Bridgetown.