At this point we can finally start to think about loading images to the system. However, before we start uploading images we need to put the pieces in place to store data relating to images.
We previously created a landing page to administer or manage a property but we have left it blank to this point. In this post we will work on this page.
In this post we will begin wiring up the ability to manage settings in our GUI.
This post is going to feel like a bit of a repeat of #25 where we added the back-end to support the administration of Properties. In this case we are going to add the back-end support for Settings. We will use settings when we manage individual properties, specifically, the settings we want to manage will be applied to the images loaded to the Media Library.
In this post we will continue where we left off in the previous post. We will add the required back-end pieces to manage properties.
In this post we will continue to integrate our application with the Redux store by wiring our registration process to the store.
In the last post we added Redux to our application, we created some authentication actions and an auth reducer. In this post we will wire up Redux complete our Login workflow. We will follow a common pattern in React by using container components.
I have spent some time debating how to best handle state in a "modern" way in our application. I keep coming back to using Redux. In this post we will make the case for using Redux and wire it into our application.