msys2 / msys2/msys2.github.io

website: code blocks

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

Nobody has claimed this yet.

Dominant language
CSS
Stars
3.3k
Forks
446
Avg merge
2h 16m
Merged PRs (30d)
1

Description

See https://www.msys2.org/ Under some step of Installation. there were no linkable headings maybe there's no markdown - 1.

When you copy the code the first character should be removed. The client/user side solution is to inject code into the website but that may/may not work. - 2

It would be best that I myself make the changes as my preferences have been satisfied. And I would make them but I can't find the edit button/link in the two places where it usually/normally/conventionally is placed. - 3

After some searching I only found this issue - https://github.com/msys2/msys2.github.io/issues/6#issue-95562703
SourceForge works fine now if you use UBlock Origin

Note - I know Markdown is used for the site but the expected result does not match the real website, see 1. Wrt 3 it is always better to use a link in terms of web UI and UX with the benefit of reduced maintenance burden. 3 -> link can be improved if there is a image icon but then you need two good visible icons.

PS - If I don't respond in time do ping me.

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.

Research direction

Start by reviewing the Installation pages on msys2.org and the related issue at msys2.github.io/issues/6, then identify how Markdown code blocks and headings are rendered. Check whether the requested copy behavior, linkable headings, and edit link can be addressed within the site. Done means the intended code-copy and navigation behavior is documented and verified on the affected pages.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
documentation, web-dev
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.