Earlier I introduced the first version of CMS: Auto generating CMS based on your GraphQL schema, and I am highly recommend you to read that article too if you haven’t yet.
In this article I want to shortly introduce to you the second version of GraphQL CMS. You’ll find what’s new and what we have and what else you should expect in future release.
###Shortly about project:
GraphQL CMS is a npm module which can save you a lot of time you’re currently spending on integration with some CMS or building your own admin-panel. All you need to do is just provide your printed GraphQL schema in config object and that’s it, module will do the rest of work for you!
It will automatically generate fully-functional CMS with all your GraphQL essence, and on any changes in schema it will dynamically catch all changes and generate new menu points, fields and etc.
###Product philosophy:
Simplicity. You don’t have to change a line of code in your project, so you’re free to use any architecture you want. Consider CMS as simple React component which you can render wherever you want, inside of other components. For example to provide header and footer or on separate route.
For the same reason we don’t provide authentication system, so you can use any approach to secure your CMS and API you want. We recommend to use FeathersJs, it’s easy to use and a great free tool.
###What’s new and what it support:
The module is pretty scalable and has ability to extend CMS with any custom functionality so it can solve 100% of your needs from CMS.
Even without custom extending CMS it will automatically give you following functionalities, which is more than enough for 90% of needs from CMS:
- [New] Documentation
- [New] Support of nested GraphQL Type fields, any deeps
- [New] Support of GraphQL List, with auto populating if list of other essence from data-base, or with ability directly create new items in list if it’s just a list of some items
- [New] Ability to use file uploading system and refer it to any field you want
- Pagination
- Fields and Side menu points ordering
- Ability of detailed configuration with custom labels for fields, menu points, and etc
- Easy to extend with custom components where you can use any other custom functions you need
- Full support of CRUD
As you can see CMS supports a lot of useful stuff out of the box.
###TODO:
- Test cases and commented code, to make it easier to contribute
If you have any suggestions to what else you would like to see in the new release please feel free to give your advice.
