Classic UI > Overrides

Open
#1,467 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Start by reading the Classic UI layers, views, and viewlets pages linked in the issue, especially their existing override sections. Create the proposed Overrides chapter with coverage for component classes, layer usage, z3c.jbot templates, REST endpoint overrides, and examples, then update those pages to reference it.

Written by the indexing model from the issue text.

Description

99 tag: classic-ui 99 tag: Plone 6.x
Plone Documentation versions affected
  • 5.x
  • 6.x
Description

The code / method for overrides in Views, Viewlets, Tiles are nearly the same, as well as using overrides is common. This chapter can be mentioned in layers, views and viewlets.

I would suggest doing for them a own chapter in classic-ui.
Structure can look like this:

  • Overview
  • Override a View, Viewlet , Tile class. ( with the zcml attributes, explanation of layer usage)
  • How to override a template with z3c.jbot
  • Rest-End-point overrides ( as @jensens mentioned)
  • Examples
Dominant language
Makefile
Stars
106
Forks
190
Avg merge
3d 2h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from plone/documentation

All issues in plone/documentation

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.