Documenting my experiences building a static site using Hugo: Part 2
The basic process for any SSG is: Markdown files (or similar) go in, static site HTML comes out. The project itself consists of a folder, containing a config file for the site name and address, page navigation, etc.; a sub-folder for content; a sub-folder for static, callable items, such as images; and other sub-folders for layouts, themes, and patterns. The files are created locally, hosted through a service like GitHub, then built and deployed through a platform like Render.
Before jumping from local development, Hugo has a great note about clearing the
In my case I created a private repo activated with a one-sentence README.
Note: Some folders did not copy, but those were empty in the Quickstart folder.
Creating a new account and loggin in were seamless because I was able to sync my GitHub account.
New Web Serviceand give Render permission to access your GitHub repo:
Only Select Repositories
The base URL in the repo
config file needs to point to the website. Remember to update this file with the necessary information.
In Render: Under the Settings tab for your service will be some options listed for Custom Domains. Follow the steps to ensure your custom domain name is routing to the Render build. For my page, this involved configuring the Namecheap DNS.
Now that the site is launched, editing and adding content is as simple as any regular GitHub workflow!