This guide is for communication leads of ocean, climate and Earth-observation programmes and for product owners in public institutions. It sits under Netbase's software product engineering work and explains the method, not a delivered case.
In this guide
- Why does a PDF report fail most of its readers?
- What content model does a science story platform need?
- How does layered reading work without asking "who are you?"
- Which visual components should be built once and reused?
- How do you build the platform, step by step?
- How do you keep the platform accessible, fast and light?
- What should security and operation cover?
- Where AI fits
- What delivery record exists, and what does not?
- Alternatives: which route fits your programme?
- Handover that makes the programme independent
- Limits of this guide
- Frequently asked questions
- Next step
Why does a PDF report fail most of its readers?
Ocean and Earth-observation programmes write for very different people. A policy officer has three minutes and needs the message. A coastal manager has ten minutes and needs to know which service to use. A scientist wants the method, the data source and the references.
A PDF serves only one of them well. It is linear. It is hard to read on a phone. It ages as soon as a link changes. A web copy of the PDF keeps the same problems.
Three questions decide whether a story platform will work:
- Can a reader get the message in three minutes and go deeper with one action?
- Can the programme's own staff add the next story without a developer?
- Will the platform still be secure, fast and maintained three years from now?
What content model does a science story platform need?
Start with the content, not the design. A good model for science storytelling has six content types: the story, the steps of a value chain (for example from observation to decision), key messages, visuals, external resources and references.
Each piece of text exists at three levels: a key message, an explanation and the full detail. The key message is one or two plain sentences. The explanation adds context for a practitioner. The full detail holds the method and the references for a scientist.
A resource, such as a data service, is entered once and appears in every story that uses it. That is how a reader discovers that the same satellite mission supports work on algae blooms, sea ice and fisheries.
With this model, a new story is an editor's task, not a development project.
How does layered reading work without asking "who are you?"
Many sites ask the visitor to choose a profile: citizen, expert or decision maker. Most visitors do not know which one they are.
Layered reading works better. Everyone starts with the same short page. A clear control opens more detail in place, and the reader never loses position. Reader profiles still help, but they work behind the scenes: they decide which content comes first, not which door the reader must pick.
Which visual components should be built once and reused?
Interactive visuals are where science stories come alive, and where budgets are often lost. The answer is a small library of components that editors configure with data and text:
- a map with layers and points of interest;
- a timeline;
- a chart with an equivalent data table;
- a before-and-after comparison;
- a value-chain diagram that doubles as navigation;
- a resource card that sends the reader to the service that holds the data.
The open-source ecosystem for this work is mature, and every project below belongs to its own authors and community. NASA's open VEDA UI repository shows how Earth-observation data stories can be assembled from reusable blocks. The figures in this table were read from the GitHub REST API on 2026-11-17 and will change over time.
-
MapLibre GL JS (maplibre/maplibre-gl-js)
- Role in a science story
- Interactive vector maps without a proprietary licence
- Licence
- BSD-3-Clause
- GitHub stars
- 12,107
- Latest release
- v6.18.0 (2026-11-11)
-
D3 (d3/d3)
- Role in a science story
- Custom charts and diagrams, such as a value chain
- Licence
- ISC
- GitHub stars
- 113,949
- Latest release
- v7.9.2 (2026-11-03)
-
Observable Plot (observablehq/plot)
- Role in a science story
- Quick, consistent statistical charts
- Licence
- ISC
- GitHub stars
- 5,427
- Latest release
- v0.6.19 (2026-11-05)
-
Apache ECharts (apache/echarts)
- Role in a science story
- Ready-made interactive charts and time series
- Licence
- Apache-2.0
- GitHub stars
- 67,740
- Latest release
- 6.1.0 (2026-05-19)
-
deck.gl (visgl/deck.gl)
- Role in a science story
- Large geospatial datasets on a map
- Licence
- MIT
- GitHub stars
- 14,764
- Latest release
- v9.3.12 (2026-10-30)
-
Scrollama (russellsamora/scrollama)
- Role in a science story
- Scroll-driven narrative steps
- Licence
- MIT
- GitHub stars
- 6,013
- Latest release
- No GitHub release; last push 2025-11-13
-
NASA VEDA UI (NASA-IMPACT/veda-ui)
- Role in a science story
- A public example of Earth-observation data stories built from reusable blocks
- Licence
- Apache-2.0
- GitHub stars
- 45
- Latest release
- v6.21.0 (2026-06-10)
Stars show community attention, not fitness for a project. A platform built on these projects should credit them and keep an inventory of every component and its licence, so a programme can hand the platform to any future provider. Getting engineers to reuse such a library is covered in design system adoption.
One rule keeps the science honest: the platform explains and links, it does not duplicate. Data stays with the operational services that own it.
How do you build the platform, step by step?
-
Map the readers
List every reader group, its question and its time budget from two or three existing reports.
-
Write the content model
Define content types, the three reading levels and the shared resources.
-
Build a pilot story
Rebuild one real report in that model before designing the full site.
-
Inventory the components
Choose each visual component and record its licence and owner.
-
Test layered reading
Test the pattern with a reader from each group.
-
Set budgets
Set accessibility and page-weight budgets, and test both before every release.
-
Hand over
Train the editors and let them build a test story on their own.
Netbase's six-step lifecycle runs from discovery and architecture planning through agile milestones and modular components to training, rollout and ongoing support. The pilot story sits in its first steps, so the content model is tested before most of the budget is spent.
How do you keep the platform accessible, fast and light?
A public platform must work for everyone. Design to WCAG 2.2 level AA: keyboard navigation, a text alternative for every visual, a data table beside every chart and plain-language key messages. A chart needs a long description or a table, not just a short label.
Speed is part of accessibility. Set a weight budget for each page, load interactive components only when the reader reaches them, and measure real loading times before each release. The same discipline appears in our guide to a performance budget and Core Web Vitals.
What should security and operation cover?
A platform that carries the name of a public institution is a target, so security belongs in the plan. Netbase's own security practices include secure code review, role-based access control, multi-factor authentication for admin dashboards, vulnerability scanning and penetration testing, and disaster recovery.
A platform of this kind is usually operated with:
- a web application firewall in front of the site;
- least-privilege roles for editors;
- off-site backups with a scheduled restore test;
- vulnerability tracking for every component, with patch deadlines;
- a written incident process and hosting in the region the programme requires.
A public body that plans the service with a remote partner can use our note on who owns what in an e-government service.
Where AI fits
Language technology can save editors time: a first translation draft for an editor to correct, a suggested text alternative for a chart, or a search that returns the original passages. An editor reviews every output before publication, and every assisted feature can be switched off. Netbase works with the major commercial and open-source AI tools and models, chosen per project, under human control.
- In delivered work
Recommendation engine
A recommendation engine delivered for 4over4's online printing store; it is not a science or Earth-observation feature.
- Available capability
Editorial assistants
Translation drafts, text-alternative suggestions and passage search for editors; not yet tied to a published case.
What delivery record exists, and what does not?
Netbase JSC was founded in 2012, has served 500+ clients and has worked with clients in 80 countries. It designs, builds and runs software across technologies and industries.
The registered record that relates to this topic is web platforms and dashboards. Netbase built Dey Page, a server-rendered, mobile-first web directory with state, city and category pages, five admin roles and per-state dashboards. Netbase also deploys help desk and CRM systems that bring client requests into one dashboard.
Netbase does not claim a delivered ocean-science or Earth-observation platform. This guide explains the problem and the method; it is not a case study.
Alternatives: which route fits your programme?
Score the three realistic routes on these criteria.
| Criterion | PDF plus a web page that copies it | Hosted story-map or scrollytelling service | Custom platform on open components with a content model |
|---|---|---|---|
| Reader time | Linear; the reader searches for the message | Good for one story at a time | Layered; the message in minutes, detail on demand |
| Editor independence | High for the PDF, low for the web copy | High inside the service's templates | High once the templates exist |
| Accessibility | Hard to make a PDF fully accessible | Depends on the service's output | Designed and tested to WCAG 2.2 AA |
| Data freshness | Ages with every changed link | Manual updates per story | Shared resources updated once |
| Reversibility | High | Low to medium; export varies by service | High with the source code and licence inventory |
| Cost drivers | Layout and translation | Subscription seats and per-story effort | Build of the model and components, then operation |
Choose the PDF route when there is one report, one audience and no plan for a series. Choose a hosted story-map service when a small team needs a few stories soon and accepts the service's limits. Choose a custom platform when a programme publishes a series, needs layered reading and shared resources, and must be able to change provider later.
Do not build a custom platform when there is no editor to own it after launch. Without that owner, the platform ages as fast as the PDF it replaced.
Handover that makes the programme independent
In Netbase's custom development, the client owns the IP created for it. A good handover delivers the complete source code, step-by-step guides for each editor role, short training for each module and a reversibility plan. Our transition and knowledge-transfer plan lists what to check.
Before handover, the programme's editors should build a test story on their own. If they can, the platform is ready.
Most Netbase projects are delivered on fixed-price contracts; milestone and retainer models are also offered. Netbase can plan such a platform through web application development and UI/UX design.
Limits of this guide
- It describes a method, not a delivered Earth-observation project.
- The open-source figures are a snapshot from 2026-11-17 and change over time.
- It does not replace an accessibility audit or a legal review of licences.
Plan the next step with a Netbase consultant
Frequently asked questions
Yes, if the platform is built on a content model with templates for each content type. Editors then fill in a story, its key messages, visuals and resources. A developer is needed only for a new kind of visual component.
A public science platform should meet WCAG 2.2 level AA. In practice that means keyboard navigation, a text alternative for every visual, a data table beside every chart and plain-language key messages, tested before every release.
No. Netbase does not claim a delivered ocean-science or Earth-observation platform. Its registered record covers web platforms and dashboards, and this guide sets out the method it would apply.
Next step
If you are turning reports into an interactive platform, send us your documents and your deadline and we will reply with a structure proposal.
Related services and solutions
AI-enabled software product engineering from discovery to operation Netbase provides software product engineering for companies that need a web, SaaS, mobile or custom platform built and kept running, with AI features and AI-assisted engineering where they pay off. We cover the full lifecycle, from discovery to operation, and the same team stays accountable for architecture, delivery and handover, so nothing important gets lost between phases.
Learn More
Web application development with AI built in where it converts Netbase provides web application development for product and commerce teams that need fast, maintainable web apps and storefront front ends, with AI search, assistants and automation added where they measurably help. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to its published case studies, PrintLeo's page load improved 35% and 4over4's conversion rose 48%.
Learn More
UI/UX design services: research, interfaces and design systems built in code Netbase designs the interfaces of web apps, SaaS products, mobile apps and online stores: user research, flows, wireframes, clickable prototypes and visual design, plus a design system shared by designers and developers. Because UI/UX designers sit inside the delivery team, the same people who design a screen see it built, tested and released.
Learn More
Digital product accelerators for SaaS, mobile and AI products Digital product accelerators are Netbase-built modules and delivery patterns that help founders and product teams launch SaaS, mobile and AI products faster. Instead of rebuilding accounts, billing, workflows and integrations from scratch, you reuse proven components, spend engineering time on what makes your product different, including the AI features buyers now expect, and own the custom code built for you.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.