kentcdodds / kentcdodds/react-workshop-app

Improvements to workshop format?

Open
#42 6 comments 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
151
Forks
36
PR merge metrics
No merged PRs in 30d

Description

I've run into a LOT of limitations that I've had to work around by using CRA for these workshops. I got really creative with codegen.macro, but now that I'm adding TypeScript support, I want to have different configs for the exercises and the final version of the exercises (so we can have strict mode enabled by default in the final, but not in the exercise).

So I'm making drastic changes to how `react-workshop-app` works. My plan is that this change will barely be noticeable by people going through the material as it's just the tooling/backend stuff that's changing here. I'm going to try and use Remix. BEFORE YOU WORRY: I've gotten permission from the remix authors to put remix in the "bundledDependencies", which means folks won't need to have a license to install this package even though it's using remix under the hood. Like I said, you shouldn't even notice that remix is powering everything. But I promise you that *I* will! 😅

So, while I'm at it, I figured I'd reach out and see whether folks are interested in offering feedback on the format of the workshops and the app. Everything's on the table, though a LOT of the way the workshops are set up are based on actual experience of many formats, so it's very possible that I won't accept your idea and I may not have time to explain why, but if you have some feedback on the format/setup of the workshop, I'd like to hear them here and now while I'm in the process of changing everything.

I'm curious about stuff like, the visual design of the app itself, where the exercise/final files are located on disk, etc. Stuff like that.

Thanks for any and all feedback!

Contributor guide

Open the contributing guide

Research direction

No specific files, tests, or entry points are named. Review the current workshop app and how exercise and final files are laid out, then assess the proposed tooling and format changes; done would require an agreed direction rather than a defined patch.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.