Domains
A site address.A connection point.
Your primary domain and service addresses form one clear connection. Psssst links them to the right launcher and configuration.
From task to outcome
A website starts with an address.A connection starts with a link.
Every address has a role: where the site runs, where modules are delivered from and which environment they serve. Linking domains and launchers brings these settings together instead of scattering them across pages.
How it works
- Primary address
- A domain links to a project and its launcher. The configuration belongs to an identifiable site.
- Service addresses
- Delivery addresses and technical bindings are considered alongside the main site, within the same connection context.
- Scope
- The launcher checks the current domain and receives the module configuration permitted for it.
In practice
A public website and a separate test environment need intentional settings for each address. Begin with a map of the domains, their purpose and their launcher connections.
Boundaries and context
A domain binding defines the entry point. DNS, certificates and publication are coordinated with project infrastructure; business scenarios remain with the connected products.
In brief
Can several websites use Psssst?
Yes. Domains and their associated launchers organize connections for different websites.
Are a domain and a launcher the same thing?
A domain defines the address. A launcher defines the connected modules and configuration. They are linked, with different roles.
Where do we start?
Start with your task, data sources and expected result. Then we can agree on configuration and connection.
Start with your task.
Tell us what your website or product needs. Together we can define the right connection.
Discuss a connection