Closed tomwilkie closed 8 years ago
Various answers from @monadic: URL=cloud.weave.works is 1st pref (alternatively run.weave.works) Title, name, etc=Weave Cloud, weave cloud iframe title= "My Scope" - not 'My' something TBC. (The nav bar needs a general review.)
For everything else, we're going to s/Scope/Cloud/ as appropriate.
Places that need updating:
change to cloud.weave.works
Weave Scope
change to Weave Cloud
new logo for weavecloud
s/Scope/Cloud/
Learn more about Weave Scope on our website.
s/Scope/Cloud/
@monadic we didn't discuss this?
s/Scope/Cloud/
Drop 'My', leave 'Scope'
new logo for weavecloud
s/Scope/Cloud/ where appropriate.
s/Scope/Cloud/
s/Scope/Cloud/
Other places where we need to replace scope.weave.works by cloud.weave.works:
I believe all my bits are done now.
New UI server bits deployed. I think all thats left is documentation and oauth names, when we deploy that.
I've completed the guides, and the docs. Guides are deployed to the live website, and can be browsed here:
https://www.weave.works/guides/monitor-docker-containers/ https://www.weave.works/guides/using-weave-scope-cloud-service-to-visualize-and-monitor-docker-containers/ https://www.weave.works/guides/service-discovery-and-load-balancing-with-weave-on-amazon-ecs-2/
(the DC/OS one needs more work, which I'll save for later, as it's not scope-specific. )
Docs have included Weave Cloud.
@abuehrle I still see references to scope.weave.works and Early Access on https://github.com/weaveworks/scope/blob/b624df63d3ea1043f8fb4fe077dd38ff4fa604d5/site/how-it-works.md
Also, I think the screenshots should be redone, the service has changed a lot since then.
fixed via 34b7506
readded the signup screen here: https://github.com/weaveworks/scope/pull/1604
@monadic would like us to make the service less scope-specific. Here are all the places I could find where we mention scope:
Places that need updating:
Weave Scope
@monadic, could you let us know what you would like each of these points to be replaced with please?