[EPIC] All standard Back Office extension usecases
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 136
- Forks
- 555
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 4
Description
PrestaShop is a CMS and its richness comes from how developers use it as a foundation to build e-commerce applications. To do so, PrestaShop provides many extension capabilities: modules, themes, hooks, template overrides, raw class overrides, services decoration ...
This issue aims to gather all the standard extension usecases so we can verify that, for each of them
- a suitable solution is available (if not: we can plan to implement something)
- a documentation and/or an example is available
Examples
Add fields inside BO forms
As a Module Developer
As my customer (the shop administrator) wants PrestaShop workflow to ackowledge
some extra properties on products / customers / ...
I want to be able to add new fields inside any forms of the Back Office
and choose where in the BO page they are displayed
and when shop administrator hits the "save" button, receive the submitted data
so I can validate it (= verify it, and if not valid refuse the form submission and display an error message)
and store it
Add BO pages reachable through the navigation menu
As a Module Developer
As my customer (the shop administrator) wants to add PrestaShop BO pages
I want to be able to add links inside the navigation menu in the Back Office
Remove BO pages reachable through the navigation menu
As a Module Developer
As my customer (the shop administrator) wants to remove PrestaShop BO pages
because they are useless for him
I want to be able to remove/hide links inside the navigation menu in the Back Office
Customize navigation menu wording
As a Module Developer
As my customer (the shop administrator) wants to improve the wording of the navigation menu
I want to be able to customize the wordings used for the navigation menu, depending on the language
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the listed Back Office extension use cases, including adding fields, navigation links, and menu wording. Done means cataloging the standard use cases and identifying a suitable solution plus documentation or an example for each.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100