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
{{ message }}
This repository was archived by the owner on Nov 5, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 5, 2025. It is now read-only.
Must have in both overview and detail
-Title
-Author
-Some notion of popularity (thumbs up or down is likely simplest/best)
-Open in VS code button (this is new, but a really strong part of the experience, and turns out it isn’t too hard to make happen)
-Deploy button
-Tags
Can go in both, but ok if only in detail
-Brief description
-Source code link
Things that should definitely only be in detail page:
-License information
-Preview of ARM template
-More detailed form for deployment (This will be more extensive and can be designed elsewhere)
-More detailed statistics on usage/popularity
-README or markdown file explaining the sample
-flag for broken (some mechanism to report)
Activity
ColbyTresness commentedon Feb 28, 2019
Must have in both overview and detail
-Title
-Author
-Some notion of popularity (thumbs up or down is likely simplest/best)
-Open in VS code button (this is new, but a really strong part of the experience, and turns out it isn’t too hard to make happen)
-Deploy button
-Tags
Can go in both, but ok if only in detail
-Brief description
-Source code link
Things that should definitely only be in detail page:
-License information
-Preview of ARM template
-More detailed form for deployment (This will be more extensive and can be designed elsewhere)
-More detailed statistics on usage/popularity
-README or markdown file explaining the sample
-flag for broken (some mechanism to report)