arqex

This is part of a frontend based CMS that I've been developing for a while. I have stopped working on it, but I thought that react-tiles deserved to be open to the community for anyone that may think it's useful, so I decided to write some docs and a demo and share it with the world.

Since frontend apps know how to load any app route, there is nothing that block us from load more than one route at the same time. That's the idea behind react-routes, a simple React component that divide your app in tiles, loading different routes in them.

This is one of the projects I have that I don't have much time to work on it, so every little help is much appreciated :)

Hope you like it.

This is part of a frontend CMS app I've been working on for a while. I have stopped working on it, but I thought that react-tiles deserved to be open to the community for anyone that may think it's useful, so I decide to write some docs and a demo and share it with the world.

Since frontend apps know how to load any app route, there is nothing that block us from load more than one route at the same time. That's the idea behind react-routes, a simple React component that divide your app in tiles, loading different routes in them.

This is one of the projects I have that I don't have much time to work on it, so every little help is much appreciated :)

Hope you like it.

https://github.com/arqex/freezer

It is a global store that can be modified inside of the components safely, as if it was component's local state.

A change anywhere in the store will trigger an update event at the top of the store, notifying the rest of the app. So if you use a part of the freezer store as local state for your component, you'll get both requirements:

* Any change to the local state will rerender your component - ease of use. * Your component's local state won't be hidden anymore. You will be able to access it from outside the component.