learn.duke is where learners start interacting with their learning communities. It connects them to a unified interface for accessing their instructional tools.
@profmikegreene
@LASHirsh
@chrislorch
@hrvalli
@joliet
@JustinJohnsen
learn.duke displays to learners a unified interface for accessing the instructional tools used by their learning communities.
We have observed that Toolkits isn’t meeting this goal, which is causing communities to either rely on a single solution, like email or the LMS, which aren’t the best learning tool for all aspects of a learning community or use unsupported tools - even when a supported alternative exists.
How might learn.duke improve this to accommodate the entire range of learning communities, those that use a single tool, those using multiple supported tools, and those using their preferred, unsupported tools?
How might learn.duke encourage our learning communities to more frequently use the best tools to meet their learning goals and taking less energy to do so?
Answering these questions are the current goals for learn.duke
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
Added for new features.
Changed for changes in existing functionality.
Depreciated for soon-to-be removed features.
Removed for now removed features.
Fixed for any bug fixes.
Security in case of vulnerabilities.
- @lashirsh and @profmikegreene present learn.duke to ITAC on 2/22/18
Prepared by @profmikegreene
- A university-level marketing campaign is going to use learn.duke.edu and the project will have to be rebranded.
- Matthew Rascoff and Shawn Miller presented learn.duke as part of a series of learning innovation projects to senior academic leadership at the university.
- @profmikegreene presented learn.duke at EDUCAUSE ELI and submitted proposals to EDUCAUSE18 and Open Apereo 18.
Prepared by @profmikegreene
- DWS Discovery report from Lauren Hirsh drafted and sent to project team and stakeholders
Prepared by @profmikegreene
- approved problem statement
Prepared by @profmikegreene
- Box folder for storing/collecting private artifacts
- LTS business problem creation meeting to align around the specific and most core problem we want to solve first. This will drive the first MVP.
Prepared by @profmikegreene
/apps/cms/content-creation/courses/dlx/techspec/templates/wizard- InvisionApp boards created to manage ideation and design
- readme.md was significantly changed in preparation for and after stakeholder interview Lauren and Michael.
- github issues using
inspirationlabel and moved them to invisionapp.