Managed platforms
RealMosaic and RealOnline are SD’s established CMS platforms. They cover different kinds of work, but both are designed to reduce unnecessary moving parts and keep responsibility clear.
RealMosaic
RealMosaic is the general-purpose platform for business websites, publishing and managed multi-site work. It gives editors the control they need while keeping the system deliberately managed.
It suits organisations that want a flexible site and direct support without being responsible for assembling and maintaining the underlying parts themselves.
Is it the right fit?
RealOnline
RealOnline handles specialist property and business-listing requirements, including structured inventory, search, feeds and portal distribution across Australia and New Zealand.
It is used where listings arrive from other systems, need specialised display and search, or need to be sent onwards through established data flows.
See AccomProperties
Platform selection
The visible website matters. So do the editors, data sources, integrations and the person expected to look after it in three years.
Best suited to
RealMosaic: business sites, publishers and managed site groups
RealOnline: property, business-for-sale and specialist listings
Content model
Pages, articles, people, services and flexible structured content
Listings, agents, offices, categories and specialist search fields
Integration work
APIs and business-system connections as required
Inbound feeds, portal pushing and listing-system connections
Ongoing model
Managed hosting, support and iterative improvement
Managed platform operation, feeds and ongoing development
Common questions
Yes. API and feed work is common, but the sensible approach depends on the source system, data quality and who owns each side of the connection.
No. The platform is the managed foundation; the public interface is designed around the project and can evolve over time.
Editors can manage day-to-day content. SD manages the platform, hosting and technical changes as part of the ongoing relationship.
Then a custom application, an integration with an existing system or another foundation may be more appropriate. The requirement comes first.
Start with the fit
The content, data sources, number of sites, editorial roles and integration requirements will usually make the right direction fairly clear.
Send the requirements