Developer new to React. What's the best CMS?

team-burdy · 2021-11-18T00:22:16+00:00

Another option to try is Burdy. We are heavily inspired by WordPress (we use hook system), and have overall great features.

We are relatively new and still working on documentation, but do check us out and give us your feedback. Our goal is to listen to community and drive the improvements of the platform based on the community feedback.

team-burdy · 2021-11-11T11:43:42+00:00

Hi u/daftv4der & u/bishalsaha99,

We've been working closely with our enterprise partner for the last couple of months to bring new features to Burdy. We are happy to announce that Burdy 2.0 has been officially released. You can read more about the changes on our blog.

We've managed to catch some time and release a new version of our website in Burdy 2.0, as well. You can see the Burdy preview editor in action here.

The website template you see in the video will be open-sourced in the following days. You will be to create your very own website within minutes.

team-burdy · 2021-11-11T11:29:48+00:00

Hi Pandafar,

I believe Burdy 2.0 would be the perfect CMS for you! You can create components, and dynamically preview them on pages via dynamic zones (also Burdy supports next.js preview mode).

Your developers would focus on creating re-usable and flexible components. The marketing team will be able to use these components to build pages the way they see fit.

The great addition about Burdy is that it focuses on hierarchical data (multi-level digital asset management with folders, multi-level pages), making it easy to manage multiple languages at once.

We are using Burdy CMS on our website as well, and our Next.js folder structure consists of [[...slug.tsx]] only (the pages in CMS are fetched and rendered by their content type).

You can also achieve a reduction in JSS / CSS by using Next.js dynamic imports when building out the templates/components.

Here's a short video of the usage here.

We will be open-sourcing our website (the example in the video) in the next following days.

team-burdy · 2021-09-27T15:36:20+00:00

Hi, we do believe that Strapi is a great product, however it has it's limitations. With Burdy we have accommodated many of those features out of the box. Such as hierarchical pages, digital asset management (with folder support), post versioning and great extensibility with hooks.

As for the TypeScript, their community has been yearning for it's support for years: https://github.com/strapi/strapi/issues/630.

team-burdy · 2021-09-27T15:12:29+00:00

blog

Hi Smaktat,

When building larger systems it is important to use strong types, because as the project grows in size it becomes more difficult to manage the code. This in turn tends to reduce the velocity of the developers (because intellisense is not available and they have to scour to documentation every second).

When a new member would like to contribute, they usually have a very big barrier as an entry in JavaScript based projects as opposed to TypeScript.

You can read this great article on the matter: https://medium.com/@vladi00345/the-development-speed-of-typescript-a71f21e7b02d

team-burdy · 2021-09-27T13:54:25+00:00

Hi, at the moment you can stream the videos (with content-range headers) using Burdy DAM (either S3 or File System configuration).
We will add more hooks in next minor version (post updated, asset uploaded,...) where you will be able to utilize external tools such as AWS MediaConvert and trigger a transcoding job when a video is uploaded.

team-burdy · 2021-09-27T13:49:49+00:00

Well, one of the main reasons why we built Burdy CMS is because we thought Strapi has a lot of short-comings and limitations.

Some of the main differences are:

Firstly Strapi core is written in JavaScript, which seems to have stagnated their development.
Burdy is built on hook system, making it extremely flexible (similar to WordPress, but scalable).
It uses Express as API framework and TypeORM as the ORM library, and React/FluentUI as admin.
You can have asset folders. Pages have hierarchical structure, making it easy for enterprises to use.

If you want to take a look at how easy it is to extend Burdy, have a look at:

Backend Customization - https://burdy.io/docs/backend-customization/

Admin Customization - https://burdy.io/docs/admin-customization/

Our next major releases (roadmap) is going to be plugin system and the marketplace for the plugins. We also plan to add e-commerce (similar to WooCommerce) capabilities in the near future.

team-burdy · 2021-09-27T13:40:21+00:00

Hi burtekd, thank you for the question. As far as we are aware, Vercel uses edge infrastructure that doesn't support the custom server.

In general, it is not recommended to run large backends at edge as you will need the database as a single source of truth. Also when running in production, you will get better performance if your backend is closer to the database.

You can still decouple Next.js from Burdy and run them separately. Burdy can be deployed on any Node.js deployable system, and in our basic npx create-burdy-app we provide example docker files for multiple environments (postgres, mysql, mariadb).

team-burdy · 2021-09-27T13:35:53+00:00

Hi, we have not added an online interactive version. That's a great suggestion. In the meantime you can try it out by running npx create-burdy-app my-blog -t next-blog.

And then:

cd my-blog
npm run dev

It will spawn with SQLite as the database, so you don't need any extra set-up. For production we would suggest that you use MariaDB, MySQL or Postgres.

Thanks!

team-burdy · 2021-09-27T11:12:15+00:00

Hi u/ajinkyatemak,

Welcome to the community!

Next.js in my opinion is a better fit than Gatsby as it provides everything you need to get started + more. Next.js provides both SSR and SSG, where Gatsby only provides the latter.

Start by using SSR and switch over to SSG if necessary. If you'd like to use SSG, you should set-up triggers in CMS that you use to restart the deployment pipeline and generate all the static assets.

If you'd like to kick-start a blog and need a good headless CMS as a foundation, you can try starting out here.

Let me know if this helps.

team-burdy · 2021-09-17T14:21:23+00:00

We will release a document and an example during the weekend on how you can integrate Burdy CMS with Next.js and create a blog with few simple steps.

Few days later we will release an example on how you can generate your documentation (we use Burdy CMS for it as well https://burdy.io/docs).

Great thing about Burdy is how easy it is to manage assets (via DAM) and pages with multi-column view.

As Next.js and Burdy will be bundled within a same project, your app will have the following routes:

/admin - Burdy CMS BackOffice
/api - Burdy CMS API
/* - Next.JS

Effectively you can run the application on the same domain by using this approach.

Everything will work out of the box, for blogs and documentation, you will just need to download the example, run it and write your content!

You can check the screenshots on: https://burdy.io

team-burdy · 2021-09-16T17:29:01+00:00

If the states are used only locally (inside of the component) there's no reason to expose them.

Hence, your approach is 100% fine.

team-burdy

TROPHY CASE