iWorky
extending a marketplace without breaking its editor
I focus on the risk of extending a marketplace theme: custom behaviour is useful only if its editor and other modules still work.
- Field
- Freelance marketplace
- Built with
- WordPress / Gutenberg
- Project year
- 2022
The challenge
iWorky used an existing marketplace theme that was not designed for arbitrary third-party changes. The client wanted custom behaviour and presentation while retaining visual content editing. The central challenge was compatibility across interconnected theme modules.
The approach
The supplied theme and Gutenberg blocks were adapted from the client’s sketches. This was a focused extension and support engagement, rather than a ground-up design or a claim to have authored the entire marketplace engine.
The project, in detail
The images show the interface and its context. Captions distinguish project archives from current-site views.
Changes that respect the publishing workflow
Customised blocks retain their visual editing controls, so the client can continue maintaining content after the implementation. The work fits new requirements into the existing system rather than replacing its editorial model.
Coordination with the original theme developers
Discovered issues were raised with the theme’s authors; additions and compatibility were discussed before rollout. Each change required broader regression checks because a modification in one module could affect another. That careful integration work is the core of this case.
The outcome
Customised marketplace theme and Gutenberg blocks
Visual editing preserved during functional changes
Details of iWorky
What kind of product work was this?
The marketplace theme gained custom behaviour while its editor and existing modules remained usable.
