Modules extend the capabilities of thirty bees. They help to make shops unique and to meet demands of each market segment. They provide payment methods as well as shop management helpers and additions to the customer visible shop.

Concepts used by thirty bees still largely match those introduced by PrestaShop over the years. Most PS 1.5 and PS 1.6 modules work just fine with thirty bees. Developers can keep most of the workflows they're accustomed to. If there are changes, they make modules more reliable and easier to handle.

These pages were written with the documentation concept of Firefox Add-Ons in mind. This concept was found to give quick first results as well a good path towards writing high quality and reliable extensions.

• What are modules? - Where do they live, what can they do?
• My first module - A trivial module with a configuration page.
• My second module - A more advanced module with back office menu entry.
• Anatomy of a Module
• Example modules

• Module main class constructor
• Module configuration page
• Back Office Menu Entries
• Back Office Display Engine
• Front office display hooks
• Configuration database table
• Internationalization
• Security best practices
• User experience best practices

The above chapters show that modules should engage in back office by adding a menu entry (Tab) and hooking up a controller to them. Accordingly, back office display gets described in

• Writing Controllers

(one page for each way to display something in front office)

• Emit a Warning in the List of Modules
• Do Web Requests With Guzzle (Guzzle is the preferred tool for such requests)