Multilingual trademark platform
PocketIP
Structured content for trademark portfolio management
PocketIP helps businesses manage their trademark portfolios. The site had to present structured legal information clearly, in several languages, and stay easy to maintain for a team with no technical background.
About the project
Trademark information is structured by nature — categories, jurisdictions, statuses, classes. Modelled as ordinary WordPress pages it becomes unmanageable within months; modelled properly it stays queryable, filterable and consistent as the catalogue grows.
I built the site around custom post types and taxonomies that mirror how trademark data is actually organised, with ACF Pro Flexible Content on top so the team can assemble pages from predefined sections, and Polylang handling the multilingual layer without duplicating the content model.
My role
WordPress Developer
I designed the content model and built the site: custom post types and taxonomies for structured trademark information, ACF Pro Flexible Content for page assembly, and Polylang for the multilingual layer.
What I did
-
Content modelling
Custom post types and taxonomies that mirror how trademark portfolios are actually structured.
-
Flexible page building
ACF Pro Flexible Content so pages are assembled from predefined, on-brand sections.
-
Multilingual layer
Polylang localization across the whole content model, not just the interface.
-
Editor experience
An admin that non-technical staff can use without a manual or a developer.
-
Custom theme
Bespoke theme built to present dense legal information clearly.
-
Scalable structure
A data model that stays queryable and filterable as the catalogue grows.
Technical challenges & solutions
-
Structured legal data in an unstructured CMS
Out of the box, WordPress wants to treat everything as a page or a post. Trademark records have categories, jurisdictions and statuses that need to be filtered and queried.
Modelled the domain properly with custom post types and taxonomies, so the structure lives in the data rather than in how someone happened to write the page.
-
Several languages without duplicating the model
A multilingual site often ends up as two or three parallel sites that slowly diverge.
Used Polylang across the content model itself, so translations attach to the same structured records instead of becoming separate copies.
-
Non-technical editors, complex content
The team needed to publish and restructure pages without breaking layout or brand.
ACF Pro Flexible Content gives them a set of predefined sections to combine freely, with the layout rules fixed in the theme.
Impact & outcomes
-
Content that stays organised
Structured CPTs and taxonomies keep the catalogue consistent as it grows.
-
Genuinely multilingual
Polylang applied to the content model, not bolted on afterwards.
-
Self-service publishing
Editors build and restructure pages without a developer.
-
Maintainable foundation
A clean data model that the next developer can extend rather than rewrite.