What question did this study set out to answer?

This work aims to document the Leather & Steel design system that enforces visual consistency across various publishing outputs.

April 27, 2026Open Access

Leather & Steel: A Visual Design System for Independent Publishing at Scale

Key Points

This work aims to document the Leather & Steel design system that enforces visual consistency across various publishing outputs.
Developed a design system using JSON specifications that includes color tokens, typography, and formatting rules.
Released five supplementary components for chart, diagram, and cover generation while ensuring compliance with visual guidelines.
Utilized Python modules to implement design standards for over 558 books and 30 papers.
Visual identity remained constant across 558+ books and 30+ papers, receiving positive feedback for consistency.
The system survived multiple redesigns without needing updates to its core token file, demonstrating robust architecture.
Utilized warm-earth-toned palette, though limitations exist in extending to other color themes.

Abstract

Abstract This paper documents the Leather the fallback solid-color cover is functional but not on-brand. Reproducibility All five components are MIT-licensed Python modules. tokens.json is CC BY 4.0 and may be forked or extended. Companion Papers This deposit is one of ten flagship records in the Practitioner Publishing Stack series. Each flagship is a methodology paper plus the relevant working source as supplementary material. The series: I. Markdown to multi-format compile pipeline (.docx, .pdf, .epub) with consistent typography. (slug: f01-pub-compile-stack, domain: PUB) II. Detection and removal of AI writing signatures from manuscripts before publication. (slug: f02-aiq-zero-signature-pipeline, domain: AIQ) III. End-to-end pipeline from literature search to Zenodo-published, DOI-indexed academic artifact. (slug: f03-res-research-to-doi, domain: RES) IV. Six python-docx utilities for format normalization, heading conversion, and AI-signature cleanup. (slug: f04-doc-production-pipeline, domain: DOC) V. (this paper) — Visual design system: color tokens, typography, charts, diagrams, and AI cover composition. VI. Markdown-driven template engine producing branded spreadsheets and PDF checklists for direct sale. (slug: f06-tpl-spec-to-sellable, domain: TPL) VII. Per-channel specification workflow for distribution across seven publishing platforms. (slug: f07-dst-multi-platform-distribution, domain: DST) VIII. Course-materials pipeline: markdown syllabus to branded PDF and per-session DOCX. (slug: f08-edu-course-materials, domain: EDU) IX. Seven-phase book production methodology with hard quality gates and 18-day average cycle time. (slug: f09-meta-book-lifecycle, domain: META) X. Architectural overview of an independent publishing operation that produced 558+ titles. (slug: f10-meta-practitioner-publishing-stack, domain: META) Author Ibrahim Anwar (Hibranwar) ORCID: 0009-0006-0425-4923 Wikidata: Q138856145 Web: hibranwar.com Affiliation: PT Hibrkraft Kreasi Indonesia (Cileungsi, Bogor, Indonesia) License The methodology paper, configuration, and sample data are released under CC BY 4.0. The Python source code in supplementary.zip is released under the MIT License. Citation If you use this work, please cite via the DOI minted on this Zenodo record. A machine-readable CITATION.cff ships in the deposit. About the Practitioner Publishing Stack The Practitioner Publishing Stack documents an independent publishing operation by Ibrahim Anwar that produced 558+ titles across nonfiction books, public-domain translations, academic papers, and digital templates, distributed across seven platforms, with a single human as the bottleneck. Average end-to-end cycle time per title: 18 days. Operator headcount: 1.

Read Full Paperexternally

Bookmark

View Full Paper

Cite This Study

Ibrahim Anwar (Sat,) studied this question.

synapsesocial.com/papers/69eefd9bfede9185760d45e4 https://doi.org/https://doi.org/10.5281/zenodo.19766002

Bookmark

View Full Paper