01 / Hook
Section jobOpen The Lab as an active proof environment, not a static archive.
Likely shellAuthority hero with one anchor claim, one start-here action, and a visible current-readout panel.
Cross-reference appliedThe current Lab hero, the recurring anchor demo, and the rule that authority still needs a clear entrance.
Pain point to solveIf the top feels too academic, people bounce. If it feels too generic, the Lab loses its authority value.
OpportunityThis is where the brand can feel disciplined, active, and useful enough to explore.
Must includeStart-here logic, visible proof posture, and a reason to keep scrolling.
Watch-outDo not open with a wall of references. The first screen should invite movement into proof.
The Lab should feel like the brand’s central proof environment: active, readable, and worth returning to.
The first section needs to say that this page holds demo videos, document workflows, instrument context, and interpretive articles without feeling like an archive index.
The visitor should understand that this is where Voy Veil shows its work. It should feel disciplined enough to trust and structured enough to enter quickly.
The top has to create movement: one clear way to start, one reason the page matters, and one signal that the proof library is alive.
Primary CTA: Watch Intro
Secondary CTA: Browse Documents
Proof hub
What should the Lab open with?
Use the hero to make the page feel active, structured, and easy to enter before the deeper proof library takes over.
Categories
See all CategoriesDiscover apps based on these most popular use cases.
Project management
Manage and track important tasks directly from your inbox.
CRM
Manage your customers all in one place.
Customer support
Add people to your team and control what they can access.
Communication
Stay in the loop and keep up to date with Communication apps.
Popular apps you might like
See all popular appsBrowse through the most commonly enabled plugins in Front.
Icon
Zapier
Connect Front to hundreds of apps with plug-and-play Zaps
Icon
Hubspot
Log messages and update CRM records in real time
Icon
Create Zoom meetings from your Front calendar or comments
Icon
Salesforce
Create and update Salesforce records directly from Front
02 / Start Here
How to enter the proof library
02 / Start Here
How to enter the proof library
Section jobShow the three cleanest ways into the Lab: demos, research library, and protocols.
Likely shellThree-card entry row with one-sentence explanations and obvious next clicks.
Cross-reference appliedThe current top-grid cards in lab.html and the requirement that the page remains navigable.
Pain point to solveWithout a clear start-here layer, the Lab can feel too broad even if the content is good.
OpportunityThis section turns authority into usability.
Must includeThree obvious entry paths, short descriptions, and confident routing.
Watch-outDo not oversaturate this with detail. It should route, not repeat the whole page.
The Lab needs an entry layer that shows people where to start without asking them to scan the whole page first.
This section should compress the page into three understandable doors: watch a live demo, open the research library, or inspect the instrument workflow.
The structure matters because authority pages are easier to trust when they are easier to navigate.
The cards should feel like guided choices rather than category labels.
Paths: live demos, research library, instrument protocols
What should this section explain?
Why should the Lab make the product more trustworthy?
Use this block to explain that Voy Labs exists to make the process visible, not just the conclusion. The visitor should understand that testing, measurement, and publishing habit are part of the product story.
The point is not content volume. It is to make clear that authority comes from visible workflow, repeatable standards, and a public proof record people can inspect.
Transparency first
Show the method, not just the claim.
Authority through process
Make workflow and measurement feel visible and retained.
Commercial meaning
The product should feel stronger because the team behind it tests more and shows more.
Why Voy Labs exists
A better product starts with visible proof.
Voy Labs exists to make testing, measurement, and product reasoning public. We want you to see how we think, how we measure, and how each product earns its place before you decide to trust it.
No other EMF team is building a public proof library this actively. The videos, documents, and ongoing tests are here so the product feels grounded in real knowledge, not just marketing language.
Watch the tests
We show the setup, the tools, and the conditions behind the result.
Go read the reports
The library stays open so you can inspect the thinking, not just the headline claim.
Building the results
When the team knows more, tests more, and publishes more, the final product gets stronger.
03 / Video Proof
Keep the Lab feeling active
03 / Video Proof
Keep the Lab feeling active
Section jobMake the Lab feel active and easy to enter through recent or grouped video proof.
Likely shellFeatured intro line plus a four-card video grid.
Cross-reference appliedThe current video-chip and card library in lab.html.
Pain point to solveWithout visible motion, the Lab risks feeling archival rather than alive.
OpportunityVideo is the easiest bridge into proof for broad audiences.
Must includeAnchor demo, one beginner video, one protocol video, and one real-life test cluster.
Watch-outDo not let the section become a pile of thumbnails without hierarchy.
The Lab should feel active because proof is easier to trust when it looks current, repeatable, and easy to enter.
This section should use the video system to make the page feel alive. The visitor should see a featured anchor demo, a few current entry points, and enough categorization to stay oriented.
The point is not just content volume. It is movement, proof habit, and visible publishing rhythm.
People should feel that this page keeps producing useful proof, not just preserving one old claim.
Video set: anchor demo, basics, protocol, real-life tests
What should video proof make easy?
Use the video row to make the Lab feel active, current, and simple to enter before deeper documents take over.
Demo
Anchor demo
Lead with the recurring baseline-versus-shielded proof block.
Basics
Signals 101
Keep one beginner-friendly video path visible.
Protocol
Meter setup
Show the workflow behind the result, not just the conclusion.
Routine
Real-life tests
Group nursery, stroller, and travel scenarios into one practical cluster.
Videos make the Lab feel active.
Start with the recurring anchor demo, then move into basics, protocols, and real-life tests without losing the thread.
Featured
Baseline versus shielded
The recurring anchor demo most visitors should watch first.
Playlist
Wi-Fi, Bluetooth, 4G, and 5G basics
A beginner-friendly walkthrough of the common signal environments in daily life.
Guide
Meter positioning and distance
A protocol page for viewers who want the workflow behind the reading.
Series
Nursery, stroller, and car tests
A grouped row for the real-life places families ask about first.
04 / Research Library
Documents should feel like a real library
04 / Research Library
Documents should feel like a real library
Section jobShow the document library as a serious, readable archive rather than a dump of links.
Likely shellShort intro and a document table with title, type, role, and open link.
Cross-reference appliedThe current lab document table and the desire for white papers, references, and deeper notes to stay useful.
Pain point to solveDense research content can feel inaccessible without a clear structure.
OpportunityThis section is where the Lab earns its “real library” feeling.
Must includeDocument titles, types, short plain-language role descriptions, and a strong open action.
Watch-outDo not let the table become visually dead or too bureaucratic.
The document section should feel like a real research library: serious, indexed, and still readable.
This is where white papers, protocols, reading lists, and outside references become useful instead of intimidating.
The table should tell visitors what each document is for, not just what it is called.
If this section works, it signals that the brand has a publishing habit and a structure behind the proof.
Documents: blanket sequencing, protection vs lab, protocol standard, reading list, physician index
What should the library make legible?
Use the document block to organize white papers, protocols, and references into something visitors can actually move through.
| Document | Type | Role | Action |
|---|---|---|---|
| Blanket-first sequencing | Framework | Show how the flagship product introduces the larger system. | Open |
| Protection versus The Lab | Page logic | Separate consumer explanation from proof-heavy substantiation. | Open |
| Instrument protocol | Method | Document the tools, setup conditions, and repeatable workflow. | Open |
Documents should feel like a real research library.
White papers, protocol notes, reading lists, and outside references gathered into one serious archive.
| Title | Type | Why it matters | Open |
|---|---|---|---|
| Blanket-first sequencing | Framework | Explains why the blanket is the first and clearest entry point into the system. | Open |
| Protection versus The Lab | Guide | Keeps consumer-facing protection language distinct from proof-heavy Lab content. | Open |
| Instrument protocol | Method | Describes the conditions, tools, and framing used in attenuation demos. | Open |
| EMF basics reading list | Reading list | Gives newcomers a plain-language path into the wider research context. | Open |
| Physician resource index | Reference index | Collects outside voices and practitioners that inform the broader library. | Open |
05 / Interpretation
Articles and publishing standard
05 / Interpretation
Articles and publishing standard
Section jobShow that the Lab does more than store proof: it interprets and republishes it consistently.
Likely shellArticle grid plus a publishing-standard close band.
Cross-reference appliedThe current Lab article cards and the publishing-habit section at the bottom of lab.html.
Pain point to solveWithout interpretation, the proof feels dense; without publication rhythm, the trust feels static.
OpportunityThis is where the Lab becomes a returning destination, not a one-time proof page.
Must includeInterpretive article layer, publishing-standard signal, and one strong close action.
Watch-outDo not end with loose content leftovers. The bottom should feel like a standard, not a pile.
The Lab should end by proving that credibility comes from a publishing habit, not from one impressive section.
This closing section should show that articles interpret the deeper material and that the brand keeps the content library active enough to build trust over time.
The close should feel like the page’s standard: clear sources, repeatable workflows, and ongoing proof that people can learn from.
The visitor should leave feeling that The Lab is worth returning to.
Close: articles, interpretation, standards note, repeatable publishing rhythm
Scaffolding Shelf
Labs V1 script and page posture
Labs V1 keeps the existing Lab content model, but adds the section workflow so the page can be rewritten deliberately instead of being redesigned blind.
Open labs v1 scaffolding
Core Snapshot
Labs V1 matrix
| Thesis | The Lab should feel like Voy Veil’s active proof environment: demos first, documents second, interpretation third. |
|---|---|
| Posture | Authority-led, technology-readable, structured enough to trust, and current enough to revisit. |
| Story arc | Open the proof hub, show where to start, make video proof feel active, organize the research library, and close with articles plus publishing standards. |
| Why it matters | This page becomes the brand’s proof headquarters, not just a resource dump. |
Keep from the current Lab
- The hero idea of demos, methods, and proof.
- The top-grid structure for live demos, research library, and protocols.
- The video proof row that keeps the page feeling active.
- The document table that makes the library feel serious.
- The article and publishing-standard close.
Do not drift
- Do not make the Lab feel like a generic blog page.
- Do not let documents overpower entry logic.
- Do not remove the video system; it is the easiest path into proof.
- Do not make the page feel archived or inactive.
- Do not let the close dissolve into random content links.