Introduction to GitHub User Pages - Part II
Check out #-Link-Snipped-#, if you haven't.
Using Automatic Page Generator to set up your GitHub Page
The first screen you would see after clicking on Automatic Page Generator is the Create a GitHub User Page. If you are aware of <a href="https://daringfireball.net/projects/markdown/syntax" target="_blank" rel="nofollow noopener noreferrer">Daring Fireball: Markdown Syntax Documentation</a>, go ahead and customize the contents, if you have something in your mind. Else, leave it as is for now. Yeah, we will be changing the contents once it is published. Click on Continue to Layouts to choose a theme design for your user page.
![[IMG]](proxy.php?image=http%3A%2F%2Fi.imgur.com%2FVMvxtNg.png&hash=86c905814a45fc497fe03b2140c03e60)
Choosing predefined GitHub User Page Themes
Once you click on Continue to Layouts button, your content will be visible with a few predefined themes. The eleven themes that were available when I was writing this article were:
![[IMG]](proxy.php?image=http%3A%2F%2Fi.imgur.com%2FkTMWPNh.png&hash=1d49e3d786a94ec049afa1ce2c181d4e)
After choosing the best theme that suits for your page, click on Publish button to save the files. The Automatic Page Generator generates a lot of files and directories, required for the theme.
Back to Branch
The main branch, in any repository will be master. So, whatever changes you do in the master, will be reflecting on your page. The branch view of your repository will be something similar to this.
![[IMG]](proxy.php?image=http%3A%2F%2Fi.imgur.com%2FLDucEPE.png&hash=3584b81d91211aea1a1b3cf8b5bccfd9)
Each code change will be a commit here. It says 2 commits because, always there is a first Initial Commit. It is required by all the VCS (or at least Git) to initialise the repository.
Checking out the new User Page
You need to wait for about ten minutes for the GitHub to deploy your page to the production. Else, it will throw an Error 404 (Page Not Found) like this.
![[IMG]](proxy.php?image=http%3A%2F%2Fi.imgur.com%2FYzTbQwS.png&hash=b368a92736a1a331d09f2e131f0d2c42)
After allowing GitHub to deploy your page, when you navigate to the website #-Link-Snipped-#, you will be able to browse through your page. In my case, it would be #-Link-Snipped-# and you can see that my page is now published.
![[IMG]](proxy.php?image=http%3A%2F%2Fi.imgur.com%2F4WimHSf.png&hash=d8d57112a4e714852da44a58a8f13001)
Using Automatic Page Generator to set up your GitHub Page
The first screen you would see after clicking on Automatic Page Generator is the Create a GitHub User Page. If you are aware of <a href="https://daringfireball.net/projects/markdown/syntax" target="_blank" rel="nofollow noopener noreferrer">Daring Fireball: Markdown Syntax Documentation</a>, go ahead and customize the contents, if you have something in your mind. Else, leave it as is for now. Yeah, we will be changing the contents once it is published. Click on Continue to Layouts to choose a theme design for your user page.
Choosing predefined GitHub User Page Themes
Once you click on Continue to Layouts button, your content will be visible with a few predefined themes. The eleven themes that were available when I was writing this article were:
- Slate
- Merlot
- Time Machine
- Minimal
- Leap Day
- Modernist
- Hack
- Midnight
- Architect
- Tactile
- Dinky
After choosing the best theme that suits for your page, click on Publish button to save the files. The Automatic Page Generator generates a lot of files and directories, required for the theme.
Back to Branch
The main branch, in any repository will be master. So, whatever changes you do in the master, will be reflecting on your page. The branch view of your repository will be something similar to this.
Each code change will be a commit here. It says 2 commits because, always there is a first Initial Commit. It is required by all the VCS (or at least Git) to initialise the repository.
Checking out the new User Page
You need to wait for about ten minutes for the GitHub to deploy your page to the production. Else, it will throw an Error 404 (Page Not Found) like this.
After allowing GitHub to deploy your page, when you navigate to the website #-Link-Snipped-#, you will be able to browse through your page. In my case, it would be #-Link-Snipped-# and you can see that my page is now published.
0