48 lines
1.9 KiB
JavaScript
48 lines
1.9 KiB
JavaScript
/**
|
|
* Forge components.
|
|
*
|
|
* Two audiences read the same records, so the folder holds two sets of pieces.
|
|
*
|
|
* Admin — building and managing workforce skill verification:
|
|
*
|
|
* ForgeHeader the masthead and the two ways in
|
|
* ForgeProgress the state of the library, in four counted figures
|
|
* SkillLibrary every skill, filterable
|
|
* SkillCard one skill and its verification journey
|
|
* SkillDetail one skill read end to end
|
|
* AddSkillTraining skill → training → proof → Owliver → publish
|
|
* ForgeRail the authoring job, the rules, and the way to Owliver
|
|
*
|
|
* Worker — proving a skill. Kept whole: these are what the employee experience
|
|
* is built from, and reframing the admin console is no reason to remove them.
|
|
*
|
|
* YourForge the record, or the process that creates it
|
|
* NextSkill the skill to prove now
|
|
* ChallengeDirectory every other challenge, searchable
|
|
* ForgeInsight a rule and a remark
|
|
*
|
|
* State and derivation stay with the page; these only arrange what they are
|
|
* given. `challengeMeta` holds the lookups both audiences share.
|
|
*/
|
|
|
|
/* Admin */
|
|
export { ForgeHeader } from './ForgeHeader';
|
|
export { ForgeProgress } from './ForgeProgress';
|
|
export { SkillLibrary } from './SkillLibrary';
|
|
export { SkillCard } from './SkillCard';
|
|
export { SkillDetail } from './SkillDetail';
|
|
export { AddSkillTraining } from './AddSkillTraining';
|
|
export { ForgeRail } from './ForgeRail';
|
|
|
|
/* Worker */
|
|
export { YourForge } from './YourForge';
|
|
export { NextSkill } from './NextSkill';
|
|
export { ChallengeDirectory } from './ChallengeDirectory';
|
|
export { ForgeInsight } from './ForgeInsight';
|
|
|
|
export {
|
|
buildRequirements, DIFF_TONE, owliverCriteria, proofSteps, statusOf, STATUS_LABEL, STATUS_TONE,
|
|
trainingKinds, trainingOutline, trainingType, TYPE_HINT, TYPE_ICON, TYPE_LABEL, typeOf,
|
|
workforceUsage,
|
|
} from './challengeMeta';
|