Put together doc for the Android SDK

[finagolfin]

There is work underway on an official Android SDK for 6.2 and trunk, we should have instructions on using it ready to go.

We'd also like to put up a blog post about the Android port.

[finagolfin]

@kaishin, I don't seem to have permission to add this to the Swift on Android project, do you? If so, please add it for us.

[finagolfin]

@heckj, the Android workgroup would like to start putting together some doc on the upcoming official Android SDK. Should we submit it in Jekyll here now or will the upcoming Docc repo be ready for us to start off with soon?

[heckj]

That's wonderful @finagolfin! I don't have a terrific answer at the moment. The Swift Core Team is discussing and reviewing the docs proposal, with some questions that we're iterating on, but with that there's no concrete deadline of when a docs repo will be available to start to fill in.

If you want something immediately (in the next couple of weeks), I'd lean towards suggesting that we drop the content using Jekyll into this repo, and when the docs repository does come into full focus, we can work on migrating that content expediently and keeping any initial URL sets active with redirects as the content gets shifted.

[finagolfin]

There were some requests for onboarding doc at the Android workgroup meeting today from newcomers: is that something we should add on this website, @heckj?

Also, could you add this issue to the Android project board? I don't seem to have that permission on this repo.

[heckj]

• Added the issue to the project board

I'm hoping to have a better location in short order, but in the meantime, let's definitely add an issue to this repo so that we can track wanting to add it, and maybe stub in the goals and outline of what you (plural - the group) wants to see within it.

Add a "documentation" label (of if you can't, let me know and I'll sort it) to it. As a loose example, #19 represents what I'm starting with as I'm working on some of the server workgroup guides to update.

I'm going back and forth between free-form drafting on HackMD to work out ideas broadly, then when I feel like it's pinned down I'm dropping them into an issue - as much to track and verify consensus on what the doc is meant to cover as much as anything else.

[finagolfin]

@heckj, responding to your comment response here, as I figured it is the most relevant:

I'm not sure how much content you're thinking about, and if that warrants it's own catalog

I think Android does warrant its own catalog, both because of the importance of the platform, and because early on, we'll have to hand-hold users with more manual setup and info, before the tools can be improved like this, swiftlang/swift-package-manager#9740.

The porting page you mentioned, #21, can be a standalone page, as it will address multiple platforms.

[heckj]

(I grabbed this issue out of the website repo and moved it into the docs repo)

[finagolfin]

I'd like to put together an Android collection, as we discussed. Should we start that here, or put it on swiftlang/swift-org-website then move it here later, once this repo goes live?