eduKate Sengkang Reader Experience Standard | Protect, Clarify, Connect

Protect the base floor

The eduKateSengkang refresh begins with a simple rule: a page that already serves its reader well should not be rewritten merely because it has entered an upgrade queue. Existing search ownership, useful explanations, stable URLs, successful examples and recent work are assets. The job of the refresh is to make the estate easier to read, easier to navigate and easier to continue from without disturbing what already works.

The reader test

Before changing an article, ask whether the proposed change makes the page easier to understand, easier to scan, easier to trust, easier to navigate or easier to continue from. If it does none of these things, leave the page alone.

Five levels of intervention

Level	Use when	Typical action
1 — Protect	The page is already strong, current, useful or visibly performing.	No substantive copy change. Verify links, owner and return path only.
2 — Connect	The page is useful but isolated.	Add a small reading route, related-owner link, previous/next control or return path.
3 — Format	The content is sound but difficult to scan or navigate.	Repair heading hierarchy, tables, spacing, contents, captions or long unbroken sections.
4 — Surgery	A bounded factual, structural or reader-experience defect exists.	Make the smallest effective change; preserve the rest.
5 — Modernise	The page is materially outdated, mis-scoped or no longer completes its reader job.	Substantive revision in place, while preserving useful base material and URL ownership.

World-class content-design principles we adopt

We borrow principles, not visual imitation. Strong public-service and research-led websites consistently make structure obvious, reduce navigation uncertainty and help readers find the section they need without forcing a linear read.

• Clear heading hierarchy. Headings should describe the section beneath them and form a logical H1 → H2 → H3 structure.
• Front-load meaning. Put the useful point early in paragraphs, headings and links so a scanning reader can understand the page quickly.
• Use visible sections before hidden UI. Prefer clear headings and a contents route to excessive tabs or nested accordions.
• Descriptive links. Link text should tell readers where they are going; avoid vague “click here” language.
• Contextual previous/next routes. When articles form a sequence, name the neighbouring topic rather than offering an unexplained arrow.
• Mobile-first readability. Avoid dense walls of text, over-wide tables and structures that depend on desktop width.
• Accessible information structure. Headings, links, lists and tables should remain understandable to keyboard and assistive-technology users.

Formatting standard for legacy articles

• Keep the existing title and URL when they already own the correct reader/search job.
• Use a concise opening that tells the reader what the article will help them understand or do.
• For long articles, add a short contents or reading-route block near the beginning when navigation genuinely benefits.
• Break long undifferentiated text into meaningful sections; do not manufacture headings merely to shorten paragraphs.
• Use tables only when comparison is easier in rows and columns than in prose.
• Keep prose columns readable rather than stretching text across the full wide layout.
• Use examples, worked cases, diagrams or callouts only when they clarify the learning job.
• Add related routes at natural decision points and a clear return to the owning hub.
• Do not add ornamental components that increase scrolling without improving comprehension.

Navigation pattern

Each substantial article should make three things easy to determine: Where am I? What should I read next? How do I return to the larger subject? The exact interface can vary by article. Consistency of purpose matters more than mechanical sameness.

Reader need	Preferred solution
Understand the page quickly	Descriptive title, short introduction, clear H2 structure
Jump to one section	Contents / anchor links on genuinely long pages
Follow a sequence	Named previous / next article links
Explore a broader topic	Return to the canonical hub or complete index
Move across domains	Contextual bridge only when the learning job genuinely crosses owners

What not to do

• Do not convert every article into a mega-longform.
• Do not change titles or slugs simply for stylistic uniformity.
• Do not replace strong article openings because another template looks newer.
• Do not create another page when an existing owner can be improved in place.
• Do not add tabs, accordions, cards or decorative blocks unless they solve a reader problem.
• Do not force identical layouts across English, Mathematics, Science, examinations and technical knowledge when their reading jobs differ.
• Do not touch recently upgraded or high-performing pages without a specific, bounded reason.

Completion states

A branch may complete an article ID as PROTECT — NO CHANGE NEEDED, CONNECT — NAVIGATION ONLY, FORMAT — READER EXPERIENCE, SURGERY — BOUNDED REPAIR, or MODERNISE — SUBSTANTIVE UPDATE. A no-change decision is a valid and desirable outcome when the base article is already strong.

Estate rule

The goal is not to make every eduKateSengkang article look newly written. The goal is to make the whole estate feel intentionally connected, professionally readable and easy to navigate while protecting the accumulated value of thousands of existing pages.