Problem
Right now any user with a valid auth token can retrieve any tag resource as long as they know the ID of the resource. We should return a 404 (Not found) error if someone tries to retrieve/update/delete a resource that does not have a matching account_id

Solution
In the show, update, and delete methods of the tag controller, let's add an authorize plug (middleware)

Feature Request

If you don't set your environment's URL options, generated URLs will contain example.com which is only handy if you're working on the new example.com.

Is your feature request related to a problem?

This comes up frequently on Discord, even though it is documented: https://docs

What is the current behaviour?

Uncommented Ruby code doesn't get displayed to the client, like so:

paragraph text: 'I will be rendered'
# paragraph text: 'I will not be rendered' 

I think this is well, but sometimes we might want to deliver HTML comments. Therefore, I propose a comment static core component, based on [the W3 reference](https://www.w3schools.com/tags/tag_c

The link in Step 1 to the troubleshooting section for the server hanging is broken.

It needs to be amended from try [this](###-problems-with-dependencies) to try [updating your deps as explained in our troubleshooting section](#problems-getting-the-initial-server-running)