Teaching kits will need manual tagging w/ web lit competencies

RESOLVED WONTFIX

Status

Webmaker
Teaching Kits / Curriculum
RESOLVED WONTFIX
4 years ago
4 years ago

People

(Reporter: brett, Assigned: codekat)

Tracking

Details

(Whiteboard: [resources] [oct17])

(Reporter)

Description

4 years ago
Over in bug #1031288, I tried to create a link to a search of teaching kits tagged with relevant competencies.

When I tried to actually make these searches, though, we realized we haven't actually been tagging teaching kits per competency.  This is likely because we don't have UI for this.

However, if we do want to link out to a larger corpus of makes other than what we've curated, we'll need to consider manually tagging these kits.

We may find however that any kit we'd consider tagging we'd have curated into /resources, so over to you Kat to evaluate!
(Assignee)

Comment 1

4 years ago
Hey Brett, 

Good point, this has been a worry of mine as well. We can manually tag kits when we need to, but we still can't guarantee users will know that in order to show up in the Web Lit resources pages under "view more", they'll need to self-tag based on competency. 

I've also seen users incorrectly tag competencies (ie just "Design" for #DesignAccessibility) so creating some sort of UI toggle where users can choose their competencies upon publish would be a great improvement to help standardize things here. How hard might that be to do?
(Reporter)

Comment 2

4 years ago
> I've also seen users incorrectly tag competencies (ie just "Design" for
> #DesignAccessibility) so creating some sort of UI toggle where users can
> choose their competencies upon publish would be a great improvement to help
> standardize things here. How hard might that be to do?

Tt's something we can't block on right now with the tools team full time on appmaker and the rest of the team sprinting for maker party.

We can file that, and either implement in thimble now, push on building kit builder, or consider a more long term solution when we look at a more robust code editing solution like Nimble.  But for now this is really a curation exercise.
Whiteboard: [july25] → [resources] [aug8]
* Where did we land with this one? Mark resolved wontfix given Brett's comments above?
Flags: needinfo?(kat)
Whiteboard: [resources] [aug8] → [resources] [sep19]
(Assignee)

Comment 4

4 years ago
Yeah, appears it was pushed to the back burner. Not my decision, but would love to see this revisited and prioritized somehow, to ensure we aren't missing important work from the community (as i suspect we are)
Flags: needinfo?(kat)
* Ok. If it means we're missing quality community work, let's keep it open. Thanks Kat.
Whiteboard: [resources] [sep19] → [resources] [oct17]
* the [oct17] train has now left the station
* so please update with [oct31], [nov14], [nov28], etc.
(Assignee)

Comment 7

4 years ago
Marking as resolved wontfix since this work has been stopped for now
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.