During the discussion of #2349559: [meta] Discuss the organization of subfolders in Classy, many people expressed confusion over the file names used for core templates. In some cases it is hard to understand what a template does from its name.

Proposed resolution

All core module templates should be reviewed and renamed, if necessary, so their purpose can be more easily inferred from their file name.

Remaining tasks

  1. Agree on file names.
  2. Rename all the files.


akalata’s picture

I reviewed the referenced issue at #2349559: [meta] Discuss the organization of subfolders in Classy, but the only template-naming confusion I saw was block-list.html.twig. Changing template names leads to changing preprocess/process functions (where/if they exist) and might be too much work for too little reward, IMO.

joelpittet’s picture

Version: 8.0.x-dev » 9.x-dev
Status: Active » Postponed

As no work was done here this will be moved to 9.x. If there is an actual proposal of changes it may be moved to 8.1.x.

catch’s picture

Status: Postponed » Closed (duplicate)

Marking as duplicate of #2702061: Unify & simplify render & theme system: component-based rendering (enables pattern library, style guides, interface previews, client-side re-rendering). That's a wide-ranging issue, but clearly identified components/templates is part of it.