Check out the preview release: new fields, caching, improved media management, and more #205
Replies: 4 comments
-
|
The demo repo is available there: https://github.com/pages-cms/demo Have a look at the config in particular: https://github.com/pages-cms/demo/blob/main/.pages.yml |
Beta Was this translation helpful? Give feedback.
-
|
Pushed some more performance improvements today, it should feel a lot snappier. I'll be pushing this release in production over the weekend. |
Beta Was this translation helpful? Give feedback.
-
|
It's in production: https://app.pagescms.org/ Do let me know if you run into any issues. It should overall be a lot faster, especially for large collections. |
Beta Was this translation helpful? Give feedback.
-
|
Documentation is also up to date: https://pagescms.org/docs/configuration/ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Check out the demo on Youtube: https://youtu.be/zWdy2T3VhkA
I've just finished setting up the preview build of Pages CMS at dev.pagescms.org. Moving forward, you'll be able to use that to try out new features before they're released to production.
Try out the upcoming version of Pages CMS (dev.pagescms.org)
It is packed with bug fixes, improvements and new features. The most important ones:
Multiple media configurations
You can now set up more than one media folders:
These can be referenced across media related configurations. Each can have their own options (e.g. categories, extensions, ...).
New file field
You can now upload whatever files you want. It supports a few options:
media: thenameof the media you want to use for that field. Defaults to the first media entry.path: the default path to upload or select files.multiple: if true, allows you to upload multiple files (and reorder them). You can also set it up to be an object withminandmaxattributes, similar to thelistattribute on all fields.categoriesandextensions: same as forimage, allows you to restrict the types of files you can upload or select.It also supports drag and drop upload.
I've updated the
rich-textandimagefields to support the same optionsSelect field
I've upgraded the select field to support
multipleentries:It also allows you to use any remote URL to fetch values:
An example of configuration to allow you to query the GitHub API:
Reference field
The reference field allows you to refer to another collection. You can set it up in a similar way to the autocomplete select:
UUID field
Allows you to get a UUID value in your content:
Caching
I've added caching on collections and media folders. It will still be fairly slow the first time you visit the collection or media page, but after that things should be pretty snappy. I will improve the caching strategy over time.
What's next?
I'm still working on rolling this out in production, but the next big things I'm working on are:
authorblock withname,photoandemailfields and reuse it in multiple content entries. Read more: Block type composition support #200 (comment)type: [ image, file, string ]), which the user can choose when editing. Read more: Block type composition support #200 (comment)./about/index.mdwould be displayed at the same level as./contact.mdand have other pages from./about/underneath it).If you're interested in helping out, come to the issue queue: https://github.com/pages-cms/pages-cms/issues/
Beta Was this translation helpful? Give feedback.
All reactions