Releases: pages-cms/pages-cms
1.0.0: Pages CMS now runs on Next.js!
This is a really big one. It's been ready for a few months now, and I finally got around to releasing it.
Let's go through the main changes:
Rebuilt on top of Next.js
The newest version was entirely rebuilt from the ground up with Next.js 14, using the App Router, shadcn/ui, drizzle and lucia under the hood, hopefully making it easier for others to contribute.
I'm also using Vercel and Turso for the (free) online version, and Resend for emails.
The Vue.js version has been archived in the vue branch. I do not plan on supporting it moving forward.
Free forever (no more "Pro")
I've merged all of the "Pro" code into the Open Source version and plan on keeping all the features on the roadmap 100% free and Open Source. The online version will remain free for now as well.
Github App and fine-grained permissions
Pages CMS is now using a proper GitHub App for authentication. This was required to enable certain features (e.g. invite users by email) and provide much more granular permissions when installing the app. You can now select specific repos within organizations.
IMPORTANT: the switch to the new version means you will need to login again. If you run into issues, especially if you were already using the Next.js version (at https://next.pagescms.org), reach out to me and I'll help you out: [email protected].
New landing page
I completely revamped the landing page, improving the repository search and adding a history which means you won't need to constantly search for projects you recently opened.
I've also improved the "Create from template" flow. For now I'm only displaying 3 templates, but there are more in the pipe.
Brand new editor
I rewrote the editor and gave it more of a Notion-style look and feel. I'm actually considering splitting it off from the main codebase as it could be helpful for other Next.js/React projects.
Invite collaborators by email
The first Pro feature that was merged into this is the "Invite by email" feature. You can now add colleagues to projects without requiring them to create a GitHub account. Granular permission management for email users is on the roadmap.
Updated documentation
The documentation is 100% up to date (same for the README).
IMPORTANT: the format option for date fields now follows the date-fns format. You need to update your .pages.yml file.
And there's more...
- Tons of small bugs have been fixed, and lots of small features have been added.
- Custom fields are a lot more powerful (and robust).
- I've made a few improvements to the media manager, including extending the list of formats (e.g. webp).
- The app is overall way more secure. Not only because of the authentication strategy, but also thanks to enforcing strict schema validation both in the front-end and the backend; users will only be able to commit changes that follow the format you've defined for the content.
0.4.2
Hotfix 0.4.1
Bug fixes
- Handle images with special characters (e.g. spaces) properly now when switching between rich-text and code editors for markdown.
- Fixed live updates of configuration for repo names with case.
0.4.0
0.4.0 is here with a completely refactored system for fields. The new approach is a lot more scalable and allows you to define your own custom fields if you decide to do so. I hope to add a few new fields in 0.4.x, including key-value, files and references. More on that soon.
More info is available on the website: https://pagescms.org/docs/custom-fields/#sort-function
Do let me know if you ned up writing your own fields or even create a PR if you think this should be part of the built-in fields.
Changes
- Refactored all the built-in fields.
- Updated Editor, Field and Collection components to handle the new fields system.
- Documented custom fields.
Hotfix 0.3.6
Bug fixes
- Fixed an infinite loop on image lists introduced by the change made to address #41.
Hotfix 0.3.5
Bug fixes
- Fixed broken custom error message for field pattern.
- Adjusted tabs for repo menu on mobile.
0.3.4
This release mostly bring better branch management.
There will be one more patch for 0.3.x to add the ability of editing the filename while creating/editing a file (rather than using the rename feature). After that, I'll focus on 0.4.0 with improvements to the field components, helping with custom fields and adding a few more default fields (e.g. files, key-value).
New features
| Menu | Modal |
|---|---|
 |
 |
- You now always have the default branch and the current branch (if different) listed at the top, followed by other branches for a total of up to 5 branches.
- You can see all branches by clicking on "Manage branches".
- From the branch modal, you can search for branches and create new branches.
Improvements
- Made lists more compact.
- Reworked the main repo and branch navigation.
0.3.3
Just back from Taiwan, I finally had the time to put a new release together. Unless I have patches/hotfixes to release for this version, I'll be working on 0.4.0 to bring some much needed changes to the fields. Not much left after that to get to 1.0.0.
New features
- Create a repo from a template: you can now create a new repository using one of the templates available, including blog templates for Astro, Next.js, Eleventy and Jekyll. I'll be adding Hugo and Nuxt shortly.
Improvements
- Updated the rich-text editor to retain HTML elements in markdown when they include a
styleorclassattribute. It also now retain<img>elements with awidthorheightattribute. - Started to move logic around for view and sorting of fields in collections, in preparation of custom fields release (0.4.0).
Bug fixes
Hotfix 0.3.2
Rework the collection view logic to properly escape HTML and prepare for modular custom field view logic.
Hotfix 0.3.1
Addressing bugs when dealing with images due to the fact that on Github, owner and repo are case insensitive (e.g. pages-cms/pages-cms is the same as PAGES-CMS/PAGES-CMS).