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

Decide for monospaced text syntax in RST files

Open
#61 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Start by reviewing the repository's RST documentation and the cited Docutils inline-markup reference. Done means the project has a documented, consistent choice between interpreted text, inline literals, and Sphinx code roles, including whether Sphinx-specific behavior is intended.

Written by the indexing model from the issue text.

Description

There are different ways to get monospaced font in docs:

  • :code:`stuff`
  • `stuff`
  • ``stuff``

According to the some docs

  • `stuff` = interpreted text
  • ``stuff`` = inline literal

Usually when I want monospaced text in rst I go for ``stuff``. Is :code:`stuff` going to add some additional functionality/highlighting?

Is :code:`stuff` part of the rst syntax or is it specifi to Sphinx?

Originally posted by @Stannislav in https://github.com/BlueBrain/Atlas-Download-Tools/pull/56#discussion_r691301335

Dominant language
Python
Stars
17
Forks
8
PR merge metrics
No merged PRs in 30d

Getting set up

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 BlueBrain/Atlas-Download-Tools

All issues in BlueBrain/Atlas-Download-Tools

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.