0.3.0
This is a big one; this should address all major bugs and improve significantly the robustness of Pages CMS when dealing with incorrect or incomplete settings. I expect to release a few more hotfix releases but will likely then mostly work towards 1.0.0.
In the next couple of days I will also deploy dev.app.pagescms.org with the latest version from the development branch. I'll use it to test releases before deploying to production (it's a tad stressful right now as I worry I will impact users).
If you're interested in helping test future releases before I roll them out, let me know: hunvreus@gmail.com.
New features
- Error-tolerant user interface. You can now have a pretty broken
.pages.ymlfile and still use the CMS. - Support dates from filenames. For example
2024-02-20-my-post.mdwill now set the entry's date to February 20, 2024 without the need for a date field in the content. - Support for content entries without fields. You do not have to specify fields now, even for collections (it will list file names).
- Full support for YAML, JSON and TOML files. You can now manage both single files and collections of files, either using the code or field editor.
- New configuration mechanism with versioned caching.
Improvements
- Improve path handling for media (input to output swaps). Do let me know immediately if you observe any weird behavior with media: hunvreus@gmail.com.
- Improved image modal for image field and rich-text field.
- Completely revamped validation for settings. This includes completely reworked error messages in the editor to make them a lot more readable (e.g. no error on the whole object when only a single property fail).
- Improved redirection rules for incomplete/invalid routes (e.g. incorrect media settings). This will need to be moved entirely in the router in 0.4.0 or 1.0.0.
- Various tiny performance improvements (especially with configuration). I will focus more on this for the 1.0.0 release.
Bug fixes
Lots of bug fixes through the app:
- Fixed the date field by reverting to moment.js (due to a bug from day.js).
- Errors on incomplete/incorrect settings.
- Error converting image paths (input <> output) especially for edge cases (e.g.
media.output: ""). - Lots of style fixes (e.g. mobile collection view).
- ...