Bot releases are visible (Hide)
exclude
property on collections. This allows to exclude specific files in a collection from being listed.icon
property in content entries.Published by hunvreus 7 months ago
Published by hunvreus 7 months ago
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.
Published by hunvreus 7 months ago
Published by hunvreus 7 months ago
Published by hunvreus 7 months ago
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).
Menu | Modal |
---|---|
Published by hunvreus 7 months ago
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.
style
or class
attribute. It also now retain <img>
elements with a width
or height
attribute.Published by hunvreus 8 months ago
Rework the collection view logic to properly escape HTML and prepare for modular custom field view logic.
Published by hunvreus 8 months ago
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
).
Published by hunvreus 8 months ago
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: [email protected].
.pages.yml
file and still use the CMS.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.Lots of bug fixes through the app:
media.output: ""
).Published by hunvreus 8 months ago
Fixing the user dropdown for short usernames or missing profile names.
Published by hunvreus 8 months ago
Addressing errors when media is not defined and a collection/file uses an image field.
Published by hunvreus 8 months ago
Fix some additional edge cases with empty JSON/YAML/TOML files and empty frontmatters.
Published by hunvreus 8 months ago
Published by hunvreus 8 months ago
Preventing corrupted image paths to trip on githubImg service.
Published by hunvreus 8 months ago
null
values.Published by hunvreus 8 months ago
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.
Published by hunvreus 8 months ago
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
.
.page.yml
file with warnings and errors to help you write something that doesn't blow up your setup._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
).Lots of improvements, but these stand out:
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.
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.
Published by hunvreus 8 months ago
This is the first official release of Pages CMS, an Open Source CMS built for static websites (Jekyll, Next.js, VuePress, Hugo, etc). It allows you to edit your website's content directly on GitHub via a user-friendly interface.
It is a continuation of a previous project (Jekyll+) with more features and broader use cases.
Still rough around the edges but fully functional with all important features:
To get started, go check the documentation at pagescms.org/docs or have a look at the README file.
You can either use the online version at app.pagescms.org or deploy your own version.
The README file includes a list of TODOs, but for 1.0.0 I am focusing on adding schema validation for .pages.yml
, the configuration wizard and project boilerplates for Next.js, Hugo, 11ty and Jekyll.
To report bugs or suggest improvements, go to the issue queue: github.com/pages-cms/pages-cms/issues