learningequality / learningequality/studio
Requiring tag lines for published channels
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Summary
Given the switch to 0.14 and the ability to have channel taglines in addition to descriptions to support enhanced usability in Studio, how can we support users of Studio in creating tag lines? One way would be to make tag lines required for published channels -- not sure if that's preferable.
Category
ENHANCEMENT
Real-life consequences (anything community should be aware of, for instance how it affects end users)
Improved content discoverability experience in Kolibri.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or entry points. Start by reviewing how Studio represents channel descriptions and published channels, then clarify whether taglines should be required or supported another way. Done should include an agreed approach that improves tagline creation and content discoverability for published channels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100