feat: adds auto generate showcases

[WillHutt]

Type of change

• Feature
• Documentation change
• Bug fix

Summary of change

• Auto generates showcases based on package.jsons
• Refactored the original kit to generate script

Checklist

• These changes follow the contributing guidelines
• This starter kit has been approved by the maintainers
• Changes for this new starter kit are being pushed to an integration branch instead of main
• All dependencies are version locked
• This fix resolves [Pods] - Auto generate showcases #1292
• I have verified the fix works and introduces no further errors

[netlify]

✅ Deploy Preview for starter-dev ready!

Name	Link
🔨 Latest commit	72fe6ac
🔍 Latest deploy log	https://app.netlify.com/sites/starter-dev/deploys/64af2faa83057c00080c484b
😎 Deploy Preview	https://deploy-preview-1296--starter-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[hdJerry]

Look good to me.
I Leave it for others to review

[lindakatcodes]

This PR will likely be best held until the new design PR is approved and merged - there's a reasonable bit of crossover between the two and having the showcases doesn't make sense without that new design.

There will be a few places we'll need to adjust once the design PR (#1291 ) is merged:

• in lib/parseKits, I think we'll be able to adjust that to pick the showcases from the package.json instead of having the variable there
• the showcase variable will need to be removed from the config file
• in that showcase variable we're also setting the icon - that doesn't seem to be handled in the current PR, so will need to be solved again

I've left a few other questions and suggestions for this PR, most fairly minor.

We should also update the root level README to indicate that new kits should include the "showcase" array, and what that should include / look like.

I also wonder if we need to update the packages/website predev and prebuild scripts to also generate the showcases? We'll likely need that to ensure things are kept up to date as well.

[WillHutt]

Yeah, I was initially planning on #1291 being merged before this was completed, but that had a few rounds of changes and is still ongoing.

I was considering pushing this into #1291, but I also didn't want to hold that up with any feedback on this and cause a massive delay on it like in previous PRs/tickets.

With that route chosen, I ended up removing the hook-up functionality I had originally implemented for instance

• The lib/parseKits adjustments
• Removal of the showcase variable from the config file
• The icon being handled since that isn't set in the package.json

I was going to create a new ticket that would focus on combining those above-needed changes with the new updates from #1291.

I'm good with either outcome and I will be pushing a new commit that should address a majority of the feedback you've given. 😄

[lindakatcodes]

@WillHutt The design changes from #1291 is now merged into main! You should be good to rebase this PR when you come back and move forward from there. 👍🏼

[lindakatcodes]

Looks solid to me! The only tiny nitpick I'd make is - the array in each kit's package.json file, can we name it "showcases" instead of "showcase" (make it plural)? Since the idea is that we'll eventually have multiple showcases? Otherwise, this feels good!

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[lindakatcodes]