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

docs.fsharp.org?

Open
#995 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
github, markdown
Domain
documentation

Research direction

Start by reviewing the proposed fsharp-docs repository structure, the existing fslang-spec, fsharp-core-docs, and fsharp-compiler-docs repositories, and the current fsharp.github.io/fsharp-core-docs search experience. Check the CNAME, existing links, and redirect requirements described in the issue. Done would require an agreed scope and plan for the consolidated docs site.

Written by the indexing model from the issue text.

Description

I've spoken with @ReedCopsey and if we like he can make the DNS changes needed to activate https://docs.fsharp.org

However we'd need to decide what docs can really go there. I'll write some notes about what I think makes sense, if someone wants to tackle this

The main docs for F# are the ones listed here: https://learn.microsoft.com/dotnet/fsharp/ and whose source is part of the .NET docs (https://github.com/dotnet/docs). Although relying on the .NET docs to host and publish the F# docs is a bit annoying (e.g. the Microsoft branding and advertising is frustrating), it's not realistic for the F# community to host all those docs instead. The real question is about the important docs that are "external" to the .NET docs and are in this org,

The .NET docs site links to these. Do we want to move the first two to docs.fsharp.org URL?

To do this we would need a single repo https://github.com/fsharp/fsharp-docs that would contain the CNAME for the DNS entry and would combine the material in

The front page docs.fsharp.org would minimally need a search experience, see search on https://fsharp.github.io/fsharp-core-docs/ for example. Other improvements would have to come my improving the tools fsdocs (https://fsprojects.github.io/FSharp.Formatting/) which would continue to be used to generate at least the core docs.

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.