Organise the hub: app catalog section, source badges, and easier contributions - #2
Merged
Conversation
chumphrey-wd
left a comment
chumphrey-wd
left a comment
Collaborator
There was a problem hiding this comment.
Changes look good.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Turns the flat examples repo into a properly organised hub: Workday-built apps and community examples are now separate, labeled, and easier to contribute to. Rolls up the feedback from the team thread (tool-agnostic wording, no-Node contributors, disclaimer, quality labeling).
Sections
New
catalog/ folderfor Workday-built apps, maintained by Workday, seeded with Work From Almost Anywhere.examples/c stays the community section and is where external PRs land.CODEOWNERS requires a DevRel review on any catalog change (activates with branch protection). Both CI workflows watch both folders.
The README now carries two generated tables (App catalog and Examples), and landing READMEs in each folder explain what lives there when browsing on GitHub.
Labeling
Every entry declares a source (workday or community, defaulting by section, validated in CI). Cards and entry pages show it as a badge in the header: blue check for Workday, neutral for Community. Entry pages get a breadcrumb showing their section, linking back to the filtered gallery.
Easier contributions
Shell scaffolders for machines that can't install Node: scripts/new-example.sh (macOS, Linux) and scripts\new-example.ps1 (Windows). All three scaffolders now copy examples/_template/, so there's one source of truth and no drift between them.
Docs are tool agnostic: App Builder, IDE plugins, and the WDCLI are presented as peer options, and the orchestration instructions cover promote-to-IMPL for tenants without Extend.
A "verify everything" notice in the README: provided as is, test in a non-production tenant.
Site
Detail pages live at
/catalog/<name>and/examples/<name>, both rendered from each entry's README with the shared layout.How to check it
node scripts/validate-examples.mjs --check passes; try an off-list product, a community source on the catalog entry, or deleting a README to see it refuse.Scaffold with any of the three scripts and diff the outputs; they're identical.
cd site && npm install && npm run dev: filters, badges, breadcrumbs, and both detail routes.