Welcome to the Mapbender Development Documentation! This documentation is intended for Mapbender developers and covers topics that are not necessary for administrators or users of Mapbender installations. It provides in-depth knowledge on how to contribute to and modify Mapbender's open source code. Before you begin, make sure to review our Conventions and familiarize yourself with the basics of collaborative work. If you want to dive deeper into a specific topic, be sure to read the Contributing Guide.
- API
- Commands
- Components
- Contributing Guide
- Controllers
- Conventions
- Directory structure
- Elements
- FAQs
- Git Archive
- Project Setup Guide
- Request/Response Workflow
- Security
- Styleguides
- Testing
- Translation
- Upgrading Guide
To contribute to Mapbender, it is essential to have a solid understanding of object-oriented PHP and Symfony, the framework we use.
You can find more information about Symfony by reading The Book. We often rely on jQuery, especially the jQuery UI Widget factory, in our JavaScript code for legacy reasons.
The installation procedure from Git is described in the Mapbender User Documentation.
Please refer to the respective sections in the Contributing Guide to understand what modules and what bundles are, and how the latter can be created.
Symfony follows the template approach that we use in Mapbender. This uses a templating engine to generate HTML, CSS or other content. A template is a text file that can generate any text based format like HTML or XML. It is used to express presentational logic. You can use them to create a layout. You can create a base layout and then overwrite or append any of your layout blocks with individual templates. Read more about Templates in Mapbender in the Contributing Guide and find a good introduction about Twig in the Symfony Template documentation.
For further assistance, consult one of the sources to enhance your understanding of Mapbender.