Currently inside the database we have a URL column which was saving the gardens own websites and fb pages. We don't really need this anymore as the idea is to have a centralised information platform that you would not need to outsource! The great thing about the backend being set up with urls though is that we can use these instead as IMG urls!
[x] Update the Seed file to include a good cover photo img url for each garden (just google the garden and make sure its a big enough photo)
[x] run the new seeds and make sure the correct data (including our new IMG URL's) is being passed to frontend using Insomnia!
[x] create a GardenHeader folder in subcomponents. Inside create a GardenHeader.jsx and a GardenHeader.test.js
[x] inside GardenHeader.jsx dynamically render the IMG and the title overtop the IMG based on which garden the user is viewing. You will need to get your head around TailwindCSS and styling components. Talk to Prue if you need help with this.
[x] Render this component inside App.jsx so that it always shows if the route hits /gardens/:id/. Hint this is not an exact path as it will have different endings based on the users nav.
[x] make sure it is above the userNav check Figma for reference!
[ ] Write tests, we want them to prove that they render the correct garden based on the URL but also that they show on every gardens/:id route including /about /events /news etc.
When the user goes to /gardens/:id/:nav we want the Garden of their choice to display a photo of that garden and the name of the Garden overtop. check the Figma for reference https://www.figma.com/file/QbkygWObPAOmQzMRvVV6ma/gardenz?node-id=2%3A123.
Currently inside the database we have a URL column which was saving the gardens own websites and fb pages. We don't really need this anymore as the idea is to have a centralised information platform that you would not need to outsource! The great thing about the backend being set up with urls though is that we can use these instead as IMG urls!