☂️ Scrutinize (and update) cookbook entries to verify up to standards

[parlough]

trafficstars

The cookbook entries are extremely valuable as short and sweet task-bask documentation. However, they have been written over many years by multiple authors, and aren't of a consistent writing style or quality. We should go through each one and verify that they:

• Is still valuable in its current form
• Follow the Google developer documentation style guide
• Follow our own preferred styles and requirements
• Are up to date in their statements and endorsements
• The code still works as expected
• All code uses the latest packages
• Have a runnable DartPad sample that follows the previous steps if it's possible

[atsansone]

@parlough : Consider this the framing issue for this project.

[parlough]

TODO: Someone add sorted by ranking list of cookbook recipes to this list. \cc @stef-luo

[stef-luo]

@parlough I'm sharing a Google Sheet with you!

[sfshaza2]

Wow, @parlough, some of the recipes get so few views that maybe we should retire them!

[parlough]

@parlough I'm sharing a Google Sheet with you!

Thank you @stef-luo!!

Wow, @parlough, some of the recipes get so few views that maybe we should retire them!

I'll do a quick dive into some of the ones with lower views. I have a feeling some should be retired but I want to make sure it's not because of poor search discoverability.