chor(blog-redesign): Revert updates to disrelated files.

Author: jesseaborden

.prettierignore

@@ -1,2 +1,2 @@
 assets/javascripts/new-javascripts/vendor/
-/posts
+posts/

_data/new-data/get-started/storybook/image-text-row.yml

@@ -1,6 +1,6 @@
 headline: Image Text Row
 image:
-  src: /assets/images/swift-redesign-blog/home_light@2x.jpg
+  src: /assets/images/placeholders/image_placeholder_large@2x.png
   alt: a place holder
 copy:
   headline: Lorem Ipsum

_includes/new-includes/components/card-grid.html

@@ -44,9 +44,11 @@ <h2>{{ include.content.title }}</h2>
       </li>
       {% endfor %}
     </ul>
-    {% endif %} {% if include.content.text %}
+    {% endif %}
+    {% if include.content.text %}
     <p>{{ include.content.text }}</p>
-    {% endif %} {% if include.content.link %}
+    {% endif %}
+    {% if include.content.link %}
     <a href="{{ include.content.link.url }}"
       >{{ include.content.link.text }}
     </a>

_includes/new-includes/components/hero-card.html

@@ -1,8 +1,3 @@
 <div class="hero-card {% if include.stand_alone %} content-wrapper{% endif %}">
-  {% if include.title %}
-  <h3>{{include.title}}</h3>
-  {% endif %} {% if include.image %}<img
-    src="{{ include.image.url}}"
-    alt="{{include.image.alt}}"
-  />{% endif %}
+  <img src="{{ include.image.url}}" alt="{{include.image.alt}}" />
 </div>

_posts/2015-12-03-swift-linux-port.md

@@ -15,60 +15,60 @@ architecture on Linux.
 
 Here are a few highlights of what's working in the port today:
 
-- **Swift without the Objective-C Runtime**: Swift on Linux does not
+* **Swift without the Objective-C Runtime**: Swift on Linux does not
   depend on the Objective-C runtime nor includes it. While Swift was
   designed to interoperate closely with Objective-C when it is present,
   it was also designed to work in environments where the Objective-C
   runtime does not exist.
 
-- **The core Swift Language and [Standard Library]** on Linux shares most of
+* **The core Swift Language and [Standard Library]** on Linux shares most of
   the same implementation and APIs as on Apple platforms. There are some
   slight differences of behavior because of the absence of the
   Objective-C runtime on Linux (noted below).
 
-- **The Glibc Module**: Most of the Linux C standard library is available
+* **The Glibc Module**: Most of the Linux C standard library is available
   through this module similar to the Darwin module on Apple platforms.
   Some headers aren't yet imported into the module, such as tgmath.h.
 
   To try it out, just `import Glibc`.
 
-- **Swift Core Libraries**: The [Core Libraries] provide implementations
+* **Swift Core Libraries**: The [Core Libraries] provide implementations
   of core APIs from Foundation and XCTest to be used on Linux without
   Objective-C . The intention is that these APIs are available in a
   cross-platform manner regardless of whether you are using Swift on
   Apple's platforms or Swift on Linux.
 
-- **LLDB Swift debugging and the REPL**: You can [debug your Swift
+* **LLDB Swift debugging and the REPL**: You can [debug your Swift
   binaries] and [experiment in the REPL] just like you do on macOS.
 
-- **The Swift Package Manager** is a first class citizen as it is on
+* **The Swift Package Manager** is a first class citizen as it is on
   Apple's platforms.
 
 Here are some things that aren't quite working yet or are planned for
 the future:
 
-- **libdispatch**: Part of the Core Libraries, updated Linux support is
+* **libdispatch**: Part of the Core Libraries, updated Linux support is
   in progress. You can follow development on the [libdispatch project on
   GitHub].
 
-- **Some C APIs**: Although this is generally true for all of our
+* **Some C APIs**: Although this is generally true for all of our
   supported platforms, a few constructs in C aren't imported yet into
   Swift. This will cause some APIs to be unavailable, such as those that
   contain varargs / `va_list`. However, in recent months Swift's
   interoperability with C has significantly advanced, gaining support
   for named and anonymous unions, anonymous structs, and bitfields.
 
-- **Some `String` APIs**: The Standard Library's `String` is missing implementations
+* **Some `String` APIs**: The Standard Library's `String` is missing implementations
   of several important APIs because they are currently tied to the
   implementation of `NSString` on Apple's platforms.
 
-- **Runtime Introspection**: When a Swift class on Apple's platforms is
+* **Runtime Introspection**: When a Swift class on Apple's platforms is
   marked `@objc` or subclasses `NSObject` you can use the Objective-C
   runtime to enumerate available methods on an object or call methods
   using selectors. Such capabilities are absent because they depend on
   the Objective-C runtime.
 
-- `Array<T> as? Array<S>`: Some mechanisms, such as casting
+* `Array<T> as? Array<S>`: Some mechanisms, such as casting
   containers with different associated types, currently do not work as
   they relied on bridging mechanisms with Objective-C.
 

_posts/2024-03-25-adwaita-swift.md

@@ -2,21 +2,21 @@
 layout: post
 published: true
 date: 2024-03-25 10:00:00
-title: 'Writing GNOME Apps with Swift'
+title: "Writing GNOME Apps with Swift"
 author: [davidswift]
 category: 'Developer Tools'
 ---
 
 Swift is well-suited for creating user interfaces thanks to the clean syntax, static typing, and special features making code easier to write.
-[Result builders](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/advancedoperators/#Result-Builders), combined with Swift's [closure expression syntax](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/closures/#Closure-Expression-Syntax), can significantly enhance code readability.
+[Result builders](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/advancedoperators/#Result-Builders), combined with Swift's [closure expression syntax](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/closures/#Closure-Expression-Syntax), can significantly enhance code readability. 
 
 [Adwaita for Swift](https://github.com/AparokshaUI/adwaita-swift) leverages these Swift features to provide an intuitive interface for developing applications for the [GNOME](https://www.gnome.org/) platform.
 GNOME is a popular, open source desktop environment for Linux, known for its emphasis on simplicity and accessibility.
 It offers an intuitive user interface, with a vast app ecosystem built using its modern Adwaita design language.
 Explore a collection of great apps under [Apps for GNOME](https://apps.gnome.org).
 
 Let's look at a code example of using Adwaita for Swift.
-The following code snippet defines a _view_, which represents a part of the user interface inside a window.
+The following code snippet defines a _view_, which represents a part of the user interface inside a window. 
 
 ```swift
 struct Counter: View {
@@ -42,22 +42,19 @@ struct Counter: View {
 
 A view can be nested within other views or added as the child of a window.
 
-Its content can be modified from outside that view and is influenced by its position in the view hierarchy.
+Its content can be modified from outside that view and is influenced by its position in the view hierarchy. 
 This makes it easier to compose views to produce different results.
 The screenshot shows one simple possibility.
 
 ![A screenshot of the counter example app.](/assets/images/2024-03-14-adwaita-swift/demo.png){:style="max-width: 100%; height: auto; width: unset; margin: auto auto; display: block;"}
 
 ## Motivation
-
 The primary motivation for this package is to enable the use of Swift when writing GNOME apps, for all the reasons outlined above. But there are a few additional reasons:
 
 ### Declarative
-
-While there are already libadwaita and GTK bindings for numerous modern programming languages, including Rust, Python, and JavaScript, all official bindings follow an _imperative_ coding style.
+While there are already libadwaita and GTK bindings for numerous modern programming languages, including Rust, Python, and JavaScript, all official bindings follow an _imperative_ coding style. 
 This can be verbose and harder to follow than a declarative style as user interfaces are constructed using a series of commands.
 The following Python code serves as an illustration of this.
-
 ```python
 class Counter(Gtk.Box):
 
@@ -89,22 +86,19 @@ class Counter(Gtk.Box):
 This Python code uses the [PyGObject](https://gnome.pages.gitlab.gnome.org/pygobject/) library and produces the same user interface as the Swift code above.
 
 ### Ease of Use
-
 As you can see, Adwaita for Swift is built around _data_.
 For example, changing the variable `count` when pressing one of the buttons in the sample app will automatically update the user interface.
 Traditional bindings require you to call a function on the object holding a widget that should update its content once a value changes.
 
 If you decide to store the value on the disk so that it persists between startups of the app, you would have to add a lot of complexity to your code using traditional bindings.
 Adwaita for Swift enables you to simply add a unique identifier to the variable that should be stored, and will take care of the rest.
-
 ```swift
 @State("count") private var count = 0
 ```
 
 There is also a simple and safe approach for localization with the [Localized](https://github.com/AparokshaUI/Localized) package.
 
 ### Readability
-
 The simplicity coming with the data-centric approach has a positive impact on readability.
 
 Another point is the declarative definition of the user interface itself. You can focus on what the app should look like and how it should behave rather than how to achieve those results.
@@ -125,7 +119,6 @@ var view: Body {
 ```
 
 ### Cross-Platform App Development
-
 Adwaita for Swift is useful in a number of ways:
 
 - You can write apps that run on Linux, macOS and Windows with a single codebase.
@@ -146,11 +139,11 @@ Learn how to publish your apps [in the Adwaita for Swift documentation](https://
 Each contribution to this project is highly appreciated.
 
 You can:
-
 - Create an app! Use the [template repository](https://github.com/AparokshaUI/AdwaitaTemplate) as a starting point and refer to the [tutorial](https://david-swift.gitbook.io/adwaita/gettingstarted). Feel free to showcase your project in the [discussions](https://github.com/AparokshaUI/adwaita-swift/discussions/categories/show-and-tell). Note that libadwaita works best on Linux. If you're on a newer Mac and interested in Linux, check out [Asahi Linux](https://asahilinux.org/fedora/?ref=upstract.com).
 - Open [issues](https://github.com/AparokshaUI/adwaita-swift/issues) if you find any problems or if you have an idea, or participate in the [dicussions](https://github.com/AparokshaUI/adwaita-swift/discussions) by asking questions, dicussing ideas, or informing others about your work.
 - Write [documentation](https://david-swift.gitbook.io/adwaita/) to help others understand Adwaita for Swift.
 - Simply star the [repository](https://github.com/AparokshaUI/adwaita-swift) to improve its discoverability.
 - Take a look at the [Memorize](https://flathub.org/apps/io.github.david_swift.Flashcards) app. It is the first app on Flathub built using Adwaita for Swift.
 
 Thanks for your participation ❤️
+

_posts/2025-03-31-swift-6.1-released.md

@@ -4,7 +4,6 @@ published: true
 date: 2025-03-31 10:00:00
 title: Swift 6.1 Released
 author: [hborla]
-category: 'Language'
 featured-image:
   url: '/assets/images/placeholders/image_placeholder_large.png'
   alt: 'An FPO image for a blog.'
@@ -42,7 +41,7 @@ nonisolated extension S: CustomStringConvertible, Equatable {
 }
 ```
 
-Swift 6.1 also improves type inference for task groups by inferring the child task result type of `withTaskGroup` and `withThrowingTaskGroup`. Previously, you always had to write the child task result type as an argument when creating the task group:
+Swift 6.1 also improves type inference for task groups by inferring the child task result type of `withTaskGroup` and `withThrowingTaskGroup`. Previously, you always had to write the child task result type as an argument when creating the task group: 
 
 ```swift
 let messages = await withTaskGroup(of: Message.self) { group in
@@ -112,7 +111,7 @@ You can find a complete list of language proposals that were accepted through th
 
 ## Package and build improvements
 
-Swift 6.1 introduces _package traits_, a new configuration for packages that allows them to offer different APIs and features when used in specific environments, such as Embedded Swift and WebAssembly. Package authors can define a set of traits in their `Package.swift` that their package offers, which provide a way to express conditional compilation and optional dependencies. The package can specify a set of default traits that are enabled in clients, and clients can customize the traits they use when they declare the dependency:
+Swift 6.1 introduces *package traits*, a new configuration for packages that allows them to offer different APIs and features when used in specific environments, such as Embedded Swift and WebAssembly. Package authors can define a set of traits in their `Package.swift` that their package offers, which provide a way to express conditional compilation and optional dependencies. The package can specify a set of default traits that are enabled in clients, and clients can customize the traits they use when they declare the dependency:
 
 ```swift
 dependencies: [
@@ -165,7 +164,7 @@ func doSomething(first: String?, second: Int) -> Float
 func doSomething(first: String?, second: Int) -> Double
 ```
 
-Previously, if you wrote a link to one of these overloads you needed to include a short hash of that symbol’s unique identifier to disambiguate the link and uniquely reference the specific overload. Swift-DocC's warnings aided in writing these hashes but a person can't decode the resulting hash suffix (`-3c5j`) to determine which overload the link is referring to. Now, you can use a combination of parameter types and return types—like `-(String,_)`, `->Float,` or `-(String?,_)->Double`—to disambiguate the link and uniquely reference a specific overload.
+Previously, if you wrote a link to one of these overloads you needed to include a short hash of that symbol’s unique identifier to disambiguate the link and uniquely reference the specific overload. Swift-DocC's warnings aided in writing these hashes but a person can't decode the resulting hash suffix (`-3c5j`) to determine which overload the link is referring to. Now, you can use a combination of parameter types and return types—like  `-(String,_)`, `->Float,` or `-(String?,_)->Double`—to disambiguate the link and uniquely reference a specific overload.
 
 You can discover the minimal combination of parameter types and return types for each overload from Swift-DocC’s warnings about ambiguous symbol links. For more details, see [the Ambiguous Symbol Links section of Linking to Symbols and Other Content](/documentation/docc/linking-to-symbols-and-other-content#Ambiguous-Symbol-Links).
 

_posts/2025-06-04-redesigned-swift-org-is-now-live.md

@@ -2,7 +2,7 @@
 layout: post
 published: true
 date: 2025-06-04 10:00:00
-title: 'Redesigned Swift.org is now live'
+title: "Redesigned Swift.org is now live"
 author: [shahmishal]
 category: 'Community'
 ---
@@ -35,8 +35,9 @@ The homepage now highlights Swift's strengths alongside code examples that illus
 
 We look forward to hearing your feedback on this first set of changes as we continue to redesign other sections of the site. There are several ways to offer feedback on the redesign and to get involved:
 
-- A [forum announcement](https://forums.swift.org/t/redesigned-swift-org-is-now-live/80296) has been shared on the forums that can be used for discussion, and the website repository has GitHub issues.
-- The website itself is open source, and your contributions to the [swiftlang/swift-org-website](https://github.com/swiftlang/swift-org-website) repository are welcome.
-- [The Swift Information Architecture Project](https://forums.swift.org/t/announcing-the-swift-information-architecture-project/75866) is an ongoing effort that has helped inform decisions related to the site redesign.
+* A [forum announcement](https://forums.swift.org/t/redesigned-swift-org-is-now-live/80296) has been shared on the forums that can be used for discussion, and the website repository has GitHub issues.
+* The website itself is open source, and your contributions to the [swiftlang/swift-org-website](https://github.com/swiftlang/swift-org-website) repository are welcome.
+* [The Swift Information Architecture Project](https://forums.swift.org/t/announcing-the-swift-information-architecture-project/75866) is an ongoing effort that has helped inform decisions related to the site redesign.
+
 
 Thank you to the website workgroup and community members for contributing to these improvements.