Ingo Schommer
Ingo Schommer
# Overview The CMS is largely regarded as "self explanatory", but there's certain user actions and features which do require explanation. For example, how users and groups inherit permissions. Currently...
# Overview Follow up work from [global archive view](https://github.com/silverstripe/silverstripe-framework/issues/6202). # Acceptance Criteria * As an author, I can make a mental connection between the act of archiving a record and...
# Overview Authors often work in specific areas of a larger website. For pages, they can just bookmark the edit link to their specific section (or a CMS pages filter)....
# Overview There's been a couple of high profile compromises of downstream dependencies in the NodeJS ecosystem. We should build security checks for this into our CI process, and fail...
# Acceptance Criteria * I have the option to undo any revertable actions in the same context as taking them * The option is only presented directly after taking the...
Travis merges PRs into the base branch. Contributors are expected to run `yarn build` when changing frontend assets. Our Travis builds run a `yarn build`, then a `git diff`. This...
# Overview Follow up work from [creating the pattern library](https://github.com/silverstripe/silverstripe-admin/issues/206). At the moment it only contains a small subset of components. # Acceptance Criteria * All React components in admin/client/src/components...
# Overview We generate an "archive warning message" proactively on each CMS page edit form load. It has to review all descendants to come up with a specific message, e.g....
# Overview We're transitioning out of the PoC phase with React customisations in the CMS, so need to ensure the system is actually ready to be used by third party...
This module has been a stop-gap solution for SS 3.x while we improved the core asset (and document) management capabilities in SS 4.x. We now have a lot more capabilities...