A few months ago, the Board decided to start a re-design of the fsharp.org website. fsharp.org is one of the first sites newcomers looking for F# resources will find, and it is therefore crucial to make a good first impression.
Over the years, fsharp.org has grown organically, which resulted in some issues: finding resources is difficult, the content is overwhelming, joining is confusing, it is hard for the Community to contribute fixes, and the overall message is not clear.
While many people visit fsharp.org, we believe our main audience is:
- developers who are F# curious and want to get started,
- C-level managers (CTOs) evaluating F# adoption.
1 improve overall looks,
2 improve navigation and content organization,
3 improve maintainability,
4 improve registration/login experience,
5 incorporate a new version of TryFSharp (F# editor in the browser).
The re-design effort is happening, along 2 directions. A design firm has been working on 1 and 2, and a separate effort is taking place for the back-end part (3, 4, 5).
What you will find below is the current proposal from the design firm. The main changes are:
- organization in 3 sections (F#/main, Community, Foundation)
- simplification of navigation, with less content, better maintained and easier to find,
- focus on a few case studies / testimonials on the front page
- TryFSharp / live editor on the front page
The documents attached show:
- 2 views of the home page, each highlighting a different case study / testimonial
- the navigation menu for the 3 sections (F#/main, Community, Foundation).
Main page, version 1
Main page, version 2
We think this direction is a clear overall improvement over the current situation.
We would love to hear your feedback, to make sure we get this right!
One of the reasons we decided to work with a design firm is that, well, while most of us are software engineers, their specific expertise is on design and user experience. In that frame, we are particularly interested in feedback that helps them understand what we want to convey, and what might be missing, and less how to specifically fix it.
What we specifically would like feedback on:
- index/main page organization
- will it grow well over time?
- look and feel, general impressions
- is there anything missing from the current website?
- color, graphics, …
- does this raise any concerns?
- what would a / your CTO think?
- what would you / your friend think?
What is not in scope:
- we will have some feedback later on around back-end improvements, and the new version of TryFSharp
- the contents of the pages will be fleshed out later
So… let us know what you think, and how we can make this better!