openlibhums / openlibhums/janeway

Back office page titles and h1 headings

Open
#4,503 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

a11y new feature
Dominant language
Python
Stars
238
Forks
97
Avg merge
9d 1h
Merged PRs (30d)
8

Description

User story

As a user of the Janeway back office, I would like a consistent name for the pages that I'm visiting. Right now, not all the information is available in the places I'd like, in the structure I need for it to be accessible.

  • I can see or hear the name of the page in the browser tab, which is good
    image

  • I can't see or hear the name of the site in the browser tab

  • I can navigate to an h1 with the page title
    image

  • I am confused by another h1 with the site name
    image

Proposed solution

  • Agree on a standard format for the browser tab (HTML title) that includes both pieces of info, like Page name | Site name.
  • Check extensions on the base template for usage of the existing title block.
  • Implement a contextual title, accounting for press, journal, and repository sites, via a standard Django template element on the base template (see https://github.com/openlibhums/janeway/pull/4491 for an example of how we might do it).
  • #4816
  • Check usage of title-section to make sure we are not creating pages with an empty h1.

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.

Research direction

Start with the base template and its existing title block, then review extensions and title-section usages across press, journal, and repository sites; use PR #4491 as the referenced example. Confirm the standard HTML title format and ensure page headings are not empty or duplicated, while checking the relationship to issue #4816.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
accessibility, frontend, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.