[DOCU-242] Add template extension use case Created: 23/Dec/11  Updated: 15/Aug/16  Resolved: 12/Jan/15

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Suzanne Deprez Assignee: Ruth Stocks
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Add a use case that describes recommendation for adding templates and/or changing/extending templates by placing them in a project module.



 Comments   
Comment by Antti Hietala [ 12/Jan/12 ]

Suzanne, please add detail. Best practice for deploying a site is to package the whole site into modules: one module for content, another for theme, third for templates and so on. Is this ticket a specific case dealing with templates only? Where does the request come from? If this is about the location where templates should go in a module, improve the existing Modules article.

Comment by Suzanne Deprez [ 25/Feb/12 ]

This is intended to strictly address templates.

Customizing/adding/extending/changing templates and where/how to include them is a frequent subject in the user list. Many times the user doesn't realize what they need to do with templates (or that they need to do something with templates) for a problem they have. Use cases should help minimize the struggles by helping them to associate how to solve their problem with templates. A list of some postings in the user list that request help for adding/extending/changing templates are:

Generated at Mon Feb 12 01:07:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.