Archive Navigation Specification

Verse & Variable
A line of verse. A line of inquiry.
لفظ سے لہر تک — Lafz se Lehar tak

1. Purpose

This document defines the information architecture and navigation principles for the Verse & Variable literary archive.

The publication brings together individual literary explorations, multilingual collections, philosophical reflections, cultural traditions, and scientific discussions.

As the archive expands, readers should be able to discover its contents through more than one route.

A visitor may arrive with the name of a poet, an individual literary work, a language, a particular theme, or a scientific concept in mind. The navigation system should accommodate these different approaches without making the archive difficult to understand.

This specification establishes:

2. Navigation Philosophy

The archive should be organised around the reader’s experience rather than the internal structure of the repository alone.

The navigation system should follow these principles.

2.1 Multiple Routes to Discovery

Readers should be able to reach the same article through different meaningful routes.

For example, an Urdu ghazal may be discoverable through:

These routes should lead to the same permanent article page rather than generating unnecessary duplicate content.

2.2 Literary Priority

The archive should preserve the identity of the original literary work.

Scientific classifications, thematic labels, and technical navigation should supplement literary discovery rather than dominate it.

2.3 Progressive Complexity

The initial navigation should remain simple.

More specialised indexes and filters may be introduced as the archive develops and contains enough material to justify them.

A large collection of empty categories is less useful than a small, well-maintained archive.

2.4 Consistency

Navigation labels, URL structures, language identifiers, collection identifiers, categories, and tags should use consistent conventions.

Changes to the information architecture should be reflected in the corresponding templates and documentation.

2.5 Accessibility

Every important navigation route should be usable through keyboards, assistive technologies, and different screen sizes.

Core content should remain accessible without depending exclusively on JavaScript.

3. Information Architecture

The intended archive has the following high-level organisation.

Verse & Variable
|
|-- Home
|
|-- Archive
|   |
|   |-- Latest explorations
|   |-- Weekly collections
|   |-- All individual entries
|   |-- Historical collections
|
|-- Languages
|   |
|   |-- Urdu
|   |-- Hindi
|   |-- Marathi
|   |-- Kannada
|   |-- Tamil
|   |-- Malayalam
|   |-- Telugu
|   |-- Additional languages
|
|-- Literary Forms
|   |
|   |-- Ghazal
|   |-- Nazm
|   |-- Poetry
|   |-- Song lyrics
|   |-- Folk literature
|   |-- Other literary forms
|
|-- Themes
|   |
|   |-- Memory
|   |-- Time
|   |-- Love
|   |-- Identity
|   |-- Nature
|   |-- Human experience
|   |-- Other themes
|
|-- Authors and Contributors
|   |
|   |-- Poets
|   |-- Writers
|   |-- Lyricists
|   |-- Translators
|   |-- Other contributors
|
|-- Scientific Explorations
|   |
|   |-- Nonlinear waves
|   |-- Mechanics
|   |-- Acoustics
|   |-- Metamaterials
|   |-- Computational science
|   |-- Other disciplines
|
|-- About
|
|-- Editorial and Publication Policies

This diagram describes the intended information architecture. It does not imply that every section already has a corresponding public page.

4. Primary Website Navigation

Primary navigation should expose the most important areas of the publication.

The recommended structure is:

Navigation item Purpose
Home Introduce the publication and highlight recent content
Archive Provide access to published literary explorations
Languages Allow discovery through original languages
About Explain the publication’s identity and editorial philosophy

A search control may be added when the search functionality is implemented and tested.

The primary navigation should remain compact.

Additional classification systems should generally be accessed through the archive rather than adding every category to the main header.

4.1 Desktop Navigation

On wider screens, the primary navigation may be displayed horizontally.

The header should provide:

4.2 Mobile Navigation

On smaller screens, navigation may collapse into an accessible menu.

The mobile menu should:

Navigation must remain usable without pointer hover.

5. Homepage Navigation

The homepage acts as the main entrance to the publication.

It should help visitors understand both the identity of the archive and the different ways to explore it.

Recommended content areas include:

5.1 Publication Introduction

A concise presentation of the publication’s identity:

A line of verse. A line of inquiry.

لفظ سے لہر تک — Lafz se Lehar tak

The homepage should communicate the relationship between literary expression and intellectual exploration without implying that every article combines literature with science.

5.2 Latest Weekly Collection

The latest published collection should be discoverable from the homepage.

The presentation may include:

Only published and successfully rendered collections should be presented as available content.

Selected individual articles may be highlighted.

Selection may consider:

Featured status should not imply that other archive entries are less important.

5.4 Language Discovery

The homepage may present a language directory linking to the main language index.

Each language should be identified using its established name and appropriate script where useful.

5.5 Archive Access

Provide a clear route to the complete archive.

Readers should not have to navigate through multiple weekly pages merely to locate an individual article.

6. Main Archive

The main archive provides a consolidated view of published individual explorations.

Its primary purpose is to make the growing collection easy to browse.

6.1 Archive Listing

Each archive item should present relevant information, such as:

The presentation should remain compact enough to support reading through a substantial list.

6.2 Sorting

The default archive order should generally be reverse chronological.

The newest published entries appear first.

Where users need alternative browsing approaches, additional views may be introduced later.

Potential sorting options include:

Sorting should not alter the permanent URL of an article.

6.3 Archive Completeness

The archive should display published content accurately.

Avoid:

6.4 Pagination

If the archive becomes sufficiently large, pagination may be introduced.

Pagination should:

Pagination should be introduced when it improves usability rather than simply because the archive reaches an arbitrary number of entries.

7. Weekly Collection Navigation

Weekly collections are one of the principal organisational structures of Verse & Variable.

Each collection brings together three independent literary explorations.

7.1 Weekly Index

A weekly index should eventually provide access to all published collections.

Each collection item may display:

7.2 Individual Weekly Page

A weekly collection page should display the three associated articles in their intended order.

The current Jekyll architecture uses:

The weekly layout uses the shared identifier to find related entries.

This relationship should remain consistent across all three articles.

7.3 Previous and Next Collections

When multiple weekly collections are available, provide navigation to:

The links should reflect actual publication order.

Do not generate links to collections that do not exist.

7.4 Weekly Continuity

A weekly collection should remain independently meaningful.

Readers should be able to open an individual article directly without first opening its weekly collection.

The weekly index should provide an additional discovery route, not become a mandatory intermediate page.

8. Language-Based Navigation

Language-based discovery is a central feature of the archive.

The language directory should allow visitors to explore works according to their original language.

8.1 Initial Language Directory

The initial directory covers:

Language Original name Language code
Urdu اردو ur
Hindi हिन्दी hi
Marathi मराठी mr
Kannada ಕನ್ನಡ kn
Tamil தமிழ் ta
Malayalam മലയാളം ml
Telugu తెలుగు te

Additional languages may be included when relevant material becomes available.

8.2 Language Index Pages

A dedicated index page for each language may be introduced as the archive grows.

A language page should display:

8.3 Original Language Is Authoritative

Language classification should be based on the original work.

The language of an English translation should not replace the original language identifier.

A translated article remains associated with the language of the original literary work, unless the article itself examines a different work or a distinct multilingual creation.

8.4 Shared Scripts

Languages sharing a writing system must remain independently identifiable.

For example, Hindi and Marathi both use Devanagari.

They should not be merged into a single language category.

9. Literary-Form Navigation

Literary-form browsing allows visitors to explore works according to their structure and genre.

Potential index sections include:

9.1 Classification Accuracy

The literary form should be established through the work’s actual structure and tradition.

Do not assign a form merely because a text resembles another form superficially.

9.2 Multiple Forms

Some works may involve overlapping genres or mixed forms.

The archive should represent such cases accurately without forcing every work into an overly narrow classification.

9.3 Relationship to Categories and Tags

Literary-form discovery should use the controlled vocabulary established in CATEGORIES_AND_TAGS.md.

Avoid creating separate competing classifications through inconsistent spelling or naming.

10. Theme-Based Navigation

Thematic browsing allows readers to explore works that engage with related questions or human experiences.

Potential thematic groups include:

Human Experience

Time and Existence

Nature and the World

Society and Culture

Spiritual and Philosophical Reflection

10.1 Meaningful Thematic Assignment

A theme should be assigned only when the article meaningfully explores it.

A single incidental mention of memory does not justify classifying an entire article as an exploration of memory.

10.2 Thematic Diversity

An article may appear under several thematic indexes.

This should help readers discover related material without implying that every work has one definitive interpretation.

11. Author and Contributor Navigation

An author and contributor index may be introduced when sufficient verified material is available.

It should distinguish between different creative and editorial roles.

Potential indexes include:

11.1 Name Consistency

Use an established display name consistently.

Where a creator’s original-script name is available, it may be presented alongside the preferred English or transliterated form.

11.2 Attribution Roles

Do not combine different roles under an undifferentiated author label when doing so creates ambiguity.

A poet’s collection should not automatically include musical performers as co-authors.

Likewise, the translator of an existing poem should not be listed as the original author.

11.3 Author Pages

An individual author page may eventually provide:

Biographical details should be included only when supported by reliable sources.

11.4 Future Implementation

Author indexes are a proposed extension.

They should be introduced after the publication has established a reliable contributor metadata structure.

12. Scientific Subject Navigation

Scientific subject navigation provides an additional way to discover articles containing substantive scientific discussion.

The scientific index should remain complementary to the literary archive.

12.1 Principal Disciplines

Potential subject areas include:

12.2 Scientific Concepts

More specialised navigation may include:

12.3 Relevance Requirements

A scientific label should be assigned only where the article engages meaningfully with the relevant concept.

A literary metaphor should not automatically become a scientific classification.

An article discussing resonance as an emotional metaphor should not automatically appear in a technical resonance index.

12.4 Scientific Subject Pages

A scientific subject page may eventually include:

Technical definitions should remain consistent with GLOSSARY.md and RESEARCH_STANDARDS.md.

13. Search Functionality

Search is a potentially valuable feature as the archive expands.

However, it should be implemented only after the underlying content and metadata structures have been validated.

13.1 Intended Search Coverage

Search may eventually support:

Multilingual search requires care.

Search behaviour should account for:

An English query should not be assumed to identify every corresponding expression in another language.

13.3 Search Result Presentation

A search result should provide:

Search results should make it clear why a result matched the query.

13.4 Empty Search Results

When no matching material is available, explain that no results were found.

Do not display fabricated suggestions or unrelated articles as though they matched the search.

13.5 Search Implementation

The current project should not assume that search functionality already exists.

Possible future approaches include client-side indexing or another lightweight search solution compatible with the static-site architecture.

Any selected approach should be assessed for:

The first implementation should favour simplicity and reliability.

14. Related Article Navigation

Related-content links can help readers explore connections between literary works and subjects.

Potential relationships include:

14.1 Relationship Quality

An article should not be labelled related merely because it shares a broad keyword.

Relationships should be meaningful and defensible.

14.2 Permanent Article Identity

Related links must point to the original permanent article URLs.

Do not create unnecessary duplicate copies of an article for different subject indexes.

14.3 Previous and Next Articles

Individual article navigation may include previous and next entries where the sequence is meaningful.

Weekly sequencing should use the actual entry ordering.

Where the archive contains no valid neighbouring entry, do not display a broken navigation control.

15. Navigation Within Individual Articles

Every individual literary exploration should provide a clear reading experience.

Recommended navigation elements include:

Navigation should not interrupt the literary experience with unnecessary interface elements.

The original literary work and its commentary should remain the principal visual focus.

The publication uses stable, readable URLs for individual entries and weekly collections.

Current collection patterns:

Individual entries

/entries/:path/

Weekly collections

/weeks/:name/

Recommended future sections include:

These are proposed URL structures and should not be treated as already implemented routes.

16.1 Permanent URLs

Once an article is published, its URL should remain stable wherever reasonably possible.

16.2 URL Changes

If an article URL must change:

Do not rename article files casually after publication.

16.3 Avoid Duplicate Pages

Different discovery routes should generally link to the same article page.

Do not create separate article copies for language, category, or thematic browsing.

17. Navigation Accessibility

The archive must remain usable by readers with different accessibility requirements.

Navigation should support:

For Urdu and other right-to-left content, ensure that mixed-direction links and text labels remain understandable.

Filters and search controls should have meaningful labels and accessible states.

No essential navigation feature should require mouse hover alone.

18. Progressive Implementation Plan

The navigation system should be implemented in stages.

Stage 1 — Existing Core Navigation

Prioritise:

Validate the existing pages before adding new navigation complexity.

Stage 2 — Archive Improvements

Introduce:

Stage 3 — Controlled Classification

After the category and tag metadata has been validated, introduce:

Once contributor metadata is sufficiently reliable, introduce:

Stage 5 — Search and Advanced Discovery

Introduce multilingual search and additional filters after verifying the performance and accuracy of the underlying index.

This staged approach avoids building an elaborate navigation interface on top of incomplete or inconsistent metadata.

19. Technical Implementation Constraints

The existing publication is built on Jekyll and GitHub Pages.

Navigation changes must respect the current architecture.

Before implementing a new feature, verify:

The current _config.yml has an intentionally lightweight configuration, including an empty plugin list.

Do not introduce plugin-dependent functionality without reviewing GitHub Pages compatibility and the publication’s build settings.

A metadata field does not automatically generate an archive page.

Likewise, a tag does not automatically create a working tag index.

Every new navigation feature should be tested against the actual generated website.

20. Performance and Sustainability

The navigation system should remain lightweight.

Prefer:

Avoid unnecessary animation, excessive interface complexity, and features that provide little value to readers.

The navigation architecture should remain maintainable by someone familiar with ordinary Markdown, YAML, Liquid, HTML, CSS, and JavaScript.

21. Navigation Quality Checklist

Before introducing or modifying a navigation feature, review:

Information architecture

Content accuracy

Technical correctness

Accessibility

Performance

22. Future Development

The archive may eventually support additional discovery dimensions.

Potential developments include:

These features should be introduced only when the archive contains sufficient verified material to support them.

The publication should avoid presenting empty or superficial classification systems simply to appear comprehensive.

23. Relationship with Other Documentation

This specification should be maintained alongside:

Changes to metadata or navigation should be reflected in the relevant technical templates and documentation.


Verse & Variable
A line of verse. A line of inquiry.
لفظ سے لہر تک — Lafz se Lehar tak