Context
Turizam Info is a long-running professional print magazine serving stakeholders across the tourism sector.
The website was never intended to be the primary channel. Over time, however, it became a necessary operational layer. The technical base was outdated, mobile use was poor, and routine changes were increasingly fragile.
In parallel, subscriptions relied heavily on manual handling and off-system communication. As the subscriber base grew, that approach introduced operational friction that did not scale.
The requirement was not a marketing site. It was reliable infrastructure for content, subscriptions, and year-round operational workflows.
The actual problem
The issue was not visual design or an “old website”.
The problem was the absence of a system capable of supporting the magazine’s business logic over time.
Concretely:
- Content and issue archives were not structured for real use.
- Subscription renewals depended on manual work and ad-hoc communication.
- There was no systematic way to manage existing subscribers ahead of expiry.
- Additional initiatives such as fairs and events had no stable technical foundation and were handled case by case.
In practice, the site behaved as a presentation layer rather than an operational tool.
Constraints and trade-offs
The solution had to remain within WordPress because the editorial team already depended on WordPress-based workflows.
Core processes could not depend on external SaaS products. Subscription handling and CRM logic needed to reflect internal operations rather than forcing the organisation to adapt to third-party models.
Generic membership, event, or CRM plugins were deliberately excluded. They would have accelerated delivery, but at the cost of rigid assumptions and reduced long-term viability.
This required more initial engineering effort, but avoided structural compromises that typically surface later.
Key architectural decisions
A fully custom WordPress theme was implemented rather than adapting an off-the-shelf solution. Content structure and navigation were designed around how editors and readers actually work with the publication.
The issue archive was implemented through a controlled iframe-based approach. This avoided migration or duplication of existing digital assets while maintaining a consistent user experience.
Subscription renewals were built as a dedicated mechanism. The system generates personalised renewal pages and automates reminder workflows, replacing manual communication without introducing generic membership abstractions.
For fair and event-related work, a separate custom CRM was developed as a WordPress plugin. Responsibilities and roles were separated explicitly.
Participant authentication uses passwordless magic links to reduce access friction and support overhead.
Administrative interfaces, operational workflows, and participant-facing views were intentionally isolated to minimise errors and keep the system extensible.
“All-in-one” tools and visually attractive but operationally irrelevant features were excluded by design.
Resulting system and long-term value
The outcome was not a redesign. It was a cohesive platform that supports content publishing, subscriptions, and operational projects within a single ecosystem.
Subscribers renew through personalised pages without manual intervention. The editorial team has clear visibility into subscription status and interaction history.
The event CRM supports participant management, networking, access control, badge issuance, search, and email communication without reliance on third-party tools or additional licensing.
The system runs continuously throughout the year and can evolve without changes to its core architecture.
The value is not in feature volume. It is in providing a technical foundation aligned with how Turizam Info operates today and how future initiatives are likely to be structured.
If this evidence matches what you need, start with the qualification criteria.