The process map guides you through all steps of the deployment. |
To get access to Github using your account on Netlify, you need to sign in first. |
When you’ve successfully authenticated on Github, a secure connection gets established between Netlify and Github. This connection enables the provisioning process to copy (clone) the template in your repo space at Github. The cloned repository is used for all of the next steps in building your website. |
In the configuration step, you can change the default name j1-template-starter of the repository on Github. Customize the name for your needs. This repo (at Github) is used for all the following steps to automatically create your new website. |
After the build process has finished, you have a new website with a random name generated on Netlify. It is recommended to change that name for your needs. |
The customized name is the base for the URL to access your website on the Internet. |
After changing the name of web, have a look and visit your new web. |
Look at your Github account after the build and deployment processes are finished on Netlify. Check for the repository of your new website created for you.
From the repository detail view, you can manage all settings of your new web online from Github. For little changes, this is possible but not convenient. Check the section What next for a much better way to manage your site’s content. |
A website based on the J1 Theme is set to development mode by default. If you check the SEO Quality Metrics calculated by Lighthouse, you’ll find good numbers for performance, but they are not excellent. The development mode for the J1 Theme supports developers in changing content and checking the outcome but does not generate optimized code for production.
Read more on calculated SEO Metrics by Lighthouse on page SEO Quality Metrics.
The mode production for the J1 Theme is the base for generating highly optimized code for production and deploying a site high-performance. Optimized code is fully compressed for all HTML pages, JS and CSS files. Additionally, all info and debug messages (displayed in a browser’s console) are removed, and only warning and error messages are issued. Removing not needed parts results in excellent performance and secured content.
You got it managed. The new website is online. The site was built from the boilerplate of J1 Theme. For sure, not your site but a good starting point for your content to make your ideas of a website real. And you’re prepared well. The control center on Netlify is in place, and your site is sitting a repo at Github. Not that bad. The next step is to create a local copy of the repo from Github to a folder on your PC to start developing from a local system.
Developing a website should be done from a local PC. J1 comes with a full-featured development system. The local copy of the repo contains already all components required to manage the development process, including a webserver. And better: your control center on Netlify supports you for the redeployment of the modifications you made. And again, all steps needed to deploy your site is done in minutes. No big deal to bring your real website online.
All you need to know is available with the tutorial J1 in a Day. You learn how to create websites based on the J1 Theme. This tutorial focuses on the basics of using Jekyll, managing J1 based sites, and deploying the modifications of your site.
Start the next journey, go for J1 in a Day.