-
-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[5.x] Add new 'Settings' CP Nav section #9857
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a really great solution. I love it. |
jesseleite
added a commit
to statamic/docs
that referenced
this pull request
Apr 10, 2024
jesseleite
changed the title
[5.x] Add new
[5.x] Add new 'Settings' CP Nav section
Apr 11, 2024
Settings
CP Nav section…s-sidebar-section
duncanmcclean
added a commit
to statamic/docs
that referenced
this pull request
May 9, 2024
* add upgrade guide * explain that seeds are removed from shuffle modifier * [5.x] Document Addon Testing (#1258) * Addon Testing docs * Fix tyyo * [5.x] Remove docs for the Antlers Regex Parser (#1242) * Remove docs page for legacy Antlers * Remove links to legacy docs & mention guarded settings * fill in min php/laravel versions, and recommend upgrading * please * nevermind i figured it out * slugs * explain how to use temporary file uploads * Tweak note about supported Laravel versions * [5.x] Update string based validation rules (#1298) * link to upgrade guides so we dont have maintain two identical lists * document rule changes * explain fake sql queries and how to disable them * [5.x] Document new `findOrFail` methods on repositories (#1305) * Tweak wording on "Entry Repository" page * Document `findOrFail` on other repositories * Terms repository: Add note about `findOrFail` now we have a `find` example * bard * helpers are removed * SVG tag: The default value for the `sanitize` parameter is now `true` * [5.x] Multi-site documentation overhaul (#1307) * sites * Tweak sites. * Note on text `direction`. * [5.x] Upgrade Guide: Add note about pagination view changes (#1312) Co-authored-by: Jason Varga <jason@pixelfear.com> * more upgrade guiding * not anymore * escaping params * Move `content/sites.yaml` to `resources/settings/sites.yaml`. See statamic/cms#9857 * Move `resources/settings/sites.yaml` to `resources/sites.yaml`. * Update screenshot, since we moved `Sites` into `Settings` section. * Update `AddonTestCase` import in upgrade guide * Add "Testing in Addons" page to Extending docs (#1323) * Add note to upgrade guide about the new `please` file This will be mostly useful for those upgrading to Laravel 11 using Shift. * Add note to the upgrade guide about the Laravel Shift discount * user role stuff * use async in example * Add sentence about running Statamic without an internet connection * you can disable svg tag sanitization * explain default value behavior change --------- Co-authored-by: Duncan McClean <duncan@duncanmcclean.com> Co-authored-by: Jesse Leite <jesseleite@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In response to #9632 (comment) and after some discussion, we've decided to:
Site
/Sites
out ofContent
and into to a newSettings
section in CP navcontent/sites.yaml
toresources/sites.yaml
Preferences
andCP Nav Preferences
from top bar intoSettings
in sidebar as wellCP Nav Preferences
into a stack editor later, post-v5