Skip to content

docs: Backport template explanation #7931

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

Merged
merged 6 commits into from
May 30, 2024
Merged

docs: Backport template explanation #7931

merged 6 commits into from
May 30, 2024

Conversation

fsbraun
Copy link
Member

@fsbraun fsbraun commented May 29, 2024

Description

this pr backports #7929

Related resources

Checklist

  • I have opened this pull request against develop-4
  • I have added or modified the tests when changing logic
  • I have followed the conventional commits guidelines to add meaningful information into the changelog
  • I have read the contribution guidelines and I have joined the channel #pr-reviews on our Discord Server to find a “pr review buddy” who is going to review my pull request.

fsbraun and others added 4 commits May 22, 2024 10:05
* fix #7859: allow special characters in page title

* Update test_templatetags.py

* Fix ruff issues in test_templatetags.py

* One more time: fix ruff issues in test_templatetags.py

---------

Co-authored-by: Fabian Braun <fsbraun@gmx.de>
)

* docs: Improve docs on how to use templates

* Fix typos, add `assertIn` to word list

* Update setup.cfg

* Remove "while"

* Clarify use of CSS and JS libraries

* Fix references.

* Update djangocms-alias section

* Update 04-templates.rst: Add missing space
@fsbraun fsbraun changed the title doc: Backport template explanation docs: Backport template explanation May 29, 2024
@fsbraun fsbraun merged commit 9a3a7b5 into release/3.11.x May 30, 2024
@fsbraun fsbraun deleted the docs/templates branch July 26, 2024 21:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants