Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Guide for Unified Succession Model

Open
#188 7 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
clojure
Domain
documentation

Research direction

Start with the linked Stack Overflow answer and inspect the existing site pages that explain Clojure's reference types. Add a guide covering the Unified Succession Model and consistently use “succession” rather than “update”; done means the concept is documented on the site alongside the reference-type material.

Written by the indexing model from the issue text.

Description

content help wanted

We talk about Clojure's Unified Succession Model when explaining the various reference types, but it is not mentioned on the site. This SO answer might be a good starting point.

At this point I strongly prefer "succession" over "update". "Succession" is more precise, and not polluted by the "in place" connotations of "update".

Dominant language
HTML
Stars
259
Forks
275
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 clojure/clojure-site

All issues in clojure/clojure-site

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.