In my experience, if you need to customize the look and behavior of the editor, Lexical Framework is the way to go. But be prepared to invest a lot of time.
If you’re fine with the default setup, you might want to go with ProseMirror or TipTap instead.
Page Mosaic CMS is an open-source platform optimized for AWS to efficiently host static websites.
It simplifies the process of creating, managing, and publishing content online.
Page Mosaic enables users to host static websites on AWS, leveraging AWS services such as S3 for file storage (images, videos, etc.) and CloudFront for content delivery network (CDN) capabilities.
SiteBud CMS doesn't require a database, and all your content is stored in your own GitHub repository. It's also currently free and is engineered to not increase your hosting fees. I created this CMS to provide a simple, cost-effective solution for our NextJs projects.
Here are a few key features of SiteBud CMS:
1. It's a separate entity from your website, meaning it won't increase your hosting fees.
2. It doesn't require a database, which can be a significant expense with other CMSs.
3. It integrates with services like GitHub and Amazon S3, allowing you to have control over your website code and content.
4. It comes with ready-made website templates, but allows for customization with your own code structure and components.
Vercel does not require authorization through GitHub, so it does not receive my personal access token.
Vercel does all operations with a GitHub account through its GitHub App, which the user can install on his account and give permission to access the repositories. That's why I don't understand how Vercel does create a new repository.
"You can see what scopes your personal access tokens have by going to the "Settings" page of your GitHub account and clicking on "Developer settings" in the left sidebar. Then click on "Personal access tokens" to see a list of your tokens.
Each token in the list will show the scopes that it has been granted. You can click on the name of a token to view its details, including its scopes."
All components are written for this demo only. You can install Webcodesk locally and write any components and functions - Webcodesk will parse the code. Please find the User Guide in the GitHub repo.
Unless the engineer in question isn't responding to emails, then your company can use the same strategy with GPLv3 code as they would with any propriety code: Pay for a license.
Or does your company not use any propriety tools at all? (It's alright if they don't; being 100% reliant on permissive open-source licenses is a nice achievement in-and-of-itself).
The Webcodesk online version is designed to demonstrate the components and how they can be combined in an application. The components themselves can be created in the local version - it is Open Source.
The tutorial project uses a limited number of components. The purpose of the tutorial was to show how to work with the components, as well as Webcodesk features. But you can create components and add properties only in the local version of Webcodesk.
If you’re fine with the default setup, you might want to go with ProseMirror or TipTap instead.