Swift.org website

Swift.org website goals include:

  • Welcome newcomers with friendly information about Swift
  • Help visitors of all skill levels get started developing with Swift
  • Document the language, libraries, and best practices
  • Announce new features, APIs, and tooling improvements
  • Provide a safe, friendly place to interact with fellow Swift developers
  • Promote activities occurring anywhere within the community
  • Support collaboration and evolution in building the Swift ecosystem

Community Participation

Everyone is welcome to contribute to the Swift.org website in the following ways:

  • Submitting pull requests to improve and correct existing content or technical infrastructure.
  • Proposing broad enhancements or large scale changes to the website. Such proposals require consultation with the website workgroup and can be proposed as a public forum post on Swift.org website forum or privately by contacting @swift-website-workgroup on the Swift Forums. Example for such broad changes include:
    • Proposing new topics and content domains, or broad changes to existing ones.
    • Proposing broad changes to how content is organized in the website (information design).
    • Proposing broad changes to how the website looks (UX/UI design).
    • Proposing broad changes to the technical infrastructure that powers the website.
  • Participating in design discussions
  • Asking or answering questions on the forums
  • Reporting or triaging bugs

See CONTRIBUTING.md for additional information about the website’s contribution guidelines.


The website has a small list of maintainers which have write access and are in charge of reviewing and merging pull requests from contributors. The maintainers group consists of a small subset of the Swift core team and the Swift website workgroup members.

The Swift.org website source code consists of several distinct parts:

  1. General content: Markdown, HTML, data files, images and other content.
  2. Blog posts: Source files for blog posts, mostly in markdown form.
  3. Technical infrastructure: Code and scripts for generating the website’s final static content (HTML mostly) from other forms of textual content such as Markdown and HTML files.
  4. Information design, user experience and user interface design: The layout and navigation of the website, including CSS and images used to define the user experience and user interface.

Each one of these areas is governed by a slightly different contribution process that matches their nature.

See Swift.org governance for additional information about the website’s governance.

Website workgroup

The Swift website workgroup is a steering team that helps guide the evolution on the Swift.org website. The Swift website workgroup will:

  • Define a set of processes that govern the contributions to the Swift.org website.
  • Actively guide Swift.org website development and contributions.
  • Define and prioritize Swift.org website related efforts that address the needs of the Swift community.
  • Channel feedback to Swift core team about the needs of the Swift community.

See Swift.org workgroup for additional information about the workgroup.