Flamelink.io VS Craft CMS

Flamelink.io Reviews

Craft CMS Reviews

Flamelink.io mentions (5)

• The best CMS on Firebase hosting.

  You also have https://flamelink.io/. Source: over 2 years ago

• Beginner Question: How would you go around adding a CMS to a Firebase-Svelte App?

  I've looked at PushTable and FlameLink already, but PushTable didn't seem to work at all, and FlameLink is really out of the budget for a small site like this. Source: over 2 years ago

• Learning to cook at home with Parsnip - built entirely with Svelte!

  I'm not sure I'd say Firestore is the ideal "serverless" backend for a Svelte app, but it sure does make it easier to develop and iterate faster. Plus with Flamelink it's provided a decent solution for use with a full-blown non-technical CMS system that we didn't have to build. Flamelink offers some primitive relational db style functionality (e.g. Some document fields can be references to other documents) which... Source: almost 3 years ago

• Learning to cook at home with Parsnip - built entirely with Svelte!

  We've gone with Firebase for our "backend" needs. This is primarily just firestore for data, cloud-functions for database sanitization, auth, and basic usability analytics. We're using it in conjunction with a CMS service called Flamelink that allows the non-technical folks on our team to add content to firebase in reasonably intuitive way without us needing to build/maintain a second app just for... Source: almost 3 years ago

• Build & Sell Apps, Not Content — Angular with Flamelink and Firebase

  The main draw of any CMS is that it lets authorized users customize content without having any knowledge of how to code. If someone knows how to use a text editor, then they should be able to create new content using the CMS. I’m going to teach you how to set up Firebase and add Flamelink to your Angular application. You’ll have it up and running in short order! - Source: dev.to / over 3 years ago

Craft CMS mentions (31)

• Different flavors of content management

  The most typical approach is having a CMS admin panel sit somewhere on the server; everyone with an account uses this. This is a very convenient approach, especially when working with a team. This way, many people can work on different articles simultaneously without worrying about potential conflicts or overwriting stuff. The only con is related to security - everyone can try to get inside, and if you forget to... - Source: dev.to / 9 months ago

• Go with PHP

  PHP has a lot of top tier CMSes. IMHO bunch of them are even better than Statamic. Craft CMS (https://craftcms.com/) is a lot more mature database based CMS. Kirby (https://getkirby.com/) is better at flat-file and has a lot better admin interface. Twill (https://twillcms.com/) is better integrated in Laravel and is fully open-source. Statamic mostly feels like it's sitting besides Laravel and they call themselves... - Source: Hacker News / 12 months ago

• Stack to build and deploy a fully functional personal blog?

  You're basically looking for any CMS that supports headless mode. E.g. Strapi (https://strapi.io/, NodeJS based), CraftCMS (https://craftcms.com/, PHP based) or countless others. Source: about 1 year ago

• A mate of mine built a cool little Tottenham Database showing the history of spurs.

  It's built on Craft CMS. Makes the relationships between elements (a match and a player, for example) super easy. Source: about 1 year ago

• Creating a CMS with React, what should I look at?

  Is there a reason you aren’t using an existing CMS? There’s a lot that provide all the UI functionality you are talking about and then expose it via a API to be consumed in your front end. https://craftcms.com is one option I’ve had good success with. Source: over 1 year ago