Purpose and ownership
Defines the page title, primary search intent, audience, evidence requirement, conversion goal, schema and related pages.
The system behind the pages
A modular framework for findable, trusted public evidence.
The Bordales Public Evidence Framework turns a professional website into a structured knowledge system. Every page has a purpose, evidence rule, search intent, conversion goal and internal-link responsibility.
Why a framework?
A growing site needs rules, not repeated improvisation.
Without a system, pages duplicate keywords, make unsupported claims, create broken journeys and become difficult to maintain. The Bordales Framework treats each page as a contracted part of a larger information architecture.
The result is modular and scalable: new pages reuse the same visual language, accessibility rules, navigation patterns, content structure and validation while owning a distinct search and user purpose.
Six framework layers01 · Page contract 02 · Content model 03 · Component system 04 · Search architecture 05 · Evidence layer 06 · Validation
The Bordales public-site architecture.
Structured public knowledge
Separates durable capability records, published insights, case-study evidence and current-work updates.
Reusable visual language
Shared heroes, contracts, cards, process steps, evidence blocks, metrics, calls to action and responsive layouts.
One clear intent per page
Prevents keyword cannibalisation and connects supporting pages through deliberate internal links.
Claims connected to proof
Capabilities link to case studies, career evidence, published thinking or public outcomes instead of standing alone.
Quality before publication
Checks required files, metadata, links, JSON structure, page contracts, privacy boundaries and runtime behaviour.
Page-contract anatomy
What every Bordales page must know about itself.
Audience question
What real question brings someone to this page?
Primary intent
Which topic or search need does this page own?
Evidence requirement
What must be present before the page may make its claim?
Section order
What understanding must be built before the call to action?
Internal links
Which related pages deepen, prove or continue the journey?
Conversion goal
What useful next action should the visitor be able to take?
Schema intent
How should machines understand the page type and content?
Privacy boundary
Which information may never cross into the public surface?
Current implementation
The portfolio as a framework proof.
13contracted core pages
15public awareness records
2runtime modes: API and browser fallback
1connected public evidence graph
Framework rules
What keeps the system coherent.
- Human-first language with technical depth available
- One primary topic and conversion goal per page
- Evidence before claims and outcomes before buzzwords
- Public-safe summaries that protect confidential implementation
- Reusable components instead of visual one-offs
- Responsive and accessible interaction by default
- Internal links that create a deliberate knowledge graph
- Validation before deployment and publication
Framework growth
How the site expands without losing control.
Register the page
Assign purpose, intent, evidence, schema, conversion and related routes.
Compose from approved components
Use the shared design system and section patterns.
Add evidence-led content
Write real copy with clear public/private boundaries.
Connect the graph
Update navigation, awareness records, internal links and sitemap.
Validate and deploy
Run automated checks, health tests and release evidence.
Built by Bordales Technologies
A framework for websites that must become business systems.
The same principles can support professional portfolios, service businesses, content hubs, client platforms and multi-site digital estates.