Hopefully you find people to work on the tasks you’ve listed. In addition, maybe you can get them to also work on a “Firebase to ParseSwift” article, similar to:
https://firebase.google.com/support/guides/parse-ios
Along with:
opened 05:51PM - 21 Jan 22 UTC
type:docs
### New Feature / Enhancement Checklist
<!--
Check all of the following bo… xes [x] before submitting your issue.
Click the "Preview" tab for better readability.
Thanks for contributing to Parse Swift!
-->
- [x] I am not disclosing a [vulnerability](https://github.com/parse-community/Parse-Swift/security/policy).
- [x] I am not just asking a [question](https://github.com/parse-community/.github/blob/main/SUPPORT.md).
- [x] I have searched through [existing issues](https://github.com/parse-community/Parse-Swift/issues?q=is%3Aissue).
### Current Limitation
The SDK supports [DocC Interactive Tutorials](https://developer.apple.com/documentation/docc/tutorial-syntax), but currently has no interactive tutorials. These tutorials can be used to teach developers how to use the SDK.
All of the current tutorials are in [Swift Playgrounds](https://github.com/parse-community/Parse-Swift/tree/main/ParseSwift.playground/Pages).
### Feature / Enhancement Description
Use the [Swift Playgrounds](https://github.com/parse-community/Parse-Swift/tree/main/ParseSwift.playground/Pages) as a baseline to make Interactive tutorials. These tutorials should include images/screenshots. This is useful when:
1. A developer wants view our tutorials online at https://parseplatform.org/Parse-Swift/release/tutorials/parseswift/
2. A developer depends on the Parse-Swift SDK using SPM and goes to "Xcode->Product->Build Documentation" in their project locally
The initial tutorial file that should be edited is here: https://github.com/parse-community/Parse-Swift/blob/main/Sources/ParseSwift/Documentation.docc/Your%20First%20Object.tutorial
The Swift Playgrounds should be left intact as they give developers a real way to test the SDK against a Parse Server. Feel free to tackle individual tutorials in separate PR's. You can leverage text from the original [Objective-C SDK guide](https://docs.parseplatform.org/ios/guide/). Much of the Swift Playground code uses completion handlers for asynchronous code. It will be beneficial to write most of the code in the tutorial using `try await` instead.
Tutorials with a checkbox have already been converted from their [Swift Playgrounds counterparts](https://github.com/parse-community/Parse-Swift/tree/main/ParseSwift.playground/Pages):
- [ ] 1 - Your first Object
- [ ] 2 - Finding Objects
- [ ] 3 - User - Sign Up
- [ ] 4 - User - Continued
- [ ] 5 - ACL
- [ ] 6 - Installation
- [ ] 7 - GeoPoint
- [ ] 8 - Pointers
- [ ] 9 - Files
- [ ] 10 - Cloud Code
- [ ] 11 - LiveQuery
- [ ] 12 - Roles and Relations
- [ ] 13 - Operations
- [ ] 14 - Config
- [ ] 15 - Custom ObjectId
- [ ] 16 - Analytics
- [ ] 17 - SwiftUI - Finding Objects
- [ ] 18 - SwiftUI - Finding Objects With Custom ViewModel
- [ ] 19 - SwiftUI - LiveQuery
### Example Use Case
Completed tutorials will look like: https://developer.apple.com/tutorials/swiftui
### Videos for Designing DocC Tutorials
- [Build interactive tutorials using DocC](https://developer.apple.com/videos/play/wwdc2021/10235/)
### Alternatives / Workarounds
Solely depend on Playground implementations for demonstrating how to use SDK.
### 3rd Party References
https://developer.apple.com/tutorials/swiftui