First rough draft

Author: finestructure

Resources/Blog/Posts/introducing-custom-package-collections.md

@@ -0,0 +1,42 @@
+We first launched support for package collections ahead of WWDC 2021 and they are a convenient way to add packages to an Xcode project.
+
+We generate a package collection for all packages by an author or organisation. For example, you can copy a link for the package collection for all of Apple’s packages via [Apple’s author page](https://swiftpackageindex.com/apple) and add it to Xcode's package collections.
+
+Since launching the feature we have been asked if we could support more curated collections that span multiple authors and today we are adding the ability to create package collections for key community efforts.
+
+The way this works is quite similar to adding packages to the Swift Package Index. Instead of adding a package to [packages.json](), you add a whole package list (whose contents _you_ maintain) to [custom-package-collections.json]().
+
+Here’s what this looks like, taking the Swift Server Workgroup Graduated packages as an example:
+
+```
+{
+    "key": "sswg-graduated",
+    "name": "SSWG Graduated",
+    "description": "SSWG packages that are in 'graduated' state",
+    "url": "https://raw.githubusercontent.com/finestructure/sswg-package-lists/refs/heads/main/graduated.json"
+}
+```
+
+The `key` field essentially determines the URL at which the package collection is available on the Swift Package Index:
+
+    [https://swiftpackageindex.com/collections/sswg-graduated](https://swiftpackageindex.com/collections/sswg-graduated)
+
+The `name` is its display name on the collections page as well as on the package page where we should a package’s membership to package collections:
+
+TODO: image package page (needs new badge icon).
+
+The `description` field brielfly explains the motivation for this custom collection. It serves informational purposes and is not displayed.
+
+TODO: describe `badge` attribute.
+
+We will be considering additions to the custom collections list on a case by case basis for package lists that benefit the Swift package ecosystem.
+
+Such lists should be goverened by a group or organisation active in the Swift open source community and have appeal for a significant part of the Swift ecosystem.
+
+The intial set of SSWG collections give an example of these requirements:
+
+- The content of the lists is managed by the Swift Server Workgroup.
+- While mainly geared towards server-side development, many packages like for example `swift-crypto` are relevant even for developers not working with server-side Swift.
+- Making the maturity levels of these packages visible on the Swift Package Index helps developers find quality packages for their needs.
+
+Please [get in touch](https://discord.gg/vQRb6KkYRw) if you have questions, would like to propose a new custom collection, or open an issue or pull request on the [PackageList repository](https://github.com/SwiftPackageIndex/PackageList/) for discussion.

Resources/Blog/posts.yml

@@ -193,3 +193,8 @@
   summary: We are thrilled to announce that Amazon is joining Apple as a supporter of the Swift Package Index by providing infrastructure support.
   published_at: 2024-10-28
   published: true
+- slug: introducing-custom-package-collections
+  title: Introducing custom package collections
+  summary: We've added support for custom package collections to allow well-known community efforts to present package collections.
+  published_at: 2024-11-22
+  published: false