You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Likewise, mention of new Sandcastle demos should link to them.
I'm not sure how to keep the website in sync yet. Perhaps we just allow links in CHANGES.md to be broken in master until we do the monthly release. We'd update the website as part of the release - which should not stop us from updating it more often.
The text was updated successfully, but these errors were encountered:
For this we would modify the markdown in CHANGES.md to link Cesium types to their reference documentation, instead of just showing them as code. For example, we would change:
Fixed `EllipsoidPrimitive` picking and picking objects with materials that have transparent parts.
to
Fixed [EllipsoidPrimitive](http://cesium.agi.com/Cesium/Build/Documentation/EllipsoidPrimitive.html) picking and picking objects with materials that have transparent parts.
which changes:
Fixed EllipsoidPrimitive picking and picking objects with materials that have transparent parts.
to
Fixed EllipsoidPrimitive picking and picking objects with materials that have transparent parts.
You might be able to write a script to do this, but you would have to verify everything since sometimes we remove or rename a type. Also, for new types, the reference doc will not exist yet, but it is easy to predict the url, which will be live when Cesium is released at the start of each month.
Are we every actually going to do this? I vote we just close this issue. Linking to new Sandcastle examples is a good idea; but that could be added to the release process for 1.0 going forward.
Cesium types in CHANGES.md should link to the reference doc.
Likewise, mention of new Sandcastle demos should link to them.
I'm not sure how to keep the website in sync yet. Perhaps we just allow links in CHANGES.md to be broken in master until we do the monthly release. We'd update the website as part of the release - which should not stop us from updating it more often.
The text was updated successfully, but these errors were encountered: