@sp-days-framework/create-sp-days 1.1.0-beta2 → 1.1.0-beta3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/changelog.mdx +15 -0
- package/lib/.tsbuildinfo +1 -1
- package/package.json +1 -1
- package/publish-package-docs.js +8 -0
- package/templates/addon-slidev/slidev/best-practices-guide.md +769 -0
- package/templates/addon-slidev/slidev/slidev-theme-sykehuspartner.md +1 -1
- package/templates/addon-slidev/slidev/templates/_category_.yml +2 -0
- package/templates/addon-slidev/slidev/templates/process-documentation.md +193 -0
- package/templates/addon-slidev/slidev/templates/technical-workshop.md +160 -0
- package/templates/addon-slidev/slidev/templates/tool-introduction.md +160 -0
- package/templates/addon-slidev/slidev/templates/training-module.md +149 -0
- package/templates/page-course/course/placeholder-basic-usage.mdx +40 -6
- package/templates/page-course/docusaurus.config.ts +42 -37
- package/templates/page-course/package.json +6 -5
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
theme: "@sp-days-framework/slidev-theme-sykehuspartner"
|
|
3
3
|
title: Sykehuspartner Slidev Theme
|
|
4
4
|
description: A professional Slidev theme for creating presentations with consistent Sykehuspartner branding
|
|
5
|
-
layout:
|
|
5
|
+
layout: cover
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Sykehuspartner Slidev Theme
|
|
@@ -0,0 +1,193 @@
|
|
|
1
|
+
---
|
|
2
|
+
theme: "@sp-days-framework/slidev-theme-sykehuspartner"
|
|
3
|
+
title: Process Documentation Template
|
|
4
|
+
description: Document workflows and processes for your team
|
|
5
|
+
layout: cover
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Process Documentation Template
|
|
9
|
+
|
|
10
|
+
## Workflow & Procedures
|
|
11
|
+
|
|
12
|
+
---
|
|
13
|
+
layout: intro
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
# Process Overview
|
|
17
|
+
|
|
18
|
+
## Purpose & Scope
|
|
19
|
+
|
|
20
|
+
This document outlines the standard process for [activity]. Following this ensures consistency and quality.
|
|
21
|
+
|
|
22
|
+
**Owner:** Team Lead
|
|
23
|
+
**Last Updated:** December 2025
|
|
24
|
+
|
|
25
|
+
---
|
|
26
|
+
layout: section
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
# Process Flow
|
|
30
|
+
|
|
31
|
+
## Step-by-Step Guide
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
layout: three-cols-header
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
# The Three Phases
|
|
38
|
+
|
|
39
|
+
::left::
|
|
40
|
+
|
|
41
|
+
## 1. Initiation
|
|
42
|
+
|
|
43
|
+
**Trigger:** Request received
|
|
44
|
+
|
|
45
|
+
- Validate requirements
|
|
46
|
+
- Assess feasibility
|
|
47
|
+
- Assign resources
|
|
48
|
+
- Create ticket
|
|
49
|
+
|
|
50
|
+
**Output:** Approved request
|
|
51
|
+
|
|
52
|
+
::middle::
|
|
53
|
+
|
|
54
|
+
## 2. Execution
|
|
55
|
+
|
|
56
|
+
**Trigger:** Approval granted
|
|
57
|
+
|
|
58
|
+
- Plan activities
|
|
59
|
+
- Execute tasks
|
|
60
|
+
- Monitor progress
|
|
61
|
+
- Handle issues
|
|
62
|
+
|
|
63
|
+
**Output:** Completed work
|
|
64
|
+
|
|
65
|
+
::right::
|
|
66
|
+
|
|
67
|
+
## 3. Closure
|
|
68
|
+
|
|
69
|
+
**Trigger:** Work complete
|
|
70
|
+
|
|
71
|
+
- Review results
|
|
72
|
+
- Document lessons
|
|
73
|
+
- Get sign-off
|
|
74
|
+
- Archive records
|
|
75
|
+
|
|
76
|
+
**Output:** Closed ticket
|
|
77
|
+
|
|
78
|
+
---
|
|
79
|
+
layout: two-cols-header
|
|
80
|
+
---
|
|
81
|
+
|
|
82
|
+
# Detailed Steps
|
|
83
|
+
|
|
84
|
+
::left::
|
|
85
|
+
|
|
86
|
+
## Step 1: Request
|
|
87
|
+
|
|
88
|
+
1. Submit request via portal
|
|
89
|
+
2. Include required information
|
|
90
|
+
3. Attach supporting documents
|
|
91
|
+
4. Select priority level
|
|
92
|
+
|
|
93
|
+
**SLA:** Response within 24 hours
|
|
94
|
+
|
|
95
|
+
::right::
|
|
96
|
+
|
|
97
|
+
## Step 2: Review
|
|
98
|
+
|
|
99
|
+
1. Validate completeness
|
|
100
|
+
2. Check against criteria
|
|
101
|
+
3. Assign to team member
|
|
102
|
+
4. Communicate timeline
|
|
103
|
+
|
|
104
|
+
**SLA:** Decision within 48 hours
|
|
105
|
+
|
|
106
|
+
---
|
|
107
|
+
layout: two-cols-header
|
|
108
|
+
---
|
|
109
|
+
|
|
110
|
+
# Roles & Responsibilities
|
|
111
|
+
|
|
112
|
+
::left::
|
|
113
|
+
|
|
114
|
+
## Requester
|
|
115
|
+
|
|
116
|
+
- Submit complete requests
|
|
117
|
+
- Provide context
|
|
118
|
+
- Respond to questions
|
|
119
|
+
- Accept deliverables
|
|
120
|
+
|
|
121
|
+
::right::
|
|
122
|
+
|
|
123
|
+
## Processor
|
|
124
|
+
|
|
125
|
+
- Review submissions
|
|
126
|
+
- Execute process steps
|
|
127
|
+
- Update status
|
|
128
|
+
- Deliver results
|
|
129
|
+
|
|
130
|
+
---
|
|
131
|
+
layout: two-cols-header
|
|
132
|
+
---
|
|
133
|
+
|
|
134
|
+
# Decision Points
|
|
135
|
+
|
|
136
|
+
::left::
|
|
137
|
+
|
|
138
|
+
## Approval Criteria
|
|
139
|
+
|
|
140
|
+
- ✅ Requirements complete
|
|
141
|
+
- ✅ Within scope
|
|
142
|
+
- ✅ Resources available
|
|
143
|
+
- ✅ Priority justified
|
|
144
|
+
|
|
145
|
+
::right::
|
|
146
|
+
|
|
147
|
+
## Rejection Reasons
|
|
148
|
+
|
|
149
|
+
- ❌ Incomplete information
|
|
150
|
+
- ❌ Out of scope
|
|
151
|
+
- ❌ Duplicate request
|
|
152
|
+
- ❌ Missing authorization
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
layout: center
|
|
156
|
+
---
|
|
157
|
+
|
|
158
|
+
# ⚠️ Important
|
|
159
|
+
|
|
160
|
+
All requests must follow this process.
|
|
161
|
+
|
|
162
|
+
**Exceptions require manager approval.**
|
|
163
|
+
|
|
164
|
+
---
|
|
165
|
+
layout: two-cols-header
|
|
166
|
+
---
|
|
167
|
+
|
|
168
|
+
# Quick Reference
|
|
169
|
+
|
|
170
|
+
::left::
|
|
171
|
+
|
|
172
|
+
## Contacts
|
|
173
|
+
|
|
174
|
+
- **Support:** support@example.com
|
|
175
|
+
- **Escalation:** manager@example.com
|
|
176
|
+
- **Documentation:** wiki.example.com
|
|
177
|
+
|
|
178
|
+
::right::
|
|
179
|
+
|
|
180
|
+
## Links
|
|
181
|
+
|
|
182
|
+
- Request Portal
|
|
183
|
+
- Status Dashboard
|
|
184
|
+
- FAQ & Help
|
|
185
|
+
- Training Materials
|
|
186
|
+
|
|
187
|
+
---
|
|
188
|
+
layout: end
|
|
189
|
+
---
|
|
190
|
+
|
|
191
|
+
# Questions?
|
|
192
|
+
|
|
193
|
+
## Contact the Process Owner
|
|
@@ -0,0 +1,160 @@
|
|
|
1
|
+
---
|
|
2
|
+
theme: "@sp-days-framework/slidev-theme-sykehuspartner"
|
|
3
|
+
title: Technical Workshop Template
|
|
4
|
+
description: A hands-on workshop format for technical training sessions
|
|
5
|
+
layout: cover
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Technical Workshop Template
|
|
9
|
+
|
|
10
|
+
## Hands-on Learning Experience
|
|
11
|
+
|
|
12
|
+
---
|
|
13
|
+
layout: intro
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
# Workshop Overview
|
|
17
|
+
|
|
18
|
+
## What You'll Build
|
|
19
|
+
|
|
20
|
+
In this workshop, you'll learn to build a complete solution step-by-step with practical exercises.
|
|
21
|
+
|
|
22
|
+
**Duration:** 2 hours
|
|
23
|
+
**Level:** Intermediate
|
|
24
|
+
|
|
25
|
+
---
|
|
26
|
+
layout: two-cols-header
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
# Prerequisites
|
|
30
|
+
|
|
31
|
+
::left::
|
|
32
|
+
|
|
33
|
+
## Required Knowledge
|
|
34
|
+
|
|
35
|
+
- Basic programming experience
|
|
36
|
+
- Familiarity with command line
|
|
37
|
+
- Understanding of core concepts
|
|
38
|
+
- Development environment setup
|
|
39
|
+
|
|
40
|
+
::right::
|
|
41
|
+
|
|
42
|
+
## Tools Needed
|
|
43
|
+
|
|
44
|
+
- Code editor (VS Code recommended)
|
|
45
|
+
- Terminal access
|
|
46
|
+
- Git installed
|
|
47
|
+
- Required SDKs/runtimes
|
|
48
|
+
|
|
49
|
+
---
|
|
50
|
+
layout: section
|
|
51
|
+
---
|
|
52
|
+
|
|
53
|
+
# Part 1
|
|
54
|
+
|
|
55
|
+
## Getting Started
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
layout: two-cols-header
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
# Step 1: Project Setup
|
|
62
|
+
|
|
63
|
+
::left::
|
|
64
|
+
|
|
65
|
+
## Create Project Structure
|
|
66
|
+
|
|
67
|
+
```bash
|
|
68
|
+
mkdir my-project
|
|
69
|
+
cd my-project
|
|
70
|
+
npm init -y
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
This creates a new project with default configuration.
|
|
74
|
+
|
|
75
|
+
::right::
|
|
76
|
+
|
|
77
|
+
## Install Dependencies
|
|
78
|
+
|
|
79
|
+
```bash
|
|
80
|
+
npm install express dotenv
|
|
81
|
+
npm install -D typescript @types/node
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
Install both runtime and development dependencies.
|
|
85
|
+
|
|
86
|
+
---
|
|
87
|
+
|
|
88
|
+
# Step 2: Configuration
|
|
89
|
+
|
|
90
|
+
## Create Configuration File
|
|
91
|
+
|
|
92
|
+
```typescript
|
|
93
|
+
// config.ts
|
|
94
|
+
import { config } from 'dotenv';
|
|
95
|
+
|
|
96
|
+
config();
|
|
97
|
+
|
|
98
|
+
export const settings = {
|
|
99
|
+
port: process.env.PORT || 3000,
|
|
100
|
+
environment: process.env.NODE_ENV || 'development',
|
|
101
|
+
apiKey: process.env.API_KEY,
|
|
102
|
+
};
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
Environment variables keep sensitive data secure.
|
|
106
|
+
|
|
107
|
+
---
|
|
108
|
+
layout: two-cols-header
|
|
109
|
+
---
|
|
110
|
+
|
|
111
|
+
# Step 3: Implementation
|
|
112
|
+
|
|
113
|
+
::left::
|
|
114
|
+
|
|
115
|
+
## Before (Basic)
|
|
116
|
+
|
|
117
|
+
```typescript
|
|
118
|
+
// Simple approach
|
|
119
|
+
function getData() {
|
|
120
|
+
const response = fetch(url);
|
|
121
|
+
return response.json();
|
|
122
|
+
}
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
Basic implementation without error handling.
|
|
126
|
+
|
|
127
|
+
::right::
|
|
128
|
+
|
|
129
|
+
## After (Improved)
|
|
130
|
+
|
|
131
|
+
```typescript
|
|
132
|
+
// Better approach
|
|
133
|
+
async function getData() {
|
|
134
|
+
try {
|
|
135
|
+
const response = await fetch(url);
|
|
136
|
+
if (!response.ok) throw new Error();
|
|
137
|
+
return response.json();
|
|
138
|
+
} catch (e) {
|
|
139
|
+
console.error('Failed:', e);
|
|
140
|
+
}
|
|
141
|
+
}
|
|
142
|
+
```
|
|
143
|
+
|
|
144
|
+
---
|
|
145
|
+
layout: center
|
|
146
|
+
---
|
|
147
|
+
|
|
148
|
+
# 🎯 Exercise Time
|
|
149
|
+
|
|
150
|
+
Try implementing the improved version yourself.
|
|
151
|
+
|
|
152
|
+
**Time:** 10 minutes
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
layout: end
|
|
156
|
+
---
|
|
157
|
+
|
|
158
|
+
# Workshop Complete!
|
|
159
|
+
|
|
160
|
+
## Questions & Discussion
|
|
@@ -0,0 +1,160 @@
|
|
|
1
|
+
---
|
|
2
|
+
theme: "@sp-days-framework/slidev-theme-sykehuspartner"
|
|
3
|
+
title: Tool Introduction Template
|
|
4
|
+
description: Introducing a new tool or technology to your team
|
|
5
|
+
layout: cover
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Tool Introduction Template
|
|
9
|
+
|
|
10
|
+
## Discover New Technology
|
|
11
|
+
|
|
12
|
+
---
|
|
13
|
+
layout: intro
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
# What is [Tool Name]?
|
|
17
|
+
|
|
18
|
+
## A Brief Introduction
|
|
19
|
+
|
|
20
|
+
[Tool Name] is a modern solution that helps teams accomplish their goals more efficiently.
|
|
21
|
+
|
|
22
|
+
**Category:** Development Tool
|
|
23
|
+
**License:** Open Source / Commercial
|
|
24
|
+
|
|
25
|
+
---
|
|
26
|
+
layout: fact
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
# 10x
|
|
30
|
+
|
|
31
|
+
## Faster than traditional approaches
|
|
32
|
+
|
|
33
|
+
Based on real-world benchmarks
|
|
34
|
+
|
|
35
|
+
---
|
|
36
|
+
layout: two-cols-header
|
|
37
|
+
---
|
|
38
|
+
|
|
39
|
+
# Key Features
|
|
40
|
+
|
|
41
|
+
::left::
|
|
42
|
+
|
|
43
|
+
## Core Capabilities
|
|
44
|
+
|
|
45
|
+
- **Feature 1** - Primary functionality
|
|
46
|
+
- **Feature 2** - Secondary capability
|
|
47
|
+
- **Feature 3** - Advanced option
|
|
48
|
+
- **Feature 4** - Integration support
|
|
49
|
+
|
|
50
|
+
::right::
|
|
51
|
+
|
|
52
|
+
## Benefits
|
|
53
|
+
|
|
54
|
+
- Increased productivity
|
|
55
|
+
- Reduced complexity
|
|
56
|
+
- Better collaboration
|
|
57
|
+
- Improved reliability
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
layout: section
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
# Getting Started
|
|
64
|
+
|
|
65
|
+
## Installation & Setup
|
|
66
|
+
|
|
67
|
+
---
|
|
68
|
+
|
|
69
|
+
# Installation
|
|
70
|
+
|
|
71
|
+
## Quick Setup Guide
|
|
72
|
+
|
|
73
|
+
```bash
|
|
74
|
+
# Install via package manager
|
|
75
|
+
npm install -g tool-name
|
|
76
|
+
|
|
77
|
+
# Verify installation
|
|
78
|
+
tool-name --version
|
|
79
|
+
|
|
80
|
+
# Initialize in your project
|
|
81
|
+
tool-name init
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
**Requirements:** Node.js 18+, Git
|
|
85
|
+
|
|
86
|
+
---
|
|
87
|
+
layout: two-cols-header
|
|
88
|
+
---
|
|
89
|
+
|
|
90
|
+
# Configuration
|
|
91
|
+
|
|
92
|
+
::left::
|
|
93
|
+
|
|
94
|
+
## Basic Config
|
|
95
|
+
|
|
96
|
+
```yaml [tool-config.yaml ~i-vscode-icons:file-type-yaml~]
|
|
97
|
+
# Minimal configuration
|
|
98
|
+
name: my-project
|
|
99
|
+
version: 1.0.0
|
|
100
|
+
settings:
|
|
101
|
+
debug: false
|
|
102
|
+
output: ./dist
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
::right::
|
|
106
|
+
|
|
107
|
+
## Advanced Options
|
|
108
|
+
|
|
109
|
+
```yaml [tool-config.yaml ~i-vscode-icons:file-type-yaml~]
|
|
110
|
+
# Extended configuration
|
|
111
|
+
name: my-project
|
|
112
|
+
version: 1.0.0
|
|
113
|
+
settings:
|
|
114
|
+
debug: true
|
|
115
|
+
output: ./dist
|
|
116
|
+
plugins:
|
|
117
|
+
- plugin-a
|
|
118
|
+
- plugin-b
|
|
119
|
+
```
|
|
120
|
+
|
|
121
|
+
---
|
|
122
|
+
|
|
123
|
+
# Common Commands
|
|
124
|
+
|
|
125
|
+
## Daily Usage
|
|
126
|
+
|
|
127
|
+
```bash
|
|
128
|
+
# Start development mode
|
|
129
|
+
tool-name dev
|
|
130
|
+
|
|
131
|
+
# Run tests
|
|
132
|
+
tool-name test
|
|
133
|
+
|
|
134
|
+
# Build for production
|
|
135
|
+
tool-name build
|
|
136
|
+
|
|
137
|
+
# Deploy to environment
|
|
138
|
+
tool-name deploy --env production
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
Use `tool-name --help` for full command reference.
|
|
142
|
+
|
|
143
|
+
---
|
|
144
|
+
layout: center
|
|
145
|
+
---
|
|
146
|
+
|
|
147
|
+
# 🚀 Try It Now
|
|
148
|
+
|
|
149
|
+
Get started in under 5 minutes.
|
|
150
|
+
|
|
151
|
+
**Documentation:** docs.example.com
|
|
152
|
+
**Support:** support@example.com
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
layout: end
|
|
156
|
+
---
|
|
157
|
+
|
|
158
|
+
# Questions?
|
|
159
|
+
|
|
160
|
+
## Let's Discuss
|
|
@@ -0,0 +1,149 @@
|
|
|
1
|
+
---
|
|
2
|
+
theme: "@sp-days-framework/slidev-theme-sykehuspartner"
|
|
3
|
+
title: Training Module Template
|
|
4
|
+
description: Educational content format for training and onboarding
|
|
5
|
+
layout: cover
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Training Module Template
|
|
9
|
+
|
|
10
|
+
## Learning & Development
|
|
11
|
+
|
|
12
|
+
---
|
|
13
|
+
layout: intro
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
# Module Overview
|
|
17
|
+
|
|
18
|
+
## Learning Objectives
|
|
19
|
+
|
|
20
|
+
By the end of this module, you will be able to:
|
|
21
|
+
|
|
22
|
+
- Understand core concepts and terminology
|
|
23
|
+
- Apply knowledge to practical scenarios
|
|
24
|
+
- Identify common patterns and solutions
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
layout: fact
|
|
28
|
+
---
|
|
29
|
+
|
|
30
|
+
# 80%
|
|
31
|
+
|
|
32
|
+
## of learning happens through practice
|
|
33
|
+
|
|
34
|
+
Hands-on experience is key to retention
|
|
35
|
+
|
|
36
|
+
---
|
|
37
|
+
layout: section
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
# Core Concepts
|
|
41
|
+
|
|
42
|
+
## Foundation Knowledge
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
layout: two-cols-header
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
# Key Concept 1
|
|
49
|
+
|
|
50
|
+
::left::
|
|
51
|
+
|
|
52
|
+
## Definition
|
|
53
|
+
|
|
54
|
+
A clear explanation of the first key concept that learners need to understand.
|
|
55
|
+
|
|
56
|
+
**Important:** This forms the foundation for everything else in this module.
|
|
57
|
+
|
|
58
|
+
::right::
|
|
59
|
+
|
|
60
|
+
## Example
|
|
61
|
+
|
|
62
|
+
```yaml
|
|
63
|
+
# Real-world example
|
|
64
|
+
name: demonstration
|
|
65
|
+
type: practical
|
|
66
|
+
difficulty: beginner
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
Concrete examples help solidify understanding.
|
|
70
|
+
|
|
71
|
+
---
|
|
72
|
+
layout: three-cols-header
|
|
73
|
+
---
|
|
74
|
+
|
|
75
|
+
# Three Pillars
|
|
76
|
+
|
|
77
|
+
::left::
|
|
78
|
+
|
|
79
|
+
## Pillar 1
|
|
80
|
+
|
|
81
|
+
**Foundation**
|
|
82
|
+
|
|
83
|
+
The base knowledge required to build upon.
|
|
84
|
+
|
|
85
|
+
- Core principles
|
|
86
|
+
- Basic terminology
|
|
87
|
+
- Essential skills
|
|
88
|
+
|
|
89
|
+
::middle::
|
|
90
|
+
|
|
91
|
+
## Pillar 2
|
|
92
|
+
|
|
93
|
+
**Application**
|
|
94
|
+
|
|
95
|
+
Putting knowledge into practice.
|
|
96
|
+
|
|
97
|
+
- Hands-on exercises
|
|
98
|
+
- Real scenarios
|
|
99
|
+
- Problem solving
|
|
100
|
+
|
|
101
|
+
::right::
|
|
102
|
+
|
|
103
|
+
## Pillar 3
|
|
104
|
+
|
|
105
|
+
**Mastery**
|
|
106
|
+
|
|
107
|
+
Advanced understanding and expertise.
|
|
108
|
+
|
|
109
|
+
- Complex situations
|
|
110
|
+
- Edge cases
|
|
111
|
+
- Best practices
|
|
112
|
+
|
|
113
|
+
---
|
|
114
|
+
layout: center
|
|
115
|
+
---
|
|
116
|
+
|
|
117
|
+
# 💡 Key Takeaway
|
|
118
|
+
|
|
119
|
+
Understanding the fundamentals enables you to adapt to any situation.
|
|
120
|
+
|
|
121
|
+
---
|
|
122
|
+
layout: two-cols-header
|
|
123
|
+
---
|
|
124
|
+
|
|
125
|
+
# Knowledge Check
|
|
126
|
+
|
|
127
|
+
::left::
|
|
128
|
+
|
|
129
|
+
## Question
|
|
130
|
+
|
|
131
|
+
What is the primary benefit of understanding core concepts before diving into implementation?
|
|
132
|
+
|
|
133
|
+
::right::
|
|
134
|
+
|
|
135
|
+
## Answer
|
|
136
|
+
|
|
137
|
+
Building on solid foundations ensures:
|
|
138
|
+
- Faster problem-solving
|
|
139
|
+
- Better decision making
|
|
140
|
+
- Reduced errors
|
|
141
|
+
- Easier adaptation
|
|
142
|
+
|
|
143
|
+
---
|
|
144
|
+
layout: end
|
|
145
|
+
---
|
|
146
|
+
|
|
147
|
+
# Module Complete!
|
|
148
|
+
|
|
149
|
+
## Ready for the Next Step
|
|
@@ -11,18 +11,52 @@ See interactive tasks in action with real-world examples. This page demonstrates
|
|
|
11
11
|
|
|
12
12
|
---
|
|
13
13
|
|
|
14
|
-
::::task[Install the
|
|
14
|
+
::::task[Install the SP Days Package]
|
|
15
15
|
|
|
16
|
-
Follow these steps to
|
|
16
|
+
Follow these steps to create a SP Days instance in your repo:
|
|
17
17
|
|
|
18
18
|
1. Open your terminal in the project root directory
|
|
19
|
-
2. Run the installation
|
|
20
|
-
3. Verify the package appears in your `package.json` dependencies
|
|
21
|
-
|
|
19
|
+
2. Run the installation `npx @sp-days-framework/create-sp-day`
|
|
22
20
|
|
|
23
21
|
:::hint
|
|
24
22
|
|
|
25
|
-
|
|
23
|
+
All packages and plugins will be installed and pre-configured!
|
|
24
|
+
|
|
25
|
+
:::
|
|
26
|
+
|
|
27
|
+
:::output
|
|
28
|
+
|
|
29
|
+
```terminal user="ubuntu" host="server" directory="~/"
|
|
30
|
+
// command "npx @sp-days-framework/create-sp-days"
|
|
31
|
+
{cyan}[INFO]{/cyan} Creating a new SP-Days site...
|
|
32
|
+
{green}[SUCCESS]{/green} Base template copied
|
|
33
|
+
{green}[SUCCESS]{/green} Slidev addon installed
|
|
34
|
+
{green}[SUCCESS]{/green} Resources addon installed
|
|
35
|
+
{green}[SUCCESS]{/green} Configuration processed
|
|
36
|
+
{cyan}[INFO]{/cyan} Installing dependencies with npm...
|
|
37
|
+
{green}[SUCCESS]{/green} Dependencies installed
|
|
38
|
+
{green}[SUCCESS]{/green} Created example-repo at "docs".
|
|
39
|
+
{cyan}[INFO]{/cyan} Inside that directory, you can run several commands:
|
|
40
|
+
|
|
41
|
+
{cyan}`npm start`{/cyan}
|
|
42
|
+
Starts the development server.
|
|
43
|
+
|
|
44
|
+
{cyan}`npm run build`{/cyan}
|
|
45
|
+
Bundles your website into static files for production.
|
|
46
|
+
|
|
47
|
+
{cyan}`npm run serve`{/cyan}
|
|
48
|
+
Serves the built website locally.
|
|
49
|
+
|
|
50
|
+
{cyan}`npm run slidev`{/cyan}
|
|
51
|
+
Launches Slidev presentation server.
|
|
52
|
+
|
|
53
|
+
We suggest that you begin by typing:
|
|
54
|
+
|
|
55
|
+
{cyan}`cd docs`{/cyan}
|
|
56
|
+
{cyan}`npm start`{/cyan}
|
|
57
|
+
|
|
58
|
+
Happy days! 📚
|
|
59
|
+
```
|
|
26
60
|
|
|
27
61
|
:::
|
|
28
62
|
|