Skip to content

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Willow-Systems
Copy link
Member

No description provided.

@Willow-Systems Willow-Systems force-pushed the update-dev-portal-docs branch from 4075a98 to ab41070 Compare August 6, 2025 21:11
Copy link
Member

@Sorixelle Sorixelle left a 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.

Comment on lines +30 to +32
# > 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you meant to comment this section out? Because they're just headings right now:

image

Copy link
Member Author

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">
Copy link
Member

@Sorixelle Sorixelle Aug 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should consider different colours here, since the current combo doesn't meet accessibility requirements (4.5 for AA, 7 for AAA):

image

Copy link
Member Author

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?

Copy link
Member

@Sorixelle Sorixelle Aug 7, 2025

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.

Comment on lines +108 to +115
<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>
Copy link
Member

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.
![add-images](/images/guides/appstore-publishing/new-add-image.png)
Copy link
Member

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?

@Sorixelle Sorixelle added type: enhancement New feature or request area: content Changes to files that include developer documentation content labels Aug 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: content Changes to files that include developer documentation content type: enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants