-
Notifications
You must be signed in to change notification settings - Fork 7
Update developer portal documentation #33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Willow Systems <[email protected]>
4075a98
to
ab41070
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New guide looks great! Just a few cleanup bits.
# > Note: An app can only be published privately while it is not already published | ||
# > publicly. If an app is already public, it must be unpublished before it can be | ||
# > made private. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops. Yes I did
|
||
<div class="alert alert--fg-white alert--bg-orange"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was a built in colour scheme from the docs. Shall we update the colour globally?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm, probably not, don't want to risk breaking something else. I've created #35 to track general accessibility stuff. For now I think we leave it as is, we can revisit later.
<div class="alert alert--fg-white alert--bg-orange"> | ||
{% markdown %} | ||
**Legacy Section** | ||
|
||
## Publishing a Companion App | ||
The Rebble Developer Portal does not yet support companion apps. The legacy Pebble documentation is currently preserved here for reference. | ||
If you wish to publish or update a companion app, please get in touch via [Discord]({{ site.links.discord_invite }}). | ||
{% endmarkdown %} | ||
</div> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we turn this "Legacy Section" into a reusable component? Seems useful for other parts of the docs too. Includes are probably the way to go here.
of the listing, including links to subpages, a preview of the public page, | ||
and any missing information preventing release. | ||
3. Click 'Next' to be taken to the images page. Here you should upload screenshots for each platform your Watchface supports. | ||
 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: do we need the new-
prefix on the image filenames?
No description provided.