From the post:
Almost one year ago, Google Cloud Platform launched our GitHub organization, with repositories ranging from tutorials to samples to utilities. This is where developers could find all resources relating to the platform, and get started developing quickly. We started with 36 repositories, with lofty plans to add more over time in response to requests from you, our developers. Many product releases, feature launches, and one logo redesign later, we are now up to 123 repositories illustrating how to use all parts of our platform!
Despite some clever naming schemes, it was becoming difficult to find exactly the code that you wanted amongst all of our repositories. Idly browsing through over 100 options wasn’t productive. The repository names gave you an idea of what stacks they used, but not what problems they solved.
Today, we are making it easier to browse our repositories and search for sample code with our landing page at googlecloudplatform.github.io. Whether you want to find all Compute Engine resources, locate all samples that are available in your particular stack, or find examples that fit your particular area of interest, you can find it with the new GitHub page. We’ll be rotating the repositories in the featured section, so make sure to wander that way from time to time.
Less than a year old and their standard metadata (read navigation) details are changing.
Judging from the comments, their users deeply appreciate the new approach.
Change is something that funders calling for standard metadata just don’t get. Which is why new standard metadata projects are so common. It is the same mistake, repeated over and over again.
To be sure, domains need to take their best shot at today’s standard metadata, but with an eye of it pointing to tomorrow’s standard metadata. To be truly useful in STEM fields, it needs to point back to yesterday’s standard metadata as well.
Sorry, got distracted.
Check out the new resources and get thee to the cloud!