Repository navigation
Roadmap to 1.0聽#144
Copy link
Copy link
Closed
Description
Hey there!
Thanks for showing interest in using TutorialKit! We are currently planning to do a 1.0 release and we're excited to share a list of the changes that we are intending to make before the release.
Planned Changes
- 馃毃 Renaming
tutorialkitto@tutorialkit/cli. So we can use that name for the vscode extension and also because thenpm create tutorialcommand is the recommended way to create a new tutorial. - 馃毃 Renaming
@tutorialkit/components-reactto@tutorialkit/reactand move it fromcomponents/reacttoreact. Simpler name and descriptive enough. - 馃毃 Update
src/content/config.tsto import the full schema from@tutorialkit/types. - 馃毃 UnoCSS config:
- Use a deep merge strategy and move default presets and transformers in
@tutorialkit/theme. - Find a way to remove
content.inline
- Use a deep merge strategy and move default presets and transformers in
- 馃摉 Document docs on how tow write your own component with
tutorialkit:store - 馃摉 Document that
tutorialkit:coreprovide low level access to webcontainer and is to be used only as a last resort - 馃摉 Document that using
@tutorialkit/reactwithout TutorialKit is experimental - Have
create-tutorialdepend on"@tutorialkit/cli": "latest"and release a fire and forget version. - Remove
.vscode/settings.json. - Add TutorialKit extension to the list of recommended extension in the generated template.
- Extension:
- Frontmatter autocomplete:
- Support folder-based and config-based ordering
- Part, chapter, lesson deletion
Nice to have, some post 1.0.0 launch:
- Have the default tutorial generated showcase all of the features of TutorialKit (ala slidev)
- JSDocs on
TutorialStoreclass - VSCode Extension
- Automated releases
- Inheritance information
- Drag and drop ordering for lesson / chapter / parts
- "Checks" to prevent navigation to next lesson until current checks have passed
- Syntax highlighting for
-
Monaco as an alternative option to CodeMirror - Opt-in TypeScript intellisense
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
Barbapapazes commentedon Aug 6, 2024
For the UnoCSS part, a similar solution to this one, https://github.com/slidevjs/slidev/blob/main/packages/slidev/node/setups/unocss.ts, used in Slidev could be used? This could help to simplify the DX and the starter.
Nemikolh commentedon Aug 7, 2024
@Barbapapazes Thanks for the pointer! This
mergeConfigsfunction fromunocssseems to be what we're looking for 馃憖