Forms with logic
Appropriate fields, meaningful checks and a clear next step after each request.
Plugin development · 01 / 06
A form, a customer area, an own process: I supplement your CMS with the function that you lack in everyday life.
Services and project questions in detail
Appropriate fields, meaningful checks and a clear next step after each request.
Maintain offers, locations or specialist content as it suits your company.
Protected content and coordinated processes for the people who use your website.
A possible example
A website collects project requests. An individual extension queries the appropriate information and prepares it for your team or a connected system.
I check your CMS, the existing extensions and the desired process. This results in whether an own plugin, an integration or an adjustment in the existing system fits. WordPress is a possible application.
Services in detail
An own CMS plugin is worthwhile if an important process cannot be mapped appropriately with existing extensions. For WordPress or another expandable CMS, we consider editorial, visitor and downstream editing together. Thus, an additional function becomes an understandable way of working.
An offer, a location or a specialist article does not always need the same fields. Own content modules can structure the care and display recurring information uniformly. Together we determine mandatory information, preview and publication steps so that the editorial team can process content without unnecessary detours.
A multi-level form can only display the questions that fit the respective selection. Then it is determined how the application is assigned and processed. For a transfer to other programs, we check their interfaces and the actually required data.
Technical implementation
The extension must work with the existing CMS, theme and editorial processes.
Own fields, forms or protected areas are planned via suitable extension points. We check which data the CMS already manages and which new structure is needed. Direct interventions in the system core should be avoided.
Editorial staff and visitors need different accesses. Form data is checked on the server; outputs and file assumptions need appropriate rules. Erroneous inputs and duplicate form submissions are also among the test cases.
CMS, theme and plugin versions can affect each other. The extension is checked with the relevant combinations. During installation, update or deactivation, the handling of created data must be fixed.
Helpful are the CMS and theme version, a list of plugins involved, sample content and the required roles in the editorial team.
Which of these questions is crucial for your project? Briefly describe your process and the existing systems.
Discuss technical requirementsYes, the goal is a targeted addition to your existing website. What adjustments are necessary, I clarify on the basis of your CMS, themes and the already used extensions.
Web design shapes the appearance of your website. A CMS extension complements its functions. If you need both, design and process can be planned together.
We define specific test cases and check the extension in a suitable test environment. This also includes display, input and the interaction with existing functions.
If a specific rule, interface or data transfer is permanently missing. Before that, we check existing possibilities and their configuration. An individual extension should have a clearly named benefit and fit the maintenance of your website.
We capture CMS version, theme and related extensions. For relevant updates, suitable test procedures and responsibilities are discussed. Maintenance and subsequent adjustments are an explicitly tailored component.
This can be provided for. For this purpose, we plan fields, help texts and editing rights based on the content that is maintained regularly. An example content shows early on whether the mask is understandable for the editorial staff.
Tell me your CMS and the function you are missing.