Operating rules behind the interface

Data structures, search, accounts, packages and moderation in one platform. A WordPress, MyListing and WooCommerce implementation with extensions tailored to OtoBroń’s rules.

Publishing, search and author tools

For OtoBroń, we implemented a listings platform combining advertisements, business and venue profiles, training and events. Our work covered both the interface and the backend: listing structures, search, user accounts, publishing packages, moderation and system communication.

The most important part of the project lay in the relationships between these elements. Data entered by an author had to appear in the right places on the listing page, feed the search filters and follow the publishing rules. Every screen was therefore part of a larger process.

Visitors, authors and the operator

The platform had to accommodate three perspectives: visitors looking for specific information, authors managing their publications and the operator responsible for reviewing them. Simplifying one path could not overlook the consequences for the others.

Different listing types also required different logic. For a venue, location, facilities and opening hours mattered. For an event, the date and its connection to a place were important. A universal form would obscure these differences, while putting the information in the description alone would prevent its use in search.

Similar dependencies applied to the backend. Allowing a listing to be edited meant defining rules for renewed moderation. A publishing package required connecting user entitlements with an order and a validity period. Seemingly small decisions affected the entire platform.

How a listing works in the portal

Entering the data
The author uses fields suited to the publication type. Location, opening hours and event dates have their own place in the listing structure.

Controlling publication
The listing is subject to moderation rules and the relevant package. Editing a published listing sends it back for review, while status changes are linked to system communications.

Presentation and search
Structured data feeds the listing views and helps visitors find it. Visitors can search using criteria appropriate to each publication type.

The engine and custom extensions

We based the implementation on WordPress, MyListing and WooCommerce, combining configuration of existing mechanisms with our own extensions. The directory engine handled the basic listing functionality; our role was to adapt its structures and rules to OtoBroń and add functionality where custom logic was needed.

Listing data powers the search

For each publication type, we configured separate field sets, result cards, detail views and search forms. Location, opening hours and event dates were stored as structured data rather than just parts of a description. The same information could therefore serve both to present a listing and to find it by location, distance or date. We also added conditional visibility of selected form fields based on category.

We represented connections between listings in the data model. An event could reference a specific venue, and a training course could reference a related venue or business profile. For these relationships, we configured selection to be limited to listings owned by the same author. The connection between content therefore also accounted for who managed it.

Listing changes and notifications

The publication lifecycle was a separate area of work. In line with the client’s requirement, editing a published listing sent it back for moderation. The dashboard distinguished active publications, those awaiting approval, those awaiting payment and expired ones. We connected these states with the system’s communication settings: we enabled 12 notification types covering listing approval, messages, reports and approaching expiry, among other events. We also adapted the messages for the Polish-language website.

Packages linked to listings

We based publishing packages on integration with WooCommerce. We assigned packages to the appropriate listing types, including variants covering several types of publication. We adapted the standard shop journey to the portal’s services by removing transitions to ordinary product pages. We also extended the order data flow with the Polish tax identification number (NIP) — from the form field and storage against the order to the administrator’s view and emails.

From search to publication

For a listings platform, we select indicators showing whether visitors find the information they need and whether authors can use the publishing service. The portal’s package revenue should be distinguished from transactions between listing users.

### Search effectiveness

Transitions from results to venue profiles, training and events, together with the proportion of searches returning no results, help assess the usefulness of data and filters. Analysis by listing type shows where visitors need a better path.

### Completing a submission

The proportion of started forms that result in a listing submitted for moderation shows whether authors complete the process. Time from submission to the operator’s decision distinguishes form difficulty from waiting for a review.

### Package purchase and renewal

Paid package orders and renewals measure use of the portal’s paid service. Comparing them with started orders and expiring publications helps identify stages that need improvement.

Media and supporting content

Our custom code also covered media and supporting content. We added a mechanism that applies a watermark to JPEG and PNG images uploaded by users other than the administrator. We created a dedicated OtoBroń plugin with Elementor modules, including an editable FAQ with answer search, as well as an automatic table of contents for articles. The extensions therefore addressed daily publishing and content maintenance as well as the website’s appearance.

A portal with publishing tools

We design websites whose interfaces follow their data model and operating rules. Explore how we can connect a directory, user accounts and paid services in your project.

• Explore web and e-commerce services

A shared backend for different listings

OtoBroń received a platform where different publication types share a common backend while retaining their own forms, presentation and search criteria. The listing author’s experience was connected with moderation rules, packages and operator communication.

The value of the project lay in translating the portal concept into specific operating rules: what data is collected, where it is used, who can manage it and what happens when a publication’s status changes. These dependencies, supplemented by custom extensions, formed the core technical work behind the OtoBroń interface.

Explore the implemented website

Discover the portal’s layout and how it presents different listing types.

• Visit OtoBroń