CMS (Content Management System)
Dev URL: https://cmsportal-dev.tokenise.io
Technology
The CMS for Tokenise-Broker is built using Strapi.
Using Strapi gives us:
- A flexible, API-first headless CMS with a clear content model
- A user-friendly admin panel, so non-developers can manage content
- Ready-made REST/GraphQL APIs for fast integration with front-ends (web, mobile, etc.)
This allows us to manage content independently of the core broker logic and deployments.
Content Separation & Responsibilities
We designed the CMS as a separate service so that all content-related changes happen outside the core system, including:
- Texts and labels in the Investor Website
- Pages, sections, and marketing content
- Logos, images, and media
- Documents and content related to each token / asset
This has several advantages:
- Content changes do not require backend/core deployments
- Business, marketing, and operations teams can update content safely
- The risk of breaking core trading or business logic due to content changes is minimized
Integration with the Investor Website
The Investor Website is connected to the CMS and:
- Fetches texts, content blocks, and media from Strapi
- Uses CMS-managed data to render pages and components
- Can dynamically adapt to content changes without code changes
In practice, the Investor Website treats the CMS as its content source, and the broker core remains focused on business logic and data, not presentation content.
Multi-Channel Content (Web, Mobile, Tokens)
Because content is managed centrally in the CMS, we can:
- Provide separate content for different channels (e.g. Web, Android, iOS)
- Define token-specific content (descriptions, documents, images) per asset
- Serve content to any future app or service via the same CMS APIs
This means new apps (like a separate mobile app) can reuse the same content infrastructure with minimal changes to the core broker system.
Scalability & Traffic Handling
By isolating content into a dedicated CMS service:
- High traffic on content pages mainly impacts the CMS infrastructure
- We can scale or upgrade only the CMS service (caching, horizontal scaling, CDNs, etc.)
- The core broker backend remains focused on business operations and is less affected by content spikes
In short, CMS + Strapi give us a clean separation of content and core logic, easier maintenance, and a scalable way to support multiple front-ends and token-specific content.
More Information
For more details about Strapi, visit the official website: