-
Notifications
You must be signed in to change notification settings - Fork 0
Aliases and Reuse
david-pettifor-nd edited this page Aug 10, 2026
·
1 revision
Use aliases when the same block of content must appear on more than one page and stay in sync. This site includes djangocms_alias for that purpose.
Back to Widgets.
Create an alias when you need:
- A shared callout, footer blurb, or promo that appears on many pages
- A navigation snippet or contact block you update once and reuse everywhere
- Any widget tree you do not want to copy-paste and keep manually aligned
Do not use an alias for one-off page content. Edit that page’s placeholders directly.
- Build the content once as an alias (a reusable content block managed through the alias UI in the CMS).
- On each page that should show it, add an Alias plugin and point it at that shared block.
- When you edit the alias content, every page that references it shows the update after you save.
Exact menu labels depend on your CMS version and permissions. If you do not see Alias options, ask an admin — see Permissions.
- Prefer NDT widgets inside aliases so shared blocks match the rest of the site (see Widgets).
- Keep aliases focused: one job per alias (one promo, one contact strip), not a whole page layout.
- Name aliases clearly so editors can find them later (for example “Global contact strip”, not “Alias 3”).
- Remember: saves are live. Changing a widely used alias updates every page that references it immediately.
- Widgets — widget catalogs
- Getting-Started — adding widgets to a page
- Permissions — who can edit shared content