life-itself / life-itself/secondrenaissance

Add HTML/markdown versions of papers on site

Open
#387 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
11
Forks
19
Avg merge
1m
Merged PRs (30d)
1

Description

## Motivation

Papers are currently linked to PDFs (Google Drive). We should add dedicated web pages for each paper with the markdown/HTML content rendered on-site.

**Benefits:**
- Better reading experience — mobile-friendly, accessible, no PDF viewer required
- SEO — content is indexed by search engines rather than locked in an opaque PDF
- Easy deep-linking to specific sections
- Consistent styling with the rest of the site

**Tradeoffs to consider:**
- Formatting-heavy PDFs (tables, figures, sidebars) may need care when converting
- Maintenance: paper updates need to be applied to both the web version and the PDF

## Approach

We already have the markdown source for most papers. Pattern would follow `/papers/tech` (paper 5), which already has a dedicated page. Each paper gets a route like `/papers/1` or `/papers/what-and-why`, rendered with the site layout. Keep the Drive PDF link as a "download / print version" option alongside.

## Papers

- [ ] Paper 1 — What & Why of a Second Renaissance
- [ ] Paper 2 — How of a Second Renaissance
- [ ] Paper 3 — From Polycrisis to Metacrisis
- [ ] Paper 4 — Developmental Spaces
- [ ] Paper 5 — In Tech We Trust (already done ✓)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining the existing /papers/tech page for Paper 5 and the markdown sources for Papers 1–4. Follow that page’s site-layout and route pattern, keeping each paper’s Google Drive PDF as a download or print option. Done means Papers 1–4 have readable on-site HTML/markdown pages with appropriate routes and the listed papers are updated accordingly.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, markdown
Domain
content, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.