TL;DR

I would like to contribute, but I am not sure how exactly the SwiftUI.swift translates into the website.

In the SwiftUI.swift file, it seems like there is an extension for every single existing Swift API, with copied paste documentation from Apple's Documentation. Obviously, the point of this project is to replace them with better, detailed, step by step documentation. But not all the methods in SwiftUI.swift shows up on the website. Will they automatically show up once the documentation is edited, or is this a manual process?

By the way, should we break up the SwiftUI.swift file into subfiles, organizing by the SwiftUI component type? Because it is kind of painful when all the previews on Github doesn't work.

Hello, the current example of RedactionReasons produces such a rendering:

I think adding a VStack would create the desired output. Or do you think it would be distracting?

I added a VStack in this PR, let me know what you think.

On macOS, some SwiftUI controls are displayed differently, and there are also some controls that can only be used on their respective platforms on macOS and iOS. I hope they can be more comprehensively reflected in the document.

such as:

#if os(macOS)
Settings {
Text("Settings here.")
}
#endif

English is not my native language; please excuse typing errors.

…rties to align with what's in Apple's official documentation.

This is what it says in Apples documentation for @frozen @propertyWrapper struct State<Value>

You should only access a state property from inside the view’s body, or from methods called by it. For this reason, declare your state properties as private, to prevent clients of your view from accessing them. It is safe to mutate state properties from any thread.

I tried to rephrase the wording in Apples documentation as not to plagiarize, but I since Apple's documentation is already very concise, I feel like I just added fluff to something that was already clear. I'm open to suggestions regarding rephrasing.

This edit should clarify two points:

1. Accessing a state property is actually more strict than using the main thread. It should only be accessed from the call to the view's body.
2. Modifying state is actually completely permissive and can be accessed from any thread.

The new static APIs introduced in Swift 5.5 allow us to use the static versions to create a TabViewStyle. We should prefer this more concise swifty version.

Hello, the current example of RedactionReasons produces such a rendering:

I think adding a VStack would create the desired output. Or do you think it would be distracting?

I added a VStack in this PR, let me know what you think.

Hi

I am iOS developer and I saw swiftontap.com new. Its a great documentation tool and helped me a lot. Thank you very much for your works.

Also I have suggestion to add Dark Mode support on https://swiftontap.com Many developers use the dark mode and it is very difficult to focus on a light background. Thanks

The RotationGesture symbol code example uses RotationGestureView (see https://swiftontap.com/rotationgesture)

This should be updated to ContentView to be thematically consistent with other pages.