The fkra blog
Changelog · 2 min

Choose what your learners see, and turn paths into programs

Workspace admins choose which fkra Library content their learners see, copy and adapt library paths, and string paths into programs with a route, an order and a certificate.

Changelog

Choose what your learners see, and turn paths into programs

Released on 27 October.

The catalog

Every workspace used to show the whole fkra Library beside its own content, with no way to tell the two apart. A new Catalog tab shows what learners see: live paths by source, the top paths, updates from fkra and what needs you. Each path carries its source (fkra, your organization or your copy) and a switch to show or hide it. A workspace can show everything, only what it picks, or only its own content, and choose whether new library paths arrive on their own. Existing workspaces keep showing everything until they change it, and hiding a path never interrupts a learner already enrolled in it.

The fkra Library

The fkra Library tab lets admins browse the library by domain, follow a domain, and add a path under one of their own domains. Change makes an organization copy with only the modules you want. The copy keeps receiving fkra’s fixes to the modules it kept, and replaces the original for new learners. Compare shows how a copy differs from the library and brings changes over.

Programs

A program strings paths into one journey. Admins build it from paths of any source, set the order (step by step, suggested or any order) and attach a certificate. Learners find programs on Discover and at /app/programs, with a progress track for each path, a route that marks what is done, where they are and what opens next, and what they will earn. Finishing a path in a step-by-step program enrolls the learner in the next one.

Also in this release

Changed

  • Domain pages list their paths in the order the domain sets.
  • The community directory lists only your organization’s communities.
0
2 views
v1.3.0-beta.10changed
FK
Get the next entry

One email when we publish. Research, product decisions, and what teams report back.