GraphQL CMS, the second version is already publicly available.

Original article in English.

In my previous article, I told about the first version of CMS: Automatically generated CMS use your ready-made GraphQL schema , and if you haven’t read it yet, you can read it for general understanding of this module.

In this article I will briefly talk about the second version of GraphQL CMS . You will see what's new in the second version and what to expect in future versions.

Briefly about the project:

GraphQL CMS is an npm module that can help you save a huge amount of time that you usually spend on integrating your project with a CMS or developing a self-written administrative panel.

All that is required of you is a GraphQL scheme, the module will do the rest for you!
The module automatically generates a full-fledged CMS using all the entities from your GraphQL scheme and with each new change in the GraphQL API, the CMS will be automatically updated according to the changes.

Project philosophy:

Simplicity. You will not need to change absolutely nothing in the existing project! You are free to use any approaches and architectures to develop, imagine that GraphQL CMS is a simple React component that you can place inside any other component, for example, to add a footer and a header or just as easily place it on a separate route.

For the same reason, there is no authentication system in the module, so you are free to use any solutions to make your CMS and API as secure as possible.

I personally recommend FeathersJs . Great, easy to use, free product.

What's new in the second version:

The module is very flexible to use and even if for some reason you don’t have enough standard features, you can easily extend the CMS with your components with any functionality, so you have 100% of the possibilities to solve any task you need from the CMS.

But even without a CMS extension with its components, the module initially provides a complete list of the capabilities of any standard CMS:

• [New] Documentation
• [New] Support for GraphQL Type properties with any number of nested objects
• [New] Support for GraphQL lists, with automatic pre-populations of options for a list, if it is a sheet of another GraphQL type, or if it's just an arbitrary sheet, it will be possible to add new items to the list
• [New] Ability to upload files, and select arbitrary properties for GrpahQL Type to which you need to use this function, instead of the standard form
• Pagination
• Sort menu items in the sidebar and all other fields
• The ability to fine tune the CMS
• Easy to expand with any other features and components.
• Full CRUD support

As you can see, GrpahQL CMS has decent features right out of the box.

TODO:

• Test cases and commented code to make it easier for other developers to participate in the project

If you have any suggestions or advice on the project, write in the comments.