Swift.org Website is Now Open Source

Tom Doron is a member of the Swift Core Team and the Swift Server Work Group. He manages a team working on server-side Swift libraries at Apple.

The Swift.org site has long served as the hub where developers come together to work on the open source Swift compiler, libraries, and tools. Today, we are happy to announce that the Swift.org website itself is also an open source project, ready for community contributions. With this move, the website is also expanding its mandate to better support the entire community of Swift users, not just contributors.

To aid in this effort, a new Swift website work group (SWWG) will be formed to navigate the evolution of the website. It is exciting to imagine what the future of our site can become with the whole community pitching in. So let’s dive into what this all means.

Goals for the Website

Swift.org is a collection of disparate content — everything from nightly build downloads, to community forums, documentation, and also evolution proposals for the language itself. As an open source project, the website goals have grown. The site should:

Swift Website Work Group (SWWG)

The Swift Website Work Group (SWWG) will have the charter to work across any tools and platforms necessary to create a truly great web experience that achieves the goals stated above. This includes work on the main website, as well as the forums, and documentation.

Anyone is welcome to contribute to the Swift.org website. All they need to do is create a pull request with a fix or improvement to the repository for the site. The maintenance of the project, and approvals for community PRs, will be handled by the SWWG, composed of people from the broad Swift community. There is also a forum for folks to talk about the project.

Today, we are opening up nominations for community members who would like to serve on the Swift Website Work Group (SWWG). The goal is to get between five and ten volunteers to manage the day-to-day review of PRs from the community, as well as direct strategy for the site.

Individuals who would like to join the workgroup should apply by contacting the @swift-website-workgroup via the Swift.org forums with your reasons for interest, and special skills that will help you serve in this capacity. Members of the Core Team will review applications, and may have follow-up questions before voting for the initial cadre of team members.

Diversity in Swift

Much like other work groups at Swift.org, the Diversity in Swift team will work with the SWWG to ensure the principles and interests of the entire Swift community are always considered. You can read more about the Swift website work group (SWWG) charter here.

Types of Content

The Swift.org website is open for community contribution, with a public governance process. However, some content hosted on Swift.org follows a different publication process and isn’t open for the same kinds of contribution. For instance, the text of The Swift Programming Language book is available under a Creative Commons license, but the project itself isn’t open source yet. We intend to adopt Swift-DocC for this content, replacing the book’s current custom publication toolchain to release TSPL as an open-source project.

The blog occasionally hosts posts — such as announcements — with content that cannot be openly shared before publication. If you have a proposed blog post you’d like to see published, we ask that you email your draft post to @swift-website-workgroup using the Swift forums.

By their nature, blog posts are relevant when they are published and become outdated over time. Pull requests to fix minor issues like typos are welcome, regardless of the post’s age. Significant changes to blog posts after publication should be infrequent — for example, it’s unnecessary to revise an old blog post when APIs or best practices change.

Repository on GitHub

The Swift.org website is now publicly available on GitHub. The website repository will also use GitHub Issues for issue tracking. We hope this will make it even easier for people to participate, and be a testbed for the rest of the Swift project to move to Issues in the future.

Next Steps

To read up on the full details of the SWWG, check out:

One of the first tasks for the work group will be to determine the future technology stack upon which to build the site. For example, documentation-style pages could move to Swift-DocC. And it may be good to use a Swift-based tool to replace Jekyll. Other efforts may include designing new “Getting Started” content to make the site more welcoming.

If you would like to join the work group, please email your interest soon. The goal is to have the first cadre of members set by the end of April 2022.