We should probably decide on how we're going to structure our client components before they get too out of hand. Need to look into it more.

https://www.robinwieruch.de/react-folder-structure

So we want the sidebar to work in a contextual way, when we're on the home page, it displays a list of the first categorisation of threads, Golf/Rugby/etc. Similarly when we're on Golf home page it should display the list of Golf subcategories. The Hot Posts section should work similarly, populating itself depending on what page they're on.

We need to set up a new route for the individual category pages something like /category/{category_id} that will have Golf/Rugby as the category_id and be used to work out how things are generated. Similarly we might need something like a Category component that gets rendered on these routes. (Although maybe just refactoring the Home Component could be better if they're structured very similarly)

Two main options that I can think of for how these contextual components (Sidebar, Hot Posts, etc) are generated:

1. Using the current URL match.params inside of each component for this logic. The hotPosts and Sidebar components will just check the current URL and call the appropriate functions to populate/style themselves,
2. Otherwise, we could put this logic inside the parent component (eg Home, CategoryPage) and just pass down appropriate, broken down info/ids etc to the Sidebar/hotPosts.

I'm leaning towards 1. Also, I think it could be pretty easy to just have a generic component that works for both the Home and Category components as they are now, but I'd imagine there will be some differences between them in the future, so I'm leaning towards two separate components for them.

Try find some convention that we can use across all pages like Restful routing or something

Should probably be a component of itself
Present on all pages, should look into best way to do this