OceanHub
A partner-facing offshore energy and marine intelligence portal, with a reproducible content + deck pipeline.
TL;DR
- Problem: Offshore projects often have fragmented stakeholders, unclear narratives, and slow partner onboarding.
- Data: Markdown-first focus areas and insights, maintained as a structured content collection.
- Method: Astro + Tailwind site with typed content collections; automated partner deck generation from source content.
- Output: A platform-style portal prototype + a reusable partner introduction deck (v1).
- Impact: Faster alignment across ecosystem partners and a repeatable workflow to publish updates consistently.
- Links: Public reference: SBGf Rio 25 OceanHub (conference page).
What I built
OceanHub is a platform-style portal designed to align clients and ecosystem partners around offshore energy, monitoring, and marine intelligence.
Key components:
- Partner-facing homepage: platform tone and CTAs (“Explore Focus Areas”, “Propose a Collaboration”).
- Content system: Focus Areas + Insights authored in Markdown and surfaced as routes (content collections).
- Reusable partner collateral: a Markdown/HTML -> PPTX pipeline to generate a partner deck from source files, so the story stays consistent across web and slides.
How it was implemented (high level)
- Frontend: Astro (static-first) + Tailwind CSS, with React used only where needed.
- Content model: type-safe content collections under
src/content/(Focus Areas, Insights, Case Studies). - Deck pipeline: scripts that transform curated narrative into a partner deck artifact (PPTX) for repeatable partner onboarding.