pebble-dev / pebble-dev/developer.rebble.io
Rehost static assets buckets
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
There's links in a handful of places to downloads for things like the SDK packages, zip files with example assets, etc. Those aren't included in the build from this repo (because of large file sizes, not suitable for Git), so we should probably spin up a bucket on our cloud infra to hold them (since that's what Pebble did).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying the existing links for SDK packages, example asset archives, and other downloads across the developer resources site. Review how Pebble hosts comparable static assets and determine the cloud bucket arrangement. Done means the assets are hosted outside the repository and every affected link points to the new location.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100