Behind the StemEra Health Website: Content, Design and Development

OctalFox’s work for StemEra Health brought together content strategy, research and content preparation, writing, graphic design and web development. The project brings specialist information into a business website: explaining the offer, organising resources and helping visitors find more information.

The StemEra Health website includes a public “Powered by OctalFox” footer credit. This article describes the confirmed scope and examples visible on the live homepage, reviewed on 26 October 2026. It focuses on the website work rather than clinical advice or measured business outcomes.

The project context: information and services together

StemEra Health presents stem cell banking information and services. Its website brings service information, educational material, events, publications and team information into one public presence.

That combination creates a useful website planning question: how can an organisation explain its subject while helping visitors find the part relevant to them? Someone looking for an introductory resource may need a different route from someone seeking service information or details about the organisation.

The homepage visibly accommodates these different entry points. It introduces the organisation, provides a services and education section, and includes sections for events, publications, resources and the team. These observations describe the page structure; they do not establish how visitors actually use it.

What OctalFox contributed

Our project records identify five areas of contribution. Together, these contributions connect content planning with visual presentation and implementation.

Confirmed contribution	What that means within this project account
Content strategy	Planning the website’s content approach
Research and content preparation	Research and preparation supporting the written material
Content writing	Producing website copy within the agreed project scope
Graphic design	Contributing graphic design alongside content and development
Web development	Implementing the website as part of the combined delivery scope

The work is also described in OctalFox’s StemEra Health project summary. The footer credit provides public credit; the project records provide the more specific account of our contribution.

Content strategy: give information a place

An information-led website needs decisions about what belongs on the homepage and what deserves a separate page or resource. A list of everything an organisation knows is not necessarily a useful starting point for a visitor.

On StemEra Health’s homepage, service and educational information sit alongside dedicated sections for events, publications and the team. This provides a concrete example of content being grouped by purpose rather than presented as one continuous explanation.

For a business planning similar work, the practical lesson is to identify the visitor questions before deciding the page list. Which questions introduce the subject? Which explain the service? Which require a more detailed resource or a conversation? Content strategy gives those decisions a place in the website brief.

Our clinic website planning guide explores that wider planning task. Use it to develop the page requirements for your own website.

Research and writing: connect the subject to the page

Research, preparation and writing formed part of OctalFox’s confirmed scope. Together, these activities support the task of turning source material into website content with a defined purpose and location.

The current homepage includes educational resources on distinct subjects, including the difference between banking and therapy and an explanation of storage. Their presence illustrates how a website can separate introductory material into more focused reading routes.

The important distinction for another business is between preparing content and substantiating specialist statements. A website delivery project should identify who supplies authoritative information and who approves it. This article does not independently verify StemEra Health’s medical, regulatory or service claims.

For your own project, record the source, reviewer and approval status of important statements before publication. That makes the content easier to review and maintain when services or supporting information change.

Graphic design: work with the content hierarchy

Graphic design was part of the project alongside the written and technical work. On the live homepage, headings and distinct content sections separate the introduction, educational material, events and team information.

That visible hierarchy matters as a design example: the page has several types of information, and each needs a clear place. Layout, typography and graphics can support that organisation instead of making every item compete for attention at once.

When briefing a comparable website, review content and presentation together. A service introduction, an article preview and a team profile do different jobs. Ask how each will be presented, what information it needs and where it leads next.

Include mobile layouts, keyboard access and the clarity of each next step in your own design review. Agree how these will be checked before approving the finished website.

Development: bring the content and presentation into use

Web development completed the confirmed combination of content and design work. The live site provides a public example that can be visited and reviewed alongside the project scope.

For a prospective client, that is a useful way to examine website work: inspect the actual site, then ask what the provider contributed. Look beyond the opening screen to the content organisation and the routes between different types of information.

The same questions should inform a new development brief. Which page types are required? Who will update resources? What should happen when a visitor wants more information? Which third-party tools, if any, belong in the agreed scope?

OctalFox’s web development service explains how requirements, implementation, testing and handover can be addressed in a website project. Use these considerations to define the responsibilities and review points in your own project.

What this example can help you assess

The StemEra Health website is useful as an example of work covering both content and website development. It lets a prospective client discuss how those capabilities relate to a real website rather than considering each service in isolation.

When reviewing this or another portfolio example, ask:

• What content, design and technical work did the provider actually deliver?
• How does the page structure separate services, resources and company information?
• Which parts are relevant to the requirements of your own business?
• What evidence would you need before accepting a claim about performance?
• Who will own content review and updates after your project is delivered?

Our records do not establish traffic growth, inquiry increases, revenue changes or patient outcomes for this project. The project records and footer credit show OctalFox’s involvement and the work included. Any future account of results would need separately verified measurement and context.

Plan the connected work your website needs

StemEra Health’s confirmed scope shows how research, writing, graphic design and development can form one website engagement. For another organisation, the right combination should follow its audience, content responsibilities and practical requirements.

Explore OctalFox’s health, wellness and lifestyle focus for the wider industry context, or brand and digital experience capabilities when your requirements span several connected areas.

Have a content-led website in mind? Discuss your website requirements with OctalFox and share the information, page types and internal expertise available for the project.