| Summary: | Give ability to add context to custom pages in the staff interface | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Jason Robb <jrobb> |
| Component: | Tools | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | andrew, blawlor, Chip.Halvorsen, chris.rowlands6, dcook, jheltibridle, sally.healey |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34863 | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Jason Robb
2023-11-14 15:25:20 UTC
I agree with Jason. Additionally, having Pages categorized under tools causes the Tools navbar to display on all of the Pages I create, which I would prefer to not see. Sounds like a pretty cool idea to me. At some point, I plan to start restricting the type of content that can be added using the Pages tool, so I'm pretty curious to hear about how people are using it... but that's out of scope for this bug. When the time comes, I'll add a question to Mattermost I think... Could it make sense to be able to assign the module to the pages depending on how they are used or would this be overkill? (In reply to Katrin Fischer from comment #4) > Could it make sense to be able to assign the module to the pages depending > on how they are used or would this be overkill? This makes sense to me, yes. The user could pick from a list of existing modules when creating the page. |