A CONSISTENT COMPANY PRESENCE
Give every public page a recognizable company identity
Manage the shared appearance of your company site, then check how the selected design works with real content and imagery.
A shared design for a connected website
A service page, contact page and company introduction should clearly belong to the same business. Tsumira separates the shared presentation from the content of each page. This gives the company a consistent starting point while preserving room for an editorial layout, different page sections and actual photographs of its work. A theme is a practical system for readable content, rather than a substitute for deciding what the company wants to communicate.
Choose a coordinated presentation
Supported site themes provide coordinated defaults for the header, footer, typography and color roles. Choose the direction that fits the business and inspect both a short page and a longer service explanation. Individual settings can adapt the shared appearance within the supported structure. Consistent navigation and an intelligible footer help visitors understand where they are and where to continue, including when they enter through a search result instead of the homepage.
- Coordinated theme defaults
- Shared header and footer
- Consistent visual roles
Use the company’s actual identity
Company identity is sourced from the company profile, with supported presentation settings for its use on the site. Keep the name, contact details and logo accurate before spending time on individual page styling. Select real media for the supported image positions and check its crop and meaning in context. An image reference should support the message; changing a theme does not grant permission to use unrelated photographs or rewrite company facts.
- Company profile as identity source
- Supported logo presentation
- Intentional image selection
Review shared changes as a release
Header and footer changes affect more than one page. The publication flow separates draft settings from the publicly released presentation and checks relevant navigation destinations. Review the first impression, long headings and mobile navigation before releasing the shared change. Existing custom content still requires its own editorial attention. A design preset does not establish that every legal statement, price or service promise on the site is correct.
- Draft and public settings separated
- Navigation destinations checked
- Desktop and mobile review
A concrete workflow
Check identity
Confirm the company name, logo asset and public contact information.
Select a theme
Choose a supported presentation and adjust its available settings.
Review real pages
Inspect actual text, imagery and navigation at narrow and wide widths.
Release shared presentation
Publish the approved settings and verify the live visitor journey.
An illustrative working example
Example: a consultancy refreshes its presentation
A consultancy keeps its established logo and updates the shared header, colors and footer. It checks an introductory page and a dense service page before release, replacing a poorly cropped image with an appropriate company asset. The service information remains owned by its editors. The result is a more consistent site without treating a visual refresh as evidence that its commercial or legal content has been reviewed.
Questions about this topic
Can we retain our existing logo?
Yes. Use the company’s actual logo asset in the supported presentation. A theme change does not require inventing a replacement identity.
Does a theme update rewrite every page?
Shared presentation and page content are separate concerns. Generated or custom content follows its own editing and ownership rules.
Are header and footer edits immediately public?
The supported flow distinguishes draft shared settings from their publication. Review and publish deliberately.
Should we check mobile layouts separately?
Yes. Long names, navigation choices and image crops can behave differently at narrow widths, so verify representative pages before release.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Drive
Workflow concept: Keep approved logo and image assets together for shared header and page presentation review.
Notion
Workflow concept: Document the chosen theme, image rules and company identity decisions for editors.
Microsoft Teams
Workflow concept: Review desktop and mobile examples with the people responsible for the company’s presentation.