We believe that the Flexibility we’ve given Flamelink is going to achieve that in 5 ways:

Everyone has their favourites. React, Angular, Vue to name but a few. While I’m pretty sure we could start a conversation that would go on forever about which Front-end Framework is the best, we may never reach a universal consensus. And that’s ok. At the end of the day, you should be able to work within a framework or language that you’re comfortable with. That’s why Flamelink’s headless solution handles content — no more, no less, and offers Developers the Flexibility to use any Front-end.

With current CMS’s, you’re kind of limited to the content types that come out the box. Eventually, it hits the straps and you need to come up with a new plan of action — which usually requires more time and more budget. Ain’t nobody got time for that.

Flamelink offers a slick drag and drop content builder to create your own content types. This also allows you to quickly put together a simple to use form for content editors and in turn create the API endpoint for the developer.

Within Flamelink’s slick User Interface, users can add, update and delete the content types created under the schema section.

They can upload any type of file to their Firebase storage bucket and organise them in their creative folders and can easily create and structure menus for web or mobile Apps, all within the navigation area.

Here’s the thing. Content Managers shouldn’t need to get their fingers dirty in the code base, and Developers shouldn’t need to stop writing smoking hot code.

The user section integrates with the authentication service from Firebase. This means that users created in Flamelink will automatically be created in Firebase. Users can be assigned to a permission group created in the permissions section for each custom content type and built-in feature.

Multiple languages, no problem. Serve up different languages instead of loading up a brand new project in Firebase for each one.

While the best testing environment is the production environment, clients and PM's don't seem to agree. Test great ideas in staging/sandbox environments before pushing to live.