Jekyll site progress update
It seems like my best options are:
- Additionally, set up an LLC for extra legal protection
Then I looked into using GitHub pages to host a “support url,” which is the other condition that Apple requires. A “support url” is what Apple calls a website for providing users a means of accessing information about your app, report bugs, submit feature requests, troubleshoot problems and contact the developer for assistance. It seems like a glorified email address, but in the long run it is better to have a website for your app. That way, users won’t need to constantly bother the developer for common or Frequently Asked Questions, and the site itself can serve to promote the app as well.
- set up Ruby, Gems, Jekyll
- set up GitHub Pages repo to host this website
- published this Jekyll website to GitHub Pages
found out how
baseurlworks when testing on localhost:
The way you organize your GitHub Pages repo affects your website’s domain. If you follow the Giraffe Academy tutorial, you would need to set
baseurl = <YourRepoName>
If you follow this other tutorial, your website’s GitHub repo name will be in the format
<UserName>.github.ioand you do not need to set
The first option is similar to how you would build a GitHub Pages site for a particular GitHub project. Let’s say that you finished writing a node.js API that has a repo on GitHub. If you want a nice website for the documentation of the API, you would create a new branch called
gh_pagesand publish the GitHub Pages site with all your Jekyll files from there. Then you would choose the
gh_pagesbranch to publish the GitHub Pages site from.
The second option creates a conventional, personal website (GitHub refers to it as a ‘user’ or ‘organization’ site). If you choose this option, you won’t be able to choose which branch or folder to publish from
If your site’s source files are located in the default publishing source —master for user and organization sites— then you cannot choose another branch or folder to publish the site from.
Otherwise if your repo is primarily for some other project and you just need a website for it, create a
gh_pagesbranch and go to your settings to choose the
gh_pagesbranch to publish from. Then you will need to use
baseurlin Jekyll as described above.
- got this Jekyll site to use new theme, a Gem plugin called Time Machine
- installed Atom to work on the project
- mixed layouts from the default theme ‘Minima’ with ‘Time Machine’
- went to martial arts class in the gym’s new location
- attended Zoom meeting to learn the history of Sayoc
- got a basic navigation menu to work
- purchased my name as a domain! www.alexbeaty.com from www.namecheap.com with free WhoIs Privacy Guard with no expiration
- did you know that some countries require their country’s TLD to preserve the owner’s privacy?
- OVH is a commercially registered TLD domain that also conforms to privacy by default
- worked on using ‘layouts’ for webpages with Jekyll
- reorganized Minima SCSS files to work with this project, combined with Time Machine’s styles
- studied Jekyll with Giraffe Academy on YouTube
- tried to configure CNAME for www.alexbeaty.com to redirect to this GitHub Pages website
- started implementing pagination for indexing my blog posts, encountered build errors
- website is almost fully functional
- pagination to list blog posts, and navigation bar are complete
- reorganized the ‘Mancala’ pages section of this website
- embedded pp onto website page and used CSS for center alignment