Give the fork's README its own identity

Open Beginner friendly
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
css
Domain
documentation

Research direction

Start with the fork's README and inspect custom.css plus the sync and deploy scripts to identify the instance-specific details that must remain visible. Update the README so it explains the live URL, R2 media, CSS overrides, and scripts, and verify that an upstream merge will not replace those instance notes with template documentation.

Written by the indexing model from the issue text.

Description

catalogue-artifact still carries the template's README verbatim. Replace or preface it with what this instance is (live URL, R2 media, custom.css overrides, sync/deploy scripts) so the upstream merge doesn't keep dragging template docs over instance docs.

Migrated from Linear A-90 · created 2026-07-25 · Backlog · Priority: Low

Dominant language
CSS
Stars
0
Forks
1
No merged PRs in 30d

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.

More from arfct/catalogue

All issues in arfct/catalogue

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.