We know it’s not perfect – it’s a quick production to see if there’s any community interest.
If there is, we’ll expend a bit of time/money on it.
That said – there are some things people should note:
Table of Content
Please note how “clean” and “unstuffed” the ToC is.
This is largely due to the lack of keyword-stuffing in Headings!
We’ve not crammed “Google” or “API” or “Leak” into every possible spot.
UX
We’ve done what we can to improve the overall experience of analysing modules and attributes.
This includes alpha-nav for modules, condensing vertical space (with the option to expand) for attributes, providing an alpha-sorted attribute-list (with target/jump links), collection related links (from the viewed module, to the viewed module, and from modules that start with the same initial string).
If we missed anything – please feel free to suggest it (within reason :D).
Community/Consensus
The whole purpose of this site is to try to encourage a greater sense of community around the leak.
Yes, it’s great seeing some of the big names say stuff (and others complain about it).
But we know some of you are just to busy to go to the efforts of deep analysis,
or put your thoughts out in tweets etc.
At least here, you can gather them, give them some life, attention and hopefully contribute as a collective.
If we’re really lucky – we’ll chip away through this and find all the valuable bits, together!
To help with that – we (currently) have 2 member-voting systems.
Belongs to (which aspects of Google the module seems tied to – such as Search, YouTube, Drive etc.).
Impact (how influential/important the module seems to be to a specific aspect).
(Comments (module and attribute) will be landing shortly.)