Aurekai
Journal

Engineering · 2 min read

EngineeringNovember 7, 2026

A public page should open the real application

Why polished frontend compositions need the right account records and workflows behind them.

Nick GonzalesNovember 7, 2026 · 2 min read

We had a growing set of attractive pages and working tools. The awkward part was what happened between them. A homepage could advertise CRM, show a polished screenshot and then send a visitor into an older interface without the right account context.

We spent a great deal of time on this because the design problem and the application problem were becoming the same problem.

The page and the application should agree

A business owner wants to open relationships, find a customer and continue the work. They shouldn't need to know which repository built the page or which framework generated the next screen.

We explored shared page and surface compilers so mature interface patterns could appear across profiles, application directories, account workspaces and public sites. A pattern includes more than CSS: the right data, actions, navigation and account identity have to arrive together.

Independent sites use shared services

A retailer may have a custom domain and branded site. A publisher may have a personal subdomain. An organization may have different experiences for customers and staff. Matrix and web-address systems connect those places to the appropriate identity and application records.

The application gallery remains useful for exploring standalone tools. The larger Aurekai work is making them available from the account and public pages where people need them.

The finished experience should feel like one thoughtful product, even if several native systems serve it.

Public surfaceApplication continuationBroken handoff to avoid
ProfileAccount-scoped CRMUnrelated older CRM screen
OfferAppropriate catalogue or booking recordA static screenshot without a working action
PublicationReader, narration or collectionA separate article island
WorkspaceSaved state and permissionA new empty session after navigation

Start at the real account

Navigation should carry the destination and account context into the installed application.

Reuse one composition system

Shared page, component and token compilers should improve the same UI on profiles and in workspaces.

Verify the continuation

The user must be able to finish the action; a beautiful landing page alone is not acceptance.