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).

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.yml file and still use the CMS.
• Support dates from filenames. For example 2024-02-20-my-post.md will 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).
• ...

Fixing the user dropdown for short usernames or missing profile names.

Addressing errors when media is not defined and a collection/file uses an image field.

Fix some additional edge cases with empty JSON/YAML/TOML files and empty frontmatters.

• Fixing a bug on collection view when media is not defined.
• Saving frontmatter as empty string between delimiters when the frontmatter object is empty.

Preventing corrupted image paths to trip on githubImg service.

• Fix error when frontmatter has null values.
• Prevent error when view fields are invalid in collections.

Fixed a bug with the rich-text field that would crash when media wasn't defined. Remove image insert feature when neither media nor options.input and options.output on the field are defined.

This release includes a lot of bug fixes, improvements and a few key features as I'm still working my way up to a 1.0.0.

New Features

• Configuration linter: when editing settings, you now have real-time validation of your .page.yml file with warnings and errors to help you write something that doesn't blow up your setup.
• Login with GitHub Fine-Grained PATs (Personal Access Tokens): an option I thought would be important to all of you nerds. You can now use a fine-grained personal access token to log in, allowing you to restrict access to specific repositories. I still need to iron this feature out, but it mostly work.
• Support for TOML, JSON frontmatter and TOML frontmatter: you can now specify any frontmatter you like (YAML, JSON and TOML) and create TOML files. This comes with configurable delimiters as well: go nuts.
• Support for JSON, YAML and JSON array files: especially useful for things like data or configuration files. This allows you to manage your _config.yml for Jekyll, an array of authors objects in a _data/authors.json file for 11ty or Gatsby (for example if you use something like gatsby-transformer-json).

Improvements

Lots of improvements, but these stand out:

• Improved upload: in particular for multiple files and drag & drop. I've also added logic for renaming that should avoid any collision when you upload files with the same name.
• Reworked image logic: I've upgraded the way I'm handling images, especially for private GitHub repository. Much better results; I have yet to see a bug.
• Caching: I've added a bit of caching in a couple places (including the configuration files).
• Change of libraries: Moment.js to Day.js, js-yaml to yaml (in particular to get parsing errors and warnings), etc.
• Improved collection view: in particular, you can now display images in the collection view.

Bug fixes

Too many to list. I went through the entire codebase and tracked down most of the obvious bugs and edge cases. I'm sure I'll still find a few here and there.

What's next?

I'm focusing on stability, performance, bug fixing, documentation and a few minor features (e.g. regular file upload field, proper table support in the rich-text editor). I expect to be able to release a 1.0.0-beta in two weeks' time.

Now that I'm over the bulk of the foundation for Pages CMS, I'm switching to feature branches and will stick to small commits.

Thanks for those of you who try this release.