CesiumGS/cesium

Consistent boilerplate code in Sandcastle demos

Open

#6,338 opened on Mar 15, 2018

View on GitHub
 (8 comments) (0 reactions) (0 assignees)JavaScript (3,324 forks)batch import
category - sandcastlegood first issue

Repository metrics

Stars
 (11,758 stars)
PR merge metrics
 (Avg merge 26d 3h) (26 merged PRs in 30d)

Description

Some Sandcastle examples use outdated or inconsistent boilerplate code. This can be fixed be clicking the Save As button in each demo and replacing the code.

This would make a good beginner issue.

More details and an example from @emackey in https://github.com/AnalyticalGraphicsInc/cesium/pull/6337/

The other changes here are just from re-saving the demo directly from a Sandcastle instance. Would be great to have an intern go through and re-save all the demos at some point, so the boilerplate code all matches what Sandcastle produces (or write a build script to do it).

Contributor guide

Research direction
Review the linked PR (#6337) for details on the desired boilerplate, then open each Sandcastle demo, click 'Save As' to regenerate boilerplate, and replace the old code.
Tech stack
javascript
Domain
frontend
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85