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

Marginalia Annotation

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
html
Domain
content, web-dev

Research direction

Begin by reading issue #1, which this issue references for comparison with layers. No files, tests, or entry points are named, and the four annotation categories do not define a concrete completion test; clarify the annotation model and scope before implementation.

Written by the indexing model from the issue text.

Description

proposed feature

From @cubap on October 16, 2015 5:32

Several types of interest areas may be important to capture, but may not be part of a cohesive enough to be part of a layer as in #1.

  1. Dry glosses and other comments or decoration between or near lines that relates to a specific part of the text. This may have a selector on the canvas for its content and target, as well as both transcribed content and commentary as to its impact or purpose.
  2. Written comments in margins that edit the main text in some way and may point specifically to text, canvas regions, or even out to other locations in the manuscript.
  3. Doodles and other graphical features that will be described, but not transcribed.
  4. Codicological features like catchwords may be noted and tied to other canvases.

Copied from original issue: cubap/TPEN3#2

Dominant language
HTML
Stars
5
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 CenterForDigitalHumanities/TPEN3

All issues in CenterForDigitalHumanities/TPEN3

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.