Over the last couple of weeks we’ve continued working on improving silverstripe/linkfield so that we can be comfortable officially supporting it.
We finished an overhaul of the contributing documentation which will hopefully make it a lot clearer what the process is for making contributions to the supported modules.
We’ve also been adding automated linting to our documentation, which should help to reduce issues rendering the markdown as well as provide early feedback to contributors about potential structure or stylistic issues with their pull request changes.
Item that has been added implicitly to ChangeSet, cannot be removed - patched in
- Add MariaDB to our CI matrix
- Review our OSS contribution doc
SiteTree::$hide_pagetypesconfiguration property (and deprecate
- Add option to select/deselect all files
As Max said at Stripecon, the community contributions are like having a 5th member of the CMS Squad. We greatly appreciate all of your work in improving Silverstripe CMS for everyone. Here’s some of the community contributions which got merged in the last couple of weeks.
- Add support for braille format files by Ed Wilde
- Use field editorconfig when sanitising content by Bernard Hamlin
- NEW: Stages differ recursive by Mojmir Fendek (which is leading on to a nice UX change in the future)
We’re in the process of decommissioning addons.silverstripe.org. There may be similar functionality implemented as part of the silverstripe.org rebuild in the next 6 months or so, but in the meantime this website had many many problems and we simply haven’t had time to resolve them. There’s more discussion about this decision in the GitHub issue itself. That subdomain will redirect to https://www.silverstripe.org/software/addons/ which provides a pre-filtered link for searching Silverstripe CMS modules in Packagist directly.
The work to add linting to our documentation continues, as does our focus on the linkfield module.
We’re also moving forward with our plans to add new community maintainer roles for the supported modules. You can track our progress in this GitHub issue.