Gardening Efforts #646
Replies: 5 comments
-
|
#649 creates the Node topic page ✅ |
Beta Was this translation helpful? Give feedback.
-
|
Love this centralized spot for talking about curated stories to build on egghead. I can pick up curating Kent C. Dodds landing page. There are a few different stories that would work well on his page. Obviously, there is EpicReact and TestingJavaScript but Kent has a great track on starting to contribute to open source that would be awesome to feature |
Beta Was this translation helpful? Give feedback.
-
|
Another activity that might be appropriate in terms of gardening is the instructor case studies that we have on howtoegghead. While transferring all the data is needed, thinking about ways that would best highlight instructors and stories would be super great |
Beta Was this translation helpful? Give feedback.
-
|
Here is the PR for the Angular Topic page #657 |
Beta Was this translation helpful? Give feedback.
-
|
I'll be working on the State Management Feature and Feature Page. |
Beta Was this translation helpful? Give feedback.
-
This outlines possible gardening efforts that we can tackle:
Topic Pages
The following topic pages need curation:
Each page needs to contain
Beginner,Intermediate,Advancedblocks, and feature courses.Home Page
We can consider a “page first” approach to curating section where the title becomes clickable and provides an entry point to the main page—a great example of this the Digital Gardening feature and its page.
The Start Learning Here section can be broken up into its own feature section. Showcasing the most popular courses and beginner-friendly content.
NEW Features. We can also create new features. A "Learn to Build Accessible Web Applications" feature section would be interesting. Mix and match these resources or any other resource:
State Management Feature. The state management playlist can also have its own feature section, very similar to the React State Management section on the react Page, but a smaller version. Mini feature sections? Ideally, it should point to the State Management Page once we have a solid version of this page.
Tailwind Feature. If we consider Tailwind content important, we can create mini-feature sections showcasing the Masterclass and other Tailwind-related content that's not necessarily courses, such as articles and podcasts.
Staff Picks and Favorites. This section is not curated and does not center the content on the learner. I would consider replacing this section with a new Feature section. See the notion document containing "groupings" of possible features.
Deep Dive into AWS & Learn Something New. This section doesn't have a clear goal. It's mostly something that we left from our previous gardening efforts. We should consider breaking these two up into their own features or creating a new feature.
Instructor Pages
The following instructor pages need curation:
The page for Stephanie Eckles is a good example of a curated instructor page. It showcases recent courses and projects. Note that we are not limited to just courses. We can also add any other resources that the instructor has created (articles, podcast episodes, talks, and partner products).
Analytics-driven curation
Analytics can drive curation efforts. Ahoy records analytics in our database. We can also consider GA, and course reviews as inputs.
Gardening efforts for the home page need to be done on a weekly basis. This is an ongoing process.
Beta Was this translation helpful? Give feedback.
All reactions