Weekly Publication Workflow

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

1. Purpose

This document establishes the editorial and technical workflow for preparing and publishing weekly editions of Verse & Variable.

Verse & Variable is an independent Indian literary journal focused on Indian literature across languages, traditions, historical periods, and literary forms.

The editor’s wider intellectual interests include Indian and international literature, scientific research, mechanics, philosophy, books, music, cinema, sport, and lived experience. These interests may inform the editorial perspective, but they do not expand the journal’s publication scope or require individual articles to adopt an interdisciplinary approach.

The publication follows a distinctive content structure in which three independent literary explorations are brought together within one weekly collection.

Each article should have its own permanent page, independent editorial identity, original commentary, source attribution, and supporting references, where appropriate.

The weekly collection page should introduce the edition and provide readers with an organised way to explore its three articles.

This workflow aims to ensure that:

The workflow is a quality framework, not a requirement to make every article follow the same interpretative pattern, share a common theme, or establish a connection with another discipline.

This is an editorial workflow specification. It does not claim that the current Jekyll website automatically performs every step described here.

2. The Weekly Publication Structure

Each weekly edition is designed around four connected website pages.

2.1 Article One

The first individual article explores a selected Indian literary expression.

It has its own permanent URL and remains independently accessible.

2.2 Article Two

The second individual article explores another literary expression.

It should have its own literary and interpretative identity rather than merely repeating Article One.

2.3 Article Three

The third individual article completes the weekly selection.

It may introduce another language, literary form, period, voice, or dimension of human experience.

2.4 Weekly Collection Page

The weekly collection page brings the three articles together.

It provides:

The collection page should not replace the individual articles or require them to share a single interpretation.

Weekly Edition | +-- Article 01 — Permanent article page | +-- Article 02 — Permanent article page | +-- Article 03 — Permanent article page | +-- Weekly Collection — Page linking all three articles

3. Editorial Principles

The weekly format should preserve the publication’s underlying editorial philosophy.

3.1 Three Independent Explorations

Each article should make a meaningful literary contribution on its own.

The weekly structure should not force unrelated material into a single narrative.

The individual work, its language, imagery, context, and emotional character should determine the direction of its exploration.

3.2 Indian Literary Scope and Linguistic Diversity

The publication’s archive is focused on Indian literature.

The current archive represents seven principal language traditions:

The selections may explore different languages, periods, literary forms, traditions, and emotional worlds.

Where suitable, the selection may include contrasting literary voices, established works, lesser-known expressions, and different cultural contexts.

Diversity should arise from meaningful editorial choices rather than an arbitrary language quota.

The editor’s broader interest in international literature remains distinct from the journal’s current publication scope.

3.3 Optional Editorial Relationships

The three articles may have an editorial relationship where one genuinely emerges from the selected works.

That relationship may arise through:

A shared theme may provide a useful way to introduce a collection, but it is not mandatory.

The three selections may also be entirely distinct.

3.4 No Forced Connections

The articles should never be linked through artificial thematic, scientific, or philosophical claims merely to make the weekly edition appear uniform.

A scientific connection is not required in any particular article or in the weekly collection as a whole.

Metaphors should not be presented as scientific predictions, and literary expressions should not be made to support technical claims that they do not establish.

3.5 Literature on Its Own Terms

Literary interpretation should begin with the selected work itself.

Its language, imagery, form, context, emotion, ambiguity, and possibilities for interpretation should remain central.

Scientific knowledge or another disciplinary perspective may contribute when a genuine connection emerges and materially deepens the reading.

It should never be imposed as an editorial obligation or used merely as technical decoration.

3.6 Quality Over Schedule

The three-article format is an editorial target, not a reason to publish incomplete or inadequately checked material.

If an edition is not ready, the publication may adjust its schedule rather than compromise its standards.

4. Weekly Edition Identification

Every weekly edition should have a stable identifier.

The established identifier format is:

week-YYYY-NN

Where:

Example:

week-2026-46

Use ISO week numbering consistently when the identifier represents a calendar week.

The editorial date range should also be recorded.

4.1 Week Identifier

The same week_id should be used in:

The identifier must follow the same spelling and format across all associated files.

Do not alternate between week-2026-46 and 2026-W46 for the same edition.

4.2 Article Numbers

Use the following sequence:

Article entry_number
Article One 1
Article Two 2
Article Three 3

These numbers establish an ordering within that weekly edition.

They do not replace the article’s permanent URL or unique identity.

4.3 Stable URLs

Once an article is published, avoid changing its URL without a specific editorial or technical reason.

Where a change is necessary, update relevant internal links and redirects where supported.

5. Weekly Planning

The edition should begin with a clear editorial plan.

5.1 Selection

Identify three prospective literary expressions rooted in Indian literature.

Selection may consider:

The present publication scope is focused on Indian literature, including its diverse languages, historical periods, and literary traditions.

The editor’s wider interests in international literature, science, and other disciplines may inform the editorial perspective but do not create additional publication categories.

5.2 Selection Diversity

Where suitable, the selection may include different literary traditions, languages, periods, or forms.

However, diversity should arise from meaningful editorial choices rather than an arbitrary language quota or predetermined distribution of subjects.

The three selections may be related or entirely distinct.

5.3 Optional Editorial Context

The editor may identify a shared idea, emotional question, philosophical concern, literary contrast, or cultural relationship when one genuinely emerges from the selected works.

There is no requirement to allocate articles between scientific and non-scientific subjects.

There is also no requirement that all three selections address the same theme.

A weekly collection should represent the actual character of its three articles rather than manufacture a connection among them.

5.4 Preliminary Rights Assessment

Before investing substantial effort, identify whether the proposed literary or visual material may involve:

Avoid building an article around material whose intended use cannot be established responsibly.

5.5 Weekly Planning Record

Prepare an internal planning record.

Field Description
Week ID Unique weekly identifier
Working title Proposed edition title
Date range Intended publication period
Article One Proposed literary expression
Article Two Proposed literary expression
Article Three Proposed literary expression
Shared theme Optional editorial connection
Primary languages Languages represented
Editorial considerations Relevant literary or contextual matters
Source status Initial research assessment
Rights status Preliminary assessment
Optional contextual research Only where relevant
Editorial status Planning stage
Responsible editor Responsible person

6. Article Preparation

Each individual article should be prepared independently using the relevant publication template.

6.1 Article Template

Use ARTICLE_TEMPLATE.md as the primary article preparation reference.

External contributors may use SUBMISSION_TEMPLATE.md.

6.2 Article Structure

A standard literary exploration should include, as appropriate:

  1. Original literary expression or a properly limited quotation.
  2. Appropriate transliteration or pronunciation guidance.
  3. English translation.
  4. Accurate attribution.
  5. Original editorial reflection.
  6. Supporting references and contextual notes.
  7. Relevant disclosures and supplementary material.

The editorial reflection should contain no more than four concise English prose paragraphs.

Fewer paragraphs are entirely acceptable.

There is no mandatory paragraph-by-paragraph formula and no paragraph reserved for interdisciplinary or scientific discussion.

The reflection should develop naturally from the literary work, following its imagery, emotional movement, language, context, and possibilities for interpretation.

Do not expand a reflection merely to reach a paragraph count.

6.3 Article Independence

Each article must be understandable without requiring the reader to visit the other two articles.

The weekly collection may provide additional context but should not contain information essential to understanding an individual article.

6.4 Originality

Each article should have its own clear interpretative contribution.

Avoid preparing three superficially different articles that repeat the same commentary with minor changes.

6.5 Article Drafting Record

For each article, record:

7. Source Verification

Source verification should begin during preparation rather than being postponed until publication.

7.1 Literary Sources

Check original texts, editions, author attribution, and variant readings.

Where possible, consult the original or an authoritative edition.

7.2 Linguistic Sources

Verify important vocabulary, idioms, grammatical relationships, pronunciation, regional usage, and transliteration choices.

Respect dialectal and regional distinctions rather than automatically replacing them with standardised forms.

7.3 Translation Sources

Identify the original translator or prepare a clearly identified new translation.

Check that the translation reflects the original meaning.

Distinguish literal, interpretative, literary, adapted, and machine-assisted renderings where relevant.

7.4 Historical and Cultural Sources

Verify important dates, events, names, and documentary claims.

Distinguish established historical information from later interpretation or contested accounts.

7.5 Scientific Sources

Where an article contains substantive scientific claims, check relevant research references, theoretical claims, mathematical formulations, and methodological explanations.

Scientific sources are not required for literary reflections that make no scientific assertions.

Do not introduce technical references merely to create an appearance of interdisciplinary research.

7.6 Source Register

Maintain a source register for substantial articles using SOURCE_REGISTER.md.

Do not cite sources that have not been identified or verified sufficiently for the claims being made.

8. Rights and Ethical Assessment

Every article should undergo the relevant rights and ethical checks.

Identify third-party literary material, translations, figures, images, recordings, datasets, and other protected resources.

8.2 Permissions

Obtain permissions where necessary and document the applicable legal basis for use.

Attribution alone should not be treated as automatic permission to reproduce copyrighted material.

8.3 Ethical Considerations

Consider privacy, consent, cultural sensitivity, confidentiality, participant protection, and potential harm.

8.4 Interviews

Where interview material is used, follow the interview and oral-history protocol.

8.5 Registers

Update the relevant internal records where applicable:

8.6 Unresolved Issues

Do not publish material with a serious unresolved rights, privacy, consent, or safety concern.

9. Specialist Review, Where Needed

Where an article contains substantive technical, historical, linguistic, or other specialist claims, consider whether specialist consultation is appropriate.

Such consultation is not a mandatory stage for every literary exploration.

9.1 Scope

Identify the precise claims requiring assessment.

Do not ask a reviewer to certify material outside their expertise.

9.2 Relevant Expertise

Different aspects of an article may require different expertise.

For example:

9.3 Review Records

Record significant feedback and the editorial response where appropriate.

9.4 Review Disclosure

Describe specialist feedback accurately.

Do not represent informal consultation as formal journal peer review.

10. Editing and Revision

Each article should pass through an editorial revision stage.

10.1 Structural Editing

Examine the organisation, sequence, clarity, and coherence of the article.

10.2 Literary Editing

Improve readability while preserving the meaning and character of the original work.

Do not standardise distinctive language, dialect, imagery, or literary expression unnecessarily.

10.3 Scientific Editing

Where scientific claims occur, check terminology, qualifications, mathematical explanations, and unsupported technical statements.

Scientific editing is unnecessary when an article contains no substantive scientific discussion.

10.4 Language Editing

Check grammar, spelling, punctuation, and consistency.

Preserve the conventions appropriate to the language and script being presented.

10.5 Translation Editing

Check the original text against the translation.

Review important ambiguities and explain material interpretative choices where necessary.

10.6 Revision History

Record substantial revisions.

Use stable article filenames and appropriate version-control history.

10.7 Final Article Decision

Complete the relevant editorial decision record using EDITORIAL_DECISION_RECORD.md.

11. Weekly Collection Preparation

Once the three articles have reached an appropriate editorial stage, prepare the weekly collection page.

The collection page should represent the edition as a whole without duplicating all three articles.

11.1 Weekly Title

Use a meaningful title that reflects the character of the selection or a genuine editorial theme, where one exists.

The title need not force all three articles into a single subject.

A numbered title such as Week 46 — Literary Explorations is entirely appropriate when the selections do not share a common theme.

Avoid misleading or exaggerated titles.

11.2 Introduction

Prepare a short introduction describing:

The introduction should not claim that all three articles share a connection that does not exist.

The three selections may simply be introduced as distinct works, each deserving its own reading.

11.3 Article Cards

Each article should be represented with:

11.4 Sequence

Display the articles in the intended editorial sequence.

The sequence should remain consistent with their entry_number values.

11.5 Independent URLs

The weekly collection should link to each individual article page.

Do not rely on a single weekly page containing all article text as a substitute for the permanent article pages.

11.6 Collection Independence

The weekly collection should remain useful even if one article is later corrected, updated, or withdrawn.

If an article becomes unavailable, update the collection page appropriately.

11.7 Optional Editorial Note

A short editorial perspective may be included when it genuinely adds context or insight.

It may discuss the relationship between the selections, their differences, or the particular reason for bringing them together.

It may also be omitted entirely.

There is no requirement to provide a concluding synthesis or a scientific or interdisciplinary interpretation of the weekly collection.

12. Weekly Metadata Coordination

The metadata of all four pages should be checked together.

12.1 Article Metadata

Each article should have the correct:

Any additional field, including permalink, should be used only when its purpose and implementation are established.

12.2 Weekly Metadata

The weekly collection should have:

12.3 Shared Identifier

All three individual article pages must use the same weekly identifier as the collection page.

For example:

week_id: "week-2026-46"

This format must remain consistent with ARTICLE_METADATA_REFERENCE.md and WEEKLY_COLLECTION_TEMPLATE.md.

12.4 Article Ordering

Use the intended ordering:

entry_number: 1

entry_number: 2

entry_number: 3

12.5 Layout Compatibility

Before publication, verify the actual fields consumed by _layouts/entry.html and _layouts/week.html.

A metadata field written in frontmatter is not necessarily displayed automatically.

12.6 Language Configuration

Check that language identifiers match _data/languages.yml.

Do not invent new identifiers without updating the language configuration and relevant site functionality.

12.7 Optional Scientific Metadata

Scientific terminology should be included in article metadata only when the article genuinely contains substantive scientific discussion.

Do not add scientific keywords to an entry simply because the editor’s research interests include those subjects.

The editor’s broader research identity should remain represented in the appropriate author profile, biography, structured data, and research-related pages.

The publication uses the Jekyll collections configured in _config.yml.

Individual article files should be stored in the configured _entries collection directory, and weekly collection files in the configured _weeks collection directory.

A recommended conceptual structure is:

_entries/
  2026-11-09-literary-exploration-one.md
  2026-11-09-literary-exploration-two.md
  2026-11-09-literary-exploration-three.md

_weeks/
  week-2026-46.md

The exact filenames should be adapted to the repository’s existing naming conventions.

The permanent URL structure should follow the configured collection permalinks rather than being inferred from filenames alone.

13.1 Article Files

Each article should contain valid frontmatter and the full article content.

13.2 Weekly File

The weekly file should contain the collection introduction and the metadata needed by _layouts/week.html.

13.3 Supporting Assets

Images and other supporting files should be stored under the repository’s established asset structure.

Do not commit confidential interview records, permission correspondence, private consent documents, or sensitive research material to public directories.

14. Example Weekly Metadata

The following examples illustrate the intended relationship between one weekly collection and its three articles.

They must be adapted to the actual templates and fields supported by the repository.

The example uses the established identifier week-2026-46.

14.1 Weekly Collection Example

---
layout: week
title: "Week 46 — Literary Explorations"
description: "Three independent literary explorations across different voices and expressions."
week_id: "week-2026-46"
date: 2026-11-09
---

14.2 Article One Example

---
layout: entry
title: "A Literary Exploration of [Work One]"
description: "A reflection on an Indian literary expression."
date: 2026-11-09
week_id: "week-2026-46"
entry_number: 1
language_id: "urdu"
language_code: "ur"
author_name: "[Verified original author]"
literary_form: "[Verified literary form]"
---

14.3 Article Two Example

---
layout: entry
title: "A Literary Exploration of [Work Two]"
description: "An exploration of a distinct literary expression."
date: 2026-11-10
week_id: "week-2026-46"
entry_number: 2
language_id: "marathi"
language_code: "mr"
author_name: "[Verified original author]"
literary_form: "[Verified literary form]"
---

14.4 Article Three Example

---
layout: entry
title: "A Literary Exploration of [Work Three]"
description: "A reflection on another literary voice and perspective."
date: 2026-11-11
week_id: "week-2026-46"
entry_number: 3
language_id: "hindi"
language_code: "hi"
author_name: "[Verified original author]"
literary_form: "[Verified literary form]"
---

These are illustrative values, not actual publication records.

The three example languages are included only to demonstrate metadata usage. They do not establish a required distribution of languages or subjects within a weekly edition.

Confirm that each language identifier exists in _data/languages.yml and that the required fields are supported by the relevant layout.

15. Pre-Publication Quality Control

Each article must pass the relevant requirements in PUBLICATION_CHECKLIST.md.

15.1 Individual Article Checks

For each of the three articles:

15.2 Weekly Collection Checks

15.3 Edition-Wide Checks

16. Weekly Publication Decision

The editor should make a decision about the complete edition as well as the individual articles.

Possible outcomes include:

Decision Meaning
Ready All three articles and the collection page are ready
Ready with minor changes Limited changes remain
Partial edition Fewer than three articles are ready, and separate publication is intentionally authorised
Delayed One or more substantial issues remain
On hold A critical editorial, rights, ethical, or technical concern remains
Withdrawn The proposed edition is no longer proceeding

16.1 Complete Edition

The normal intended format is three independent article pages and one weekly collection page.

16.2 Partial Publication

If fewer than three articles are ready, the editor may:

Do not publish incomplete material simply to meet a calendar deadline.

16.3 Delayed Edition

A delayed edition should be handled transparently.

Avoid presenting a revised date as an original publication date.

17. Publication Sequence

Once the edition has been approved, publish the material in a controlled sequence.

Step 1 — Finalise Article One

Step 2 — Finalise Article Two

Step 3 — Finalise Article Three

Step 4 — Finalise Weekly Collection

Step 5 — Commit the Edition

Commit the new files and supporting public assets to the repository.

Use a descriptive commit message.

Example:

Publish 2026 Week 46 literary explorations

Step 6 — Verify Deployment

Check the GitHub Pages deployment status.

Do not assume that a successful Git commit necessarily means that the live website has updated correctly.

Step 7 — Inspect All Four Pages

Verify:

Step 8 — Record Publication

Record publication dates, final URLs, and the edition’s status in the appropriate internal record.

18. Publication Timing and Schedule

The publication may aim for one weekly edition.

However, a weekly format should not create unnecessary pressure to publish incomplete material.

18.1 Flexible Scheduling

The publication date may be adjusted according to:

18.2 Date Accuracy

Distinguish between:

Do not use a scheduled date as though it were an actual publication date.

18.3 Time Zone

The website configuration currently specifies:

Asia/Kolkata

Use this configured timezone consistently for publication-date handling unless the site configuration is deliberately changed.

18.4 Missed Weeks

If an edition is not ready, record the delay internally where useful.

Do not fabricate a publication date or backdate an article to create the appearance of a continuous archive.

19. Revision and Correction of a Weekly Edition

An article may require revision after the weekly collection has been published.

19.1 Individual Article Revision

An individual article may be corrected or updated without necessarily changing the entire weekly collection.

19.2 Collection Update

Update the weekly collection when:

19.3 Historical Accuracy

Preserve the original publication date unless there is a legitimate editorial reason to correct it.

A revision date should not be misrepresented as the original publication date.

19.4 Withdrawal

If an article is withdrawn, determine whether the weekly collection should:

The action should follow the relevant correction and takedown policies.

20. Internal Weekly Edition Record

Use the following template for each weekly edition.

Weekly Edition Record

Week ID: [week-YYYY-NN]

Edition title: [Title]

Date range: [Date range]

Planned publication date: [Date]

Actual publication date: [Date]

Responsible editor: [Name]

Article One

Title: [Title]

Filename: [Path]

URL: [URL]

Language: [Language]

Entry number: 1

Editorial status: [Status]

Article Two

Title: [Title]

Filename: [Path]

URL: [URL]

Language: [Language]

Entry number: 2

Editorial status: [Status]

Article Three

Title: [Title]

Filename: [Path]

URL: [URL]

Language: [Language]

Entry number: 3

Editorial status: [Status]

Weekly Collection

Title: [Title]

Filename: [Path]

URL: [URL]

Collection status: [Status]

Edition-Wide Checks

Final edition decision: [Decision]

Commit reference: [Git commit hash]

Additional notes: [Notes]

21. Weekly Workflow Summary

The complete process may be represented as follows.

Editorial planning
       |
       v
Select three Indian literary expressions
       |
       v
Preliminary source and rights assessment
       |
       v
Prepare three independent drafts
       |
       v
Literary, linguistic and cultural research
       |
       v
Translation, attribution and ethical checks
       |
       v
Optional specialist consultation or scientific research
       |
       v
Editorial revision
       |
       v
Complete individual article decisions
       |
       v
Prepare weekly collection page
       |
       v
Check shared metadata and links
       |
       v
Complete publication checklist
       |
       v
Commit repository changes
       |
       v
Verify GitHub Pages deployment
       |
       v
Inspect all four live pages
       |
       v
Record publication and maintain archive

The optional consultation stage may be omitted entirely when it is not relevant to the articles.

22. Weekly Edition Final Checklist

Before declaring an edition complete, confirm:

Editorial

Research and Verification

Rights and Ethics

Website

Publication Record

23. Relationship with Other Publication Documentation

This workflow should be read alongside:

24. Continuing Commitment

The weekly structure of Verse & Variable is intended to create a growing archive of independent literary explorations rooted in Indian literature.

Each article should stand on its own. Each weekly collection should bring its articles together without forcing their differences into an artificial narrative.

The publication should value the integrity of individual contributions above the pressure of a recurring schedule.

Three carefully considered literary explorations are more valuable than three articles published merely to complete a weekly count.

The long-term objective is an archive that grows through literary depth, linguistic diversity, cultural sensitivity, intellectual curiosity, and responsible editorial practice.

Three independent literary explorations. One weekly collection. An expanding archive of Indian literary voices and human experience.


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