Divi
Four modules for the Divi Builder
Add the job board, the search, a role’s content or its application form to any Divi layout. They are Divi modules, taking Divi’s own settings, and they render through the same code as the blocks, the Elementor widgets and the Beaver Builder modules.
Nothing is registered unless Divi is actually loaded.
What you get
The four modules
| Job board | The listing of open roles |
|---|---|
| Job search | Keyword and location search over the board |
| Job details | One role’s content |
| Job application | The application form for one role |
The same board, wherever it is built
Divi describes them its way; the markup comes from one place
Divi hands a module’s settings over in its own shape, as Beaver Builder does in a different one. The adapter translates that and nothing more: the markup itself comes from the seam every other layout renders through. So a Divi page shows the same board as a block page, and a change made in the plugin reaches both at once rather than needing to be made twice.
- Markup from the same seam as blocks, widgets and modules
- No separate template file to drift
- Settings translated, never reinterpreted
- The shared templates escape everything they print
A privately owned main contractor in Leeds is hiring a senior QS to take commercial ownership of a £40m mixed-use scheme through to practical completion, reporting to the commercial director.
- Five years’ post-graduate experience with a main contractor
- Valuations above £5m run without supervision
A designer gets two switches and a job number
The same settings surface as every other builder. No field picker, no query builder, no template setting, because an element that could be pointed at arbitrary data is an element that can publish a field you chose to keep private. The job number is read as untrusted and must resolve to a role the access layer will show.