Skip to content

Explore

Knowledge Product

Nexus Knowledge and Publication System

This website connects free texts, books and research through paths for different interests.

Public reader and research system
Actual English home page with the Closer to life introduction and the grail illustration.
Own website · actual view captured 29 October 2026

Problem and result

A wealth of knowledge. A clear way in.

A large bilingual research and writing project can confuse readers if book, protocols, research notes and claims boundaries are not separated.

How the scope was defined

Keep the reader homepage intact and add structured paths for publication, research, practice and evaluation.

My responsibility

I own the conceptual architecture, editorial system, product decisions and boundary setting. Implementation has been developed with technical tooling and AI assisted coding support.

What exists

  • Bilingual reader routes and topic paths.
  • Book, protocol, whitepaper and research entry points.
  • Claims and scope documentation.
  • Audience separation between readers, evaluators and professional reviewers.

The system is a publication and knowledge product. Scientific, health and commercial claims remain bounded and require careful source review.

Workflow at a glanceFrom a body of work to a reading path

Public reader and research system

  1. Texts and sources

    Books, protocols and research questions have distinct starting points.

  2. Choose a path

    The reader's interest determines where to go next.

    • Reading
    • Research
    • Practice
  3. Read and examine

    Texts, sources and the limits of claims remain distinct.

Human reviewEditing and source review remain human responsibilities before claims are extended.

Public reading paths do not establish clinical effectiveness or scientific consensus.

Examine the work

Open the actual pages

These own-project pages are publicly readable. They show structure and implementation, not paid client delivery or business results.

Scope, evidence and technical limits in detail

Product problem

The same body of work must serve readers, scientific evaluators, institutional partners and professional reviewers without collapsing all needs into one homepage.

Users or reviewers

Readers, scientific evaluators, institutional partners, hiring managers and Product Leads interested in knowledge architecture.

Product decision

Separate Nexus as the public knowledge and practice work, Water Is the Holy Grail as book origin, and Professional Work as the proof surface.

Scope and explicit exclusions

  • Included: bilingual routes, reader paths, research field, protocols, book and whitepaper entry points.
  • Included: claims boundaries for health, scientific and symbolic statements.
  • Excluded: medical advice, validated health product claims and commercial performance promises.

Implementation evidence

  • The website exposes German and English reader paths.
  • The research field keeps source and outline work inspectable.
  • The proof surface keeps professional cases outside the primary reader journey.

My role

I own the conceptual architecture, editorial system, product decisions and boundary setting. Implementation has been developed with technical tooling and AI assisted coding support.

What this demonstrates

  • Long term Product Ownership of a complex knowledge system.
  • Audience separation as a product architecture problem.
  • Bilingual publication structure and editorial governance.
  • Claims discipline in a sensitive topic area.

What remains untested

  • Clinical validation.
  • Scientific consensus for every hypothesis.
  • Commercial traction.
  • A finished institutional product.

Inspection path

  • Open the reader routes and compare English and German structure.
  • Inspect the research and claims boundary documents.
  • Check how the new Work surface leaves the reader homepage intact.

Human review boundary

Scientific and health adjacent statements require source review and careful wording before public expansion.

Current maturity

Public website and research publication architecture with controlled professional separation.

Next evidence needed

Reader feedback, institutional review or a specific editorial partnership should determine the next expansion.

Website care & technical security maintenance

A good website stays manageable after launch.

For your new or existing website: a focused review, agreed improvements and a handover you can work with. Ongoing care can be arranged to suit the site.

Maintenance you can follow

Review known security advisories, test suitable updates and check important visitor journeys. Receive a clear account of completed work and remaining issues.

Less unnecessary data

Keep forms focused, load external content deliberately and match consent to the feature. Data flows and required provider agreements are clarified before use.

A clear operating handover

Access, responsibilities and recovery belong in the handover. Ongoing care has an agreed system scope, schedule, budget and response times, so you know who handles what.

The deliverable is documented technical work. Legal review, independent penetration tests and 24/7 incident coverage are separate services. Privacy decisions and approvals are agreed with the responsible operator.

The next step

What would you like to make easier?

Describe the task, the people involved and the outcome you need. A few sentences are enough for an initial conversation.

Discuss a similar task

A non-binding enquiry. We agree scope, price and acceptance before an assignment.

Please leave confidential documents out of your first message.

Or by emailhello@wateristheholygrail.com