Initial Setup
The first step to developing Kajabi themes is to establish a Kajabi Developer Account. If you do not already have access to a Kajabi Developer account reach out to themes@kajabi.com for one.
Sign into your Kajabi developer account
Open the Website tab from the dashboard
Select Page Builder
Click Upload Theme
Upload the theme via this link:
Create a local version of Cornerstone. Our bare-bones landing page theme meant for bootstrapping new projects.
Next, install the RubyGem in your local text editor
Inside the new theme directory run
After running this, the text editor should ask you for
Remote theme id
Your api key
Your api secret key
The path to a CA cert file (optional)
Upload your local files to the remote theme
Have Kajabi watch for local changes and sync with your dev account theme
Gathering Assets
Kajabi Themes use gulp to gather scss and js files and place them in the assets folder. To get this working run the following commands inside your theme directory.
Inside your theme directory is a file named gulpfile.js and this file tells the theme what stylesheets and javascript files to look for and move into the assets folder as you work.
To have gulp do this automatically as you're working, simply run is the following command
Once you have your local environment set up, dive into the docs to discover all of the functionality available to you with Kajabi Themes
Configuring TLS options
Transport Layer Security (TLS) is used to create a secure connection when syncing data to our servers. In some cases the kajabi-theme
tool may not be able to verify the connection, and you'll get the following error:
We rely on a default Certificate Authority (CA) cert file. If you run into this error, you can configure a different CA cert file.
Configure a different CA cert file:
Save the CA cert file to a location on your file system
Run
kajabi-theme configure
and provide the path to that file when promptedYou can also manually edit
config.yml
and set the:cainfo:
option
If you're still having issues after configuring a different CA cert file, it's possible to disable SSL verification entirely.
Deactivate SSL verification:
Edit
config.yml
Update
:ssl_verifypeer: false
and save
We strongly recomend against this option and it should only be used as a last resort
Last updated