Posted on emTr0.dev.

It happens to everyone. You start or get back into something and you either get distracted, busy with something else or lose motivation and take a break. This happens with coding too. It's happened to me, requiring me to revisit "intro to" courses to get a refresher before continuing with the next step of the learning process.

For example, I've taken a bunch of Python courses and got far in the Coursera curriculum but it's been so long since I've done anything with Python, I'd need a basics refresher if I wanted to continue to learn anything more advanced. More recently, I completed the Responsive Web Design certification at freeCodeCamp but again took too long of a break (because life), so I found myself taking some intro to HTML, CSS and JavaScript courses on Codecademy before continuing the JavaScript Algorithms and Data Structures certification.

If this happened or is currently happening to you, I put together a list of "intro to" courses that should help you get back into learning and advancing your developer skills. The other advantage of going through these again is they may have been updated with new concepts and technologies you weren't aware of when you first learning the basics.

Intro to HTML courses:

Intro to CSS courses:

Intro to JavaScript courses:

Feel free to comment with your own suggestions. 🤓

Posted on emTr0.dev

emTr0.dev is now pretty much how I want it in terms of design and setup (comment system coming soon) so as promised, here's a quick guide on how I got everything working. The sources for this guide as well as additional resources for the platforms are linked at the end.

Before jumping into it, I wanted to mention the GitHub Student Developer Pack. If you're currently a student interested in anything related to developing websites and software, domains, security, productivity and more, you can sign up here:

GitHub Student Developer Pack

The Dev Pack includes (typically) a year of free access to some of the premium services I use in this guide. The way I set things up keeps everything completely free for the average user but if you're looking to do more than what the free versions allow you to do, you'll at least have a year or so of free access as a student.

The final product of this guide will be a JAMstack-based website. What is JAMstack?

You may have already seen or worked on a Jamstack site! They do not have to include all attributes of JavaScript, APIs, and Markup. They might be built using sites built by hand, or with Jekyll, Hugo, Nuxt, Next, Gatsby, or another static site generator...

The thing that they all have in common is that they don’t depend on a web server.

While the end-product of this guide will indeed be a JAMstack site, our use of a Heroku web server to run the actual Ghost installation kind of makes it a hybrid. They're still independent of each other so if Heroku goes down, your site won't. The benefit of using Heroku is you can access the Ghost CMS from anywhere vs just pushing to GitHub from a local installation, where you'd only be able to make changes from that same computer. Using the JAMstack version also minimizes the use of your Heroku resources and you'll also be able to get a free SSL certificate with Netlify, where you'd need to upgrade to get that with Heroku. Moving on...

What you'll need for this guide:

• Free Heroku account.
• Free GitHub account.
• Free Netlify account.
• Custom domain (optional but recommended for that "professional" look, available free through some services in the Dev Pack).

Once you created the above accounts, use this link to one-click deploy a Ghost v3.X installation to your Heroku account. Make "App name" something unique. For my site, I used "emtr0-dev" since my custom domain would eventually be emTr0.dev. Make sure you set the APP_PUBLIC_URL under the "Config Vars" section to this app name for now. You'll change this later as you integrate the rest of the JAMstack setup.

This one-click deploy option automatically sets up accounts for the following:

Cloudinary : To store images and video resources; You can replace Cloudinary with S3.

JawsDB MySQL: To store actions, emails, integrations, members, permissions, posts, posts meta, roles, tags, settings, users etc. From Heroku app overview page, click on the JawsDB add-on you installed to access your JawsDB database dashboard. You can use the credentials and MySQL Workbench to connect to your JawsDB to access your data.

Mailgun: To send, receive and integrate emails. Your blog collaborators must be authorised receipents and agree to receive emails before they will receive emails from Mailgun.

We won't really be using these service but I did occasionally use Cloudinary to host some images that I used in the theme's design, so that's handy. If you decide to use Heroku to serve your Ghost site instead of the JAMstack site with GitHub and Netlify, you'll also have that option at this point and don't need to continue the guide. If you want to do that, just scroll down to the bottom and refer to the Heroku docs on how to setup a custom domain. Remember though, you won't get a free SSL certificate if you use Heroku this way.

Once you complete the Ghost setup on Heroku, go to https://YOURAPPNAME.herokuapp.com/ghost and finish setting up your admin account to access the CMS.

Once you're done setting up your Ghost installation on Heroku, use this link to deploy a Gatsby Starter Theme for Ghost on Netlify (from the Ghost GitHub repo). The process will walk you through connecting your GitHub and Netlify accounts, and then setting up a repo for the files that will be served by Netlify. Feel free to make this repo private if you'd like. The auth connection allows the repo to be private without losing access to what needs to be served.

Next, you'll need to connect your Heroku Ghost installation with your GitHub/Netlify site. This is what makes Ghost "headless", allowing you to serve your content through the Netlify-served static website. To do this, go into Heroku Ghost > Integrations > + Add custom integration. You can name this integration anything but the most appropriate name would be "Gatsby". Copy the "Content API Key" and "API URL" and save these somewhere you can easily access for an upcoming step.

Go to your GitHub repo > .ghost.json file and edit it right inside GitHub. Replace the "apiUrl" and "contentApiKey" with what we just copied from the Gatsby integration. Save the changes.

Next you'll need to create a hook/webhook to make sure your changes in the Heroku Ghost CMS are being deployed by Netlify on your static site. First go into Netlify > Your site > Settings > Build & deploy > scroll down to "Build hooks" and click "Add build hook". Appropriately name it Ghost, leave "Branch to build" as master and then click save. Copy the generated URL.

Go back to your Heroku Ghost > Integrations > create a "Netlify" integration and then under "webhooks" click "+ Add webhook". Name it something like "Build", set the Event to "Site changed" and then paste in the URL you copied from Netlify. Click create to finish the setup.

The next step would be to setup your custom domain. I waited until I had my site at least 90% ready to go since emTr0.dev was previously active, and I didn't want anyone seeing it before it was ready. Once you're ready though, go into Netlify > Settings > Domain management and set up your custom domain there. You'll have to make changes to your domain's DNS settings if it's managed elsewhere and make sure you copy your MX records over to Netlify if you use that domain for email.

Lastly, you need to update your domain settings everywhere to make sure everything is referenced correctly internally. Go into Heroku > Your site > Settings > Reveal config vars and update "APP_PUBLIC_URL" to your domain which in my case was https://emtr0.dev/. Save that and then go to GitHub > Your site repo > src > utils > siteConfig.js and update the settings appropriately. You may need to update the theme files if your initial link exists somewhere that wasn't automatically updated with a Netlify build from your Ghost site. If you used your domain for another site, you can set up redirects to direct visitors appropriately when they click on an old or broken link.

A follow-up change I made (that's optional for you) was adding external link indicators to external links in my site's navigation bar and footer. As you can see, my GitHub and Ko-fi links have icons that let you know you'll be opening another tab by clicking on them. Instructions on how to do this with a resource for icon images are included below. I plan to also do something similar for post/page links but haven't figured that one out yet.

That's it! I hope you found this guide useful. If I missed something or have bad info somewhere, please let me know. I should have my commenting system up and running later today but you can always reach out to me on Twitter, Instagram or Facebook.

Thanks for stopping by!

Sources:

Create a free JAMStack blog using Ghost, Heroku and Netlify

Use Ghost as a Headless CMS for static site - Gatsby + Netlify

Ghost Netlify Integration

Adding External Link Indicator with CSS - Waaz Solutions

Open in new window Icons - Free Download, PNG and SVG

Additional resources:

Ghost Docs

Documentation | Heroku Dev Center

Gatsby.js Documentation

Netlify Docs