Closed vegetabill closed 3 years ago
Opinions:
I think we can limit use of jQuery, but I don't think it's throwaway. It's legacy, but a lot of companies still use it, and I think it's a good way to introduce methods and use of JS in the dom. I can also be convinced to just teach vanilla JS for this purpose, though. But by the logic of the first comment, we could just teach them React instead of HTML too.
I understand if pacing is a problem, but I don't see why that means we have to start from scratch.
I also think some of this kinda cuts into the core of project-based learning, so I think we do need to have a phone call about it. I'll ping you.
Notes from 04/27 Bill:Alina 1-on-1:
Archived feedback notes from Eventonica experience
jQuery instances are listed here: https://github.com/Techtonica/curriculum/pull/1371
@alodahl I added a table to visualize the parts of this epic above and I'll try to further break it down over the next week.
Does no issue mean that it's done, or that it needs an issue made?
@alodahl I've added placeholder tickets so now there is either an issue or an explicit "none" for each and I think this now represents the whole scope. We an add a ✅ or something as they are done like JIRA does for their inline card links
All items are merged or closed. Closing this epic.
Future ideas can be added to => #1542
TL;DR
High-level improvements to Eventonica based on H1-2020 cohort's experience along with Alina & Bill's Opinions.
Background
In cohorts so far, the main project used to learn full-stack app development is [Eventonica](), a CRUD app for handling events of different categories. It was divided into Parts 1-7.
Eventonica Tenets
New Sequence
Intro readme should list user story-style features and these will be used throughout all the assignments.
Optional Items
1429 Reinforcement Lesson for splitting/refactoring a frontend and backend (nice-to-have)
Child Issues
For FAQs on how to contribute, see: https://github.com/Techtonica/curriculum/blob/main/CONTRIBUTING.md