feat(docs): Add a table-of-contents to the docs directory.
#1108
Conversation
| * (although this will soon change to publish to https://maven.mozilla.org). | ||
| * There is also a manual step where we mirror artifacts from bintray to maven.mozilla.org, | ||
| as a temporary measure until we can get automatic publishing set up correctly. | ||
| * Publish it to the [maven.mozilla.org](https://maven.mozilla.org). |
There was a problem hiding this comment.
I updated the docs around bintray/maven while I was in here - @eoger r?
| @@ -10,7 +10,7 @@ The package is published as a release on github: https://github.com/mozilla/appl | |||
|
|
|||
| - Add the dependency line to the Cartfile, for instance: `github "mozilla/application-services" ~> "v0.16.1"` | |||
| - `carthage` will download MozillaAppServices.frameworks.zip, and add all the available frameworks to the 'Carthage/' dir. | |||
| - Choose which framework to link against for your project (in the *Link Binary with Libraries* step in your Xcode target). | |||
| - Link against the provided MozillaAppServices.framework (in the *Link Binary with Libraries* step in your Xcode target). | |||
There was a problem hiding this comment.
I believe this needs to change to reflect the fact that we're no longer publishing individual component frameworks on iOS.
| @@ -1,36 +0,0 @@ | |||
| > Android requires that all APKs be digitally signed with a certificate before they can be installed. | |||
There was a problem hiding this comment.
Maybe controversial, but...I don't think this doc belongs here. It's specifically about generating apks, which we don't do in this repo, so it wasn't obvious how to link to it from the ToC.
I wonder if there's some more android-product-development-centric place we could move it to?
There was a problem hiding this comment.
Perhaps this could live in https://github.com/mozilla-mobile/shared-docs? @vladikoff thoughts?
There was a problem hiding this comment.
Ref mozilla-mobile/shared-docs#80 for following
There was a problem hiding this comment.
Ah this doc was useful before, we can move it though, it's okay 👍
There was a problem hiding this comment.
Yep, I don't think we should lose it entirely, it's 👍 content
rfk
force-pushed
the
docs-table-of-contents
branch
from
8c959e2
to
4e2ceef
Compare
Fixes #869. Rendered.