[go: up one dir, main page]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PB Results Prescriptive Documentation: H5P Naming #3832

Open
jcurtis-pressbooks opened this issue Nov 6, 2024 · 1 comment
Open

PB Results Prescriptive Documentation: H5P Naming #3832

jcurtis-pressbooks opened this issue Nov 6, 2024 · 1 comment

Comments

@jcurtis-pressbooks
Copy link
jcurtis-pressbooks commented Nov 6, 2024

In Pressbooks, the way H5P activities are integrated makes the activity name less critical for students, as they don’t see it (although it might improve the user experience if they DID see the activity names - as noted in some other usability-related tasks).

Naming is more about helping instructors organize their content. However, it’s still important to clearly indicate to students what they need to complete. Developing a consistent naming process takes time and may require adjustments as content evolves, but there’s currently no recommended approach for naming.

This task is to provide prescriptive "best practices" type guidance in documentation about how to approach naming so that it works well for organizing content AND it works well for using and interpreting learning data and scores captured via Pressbooks Results.

Best practices-type materials probably already exist and may be in use by clients - whether developed by H5P or by instructional designers supporting faculty creators. We should investigate what already exists, especially anything openly-licensed, and consider how to adapt this work to fit the Pressbooks Results context.

@cmurtagh
Copy link
Contributor

This Asana ticket has a lot of overlap with this github issue:

https://app.asana.com/0/647986684381816/1208770115541213/f

A note has been add in the Asana issue to reference this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants