-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Documentation improvements: Audit Trail/Redis/SEO/Deployment docs, demo videos, YouTube embed privacy (Lombiq Technologies: OCORE-78) #11154
Conversation
Piedone
commented
Feb 10, 2022
•
edited
Loading
edited
- Typos and formatting fixes
- Audit Trail module docs, fixes Document Audit Trail #10097
- Redis module docs
- SEO module docs
- Adding missing demo videos
- Videos are embedded with the YouTube privacy-enhanced mode
- Improving docs contribution docs
@@ -375,7 +374,7 @@ When rendering the scripts the resource manager will order the output based on t | |||
3. `bar` | |||
|
|||
!!! note | |||
You do not have to define a name for your script or style unless you want to reference it as a dependency, or declare it as `Inline`. | |||
You do not have to define a name for your script or style unless you want to reference it as a dependency, or declare it as `Inline`. Hence why the above inline examples all include a name. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See: #11153
|
||
You can attach the `AuditTrailPart` content part to your content type. This will allow content editors to enter a comment to be saved into the Audit Trail event when saving a content item. This will then be visible in the Audit Trail event list. | ||
|
||
## Recording Custom Events |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've removed the long tutorial that was previously added to the file under #10097. It would need extensive update to reflect the current API and while it would be nice to have such a tutorial, it's also a pain to maintain, and in the light of living examples being available in the source code I don't see the real point.