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

Convert the specs to Markdown?

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
markdown, tex
Domain
documentation

Research direction

Start by locating the specification sources in the repository and reviewing how they are currently written and published. Determine the scope of converting them to Markdown; done means the specs use the collaboration-friendly format and remain complete and reviewable.

Written by the indexing model from the issue text.

Description

language-spec

It would be much easier to contribute to the spec and review changes if it had a more collaboration-friendly format.

Dominant language
TeX
Stars
311
Forks
291
PR merge metrics
No merged PRs in 30d

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.

More from fsharp/fsharp.org

All issues in fsharp/fsharp.org

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.