You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Throughout this guide, you'll see references to `<your-organization-uuid>` and `<your-certification-uuid>` placeholders. Make sure to replace all of these with your actual UUIDs from the [Instructor Console](https://cloud.layer5.io/academy/instructors-console) when implementing your certification.
39
+
{{< /alert >}}
40
+
41
+
Each certification is tied to a specific organization and secured by a unique identifier (UUID). This is a system-generated ID that ensures your content is scoped only to your organization.
42
+
43
+
You'll need two types of UUIDs:
44
+
-**Certification ID**: A unique identifier for your specific certification that gets added to the front matter of your certification's index file
45
+
-**Organization ID**: Your organization's UUID that's used in directory paths
46
+
47
+
{{< alert type="info" title="Generating Your IDs from the Instructor Console" >}}
48
+
49
+
The easiest way to get the correct IDs is by using the content creation tool.
50
+
51
+
- Navigate to the [Instructor Console](https://cloud.layer5.io/academy/instructors-console) in Layer5 Cloud.
52
+
- Use the "Create New Content" tool and fill in the information for your new content
53
+
- The final step generates all the necessary materials to get started: the front matter, repository setup instructions, and your unique IDs.
54
+
55
+
[Learn more](https://cloud.layer5.io/academy/instructors-console) about the Academy Console.
56
+
{{< /alert >}}
57
+
35
58
### 1. Set Up the Directory Structure
36
59
37
-
All content for a new certification must reside within the `content/certifications/orgID` directory. To keep content organized, each certification has its own folder named with a descriptive, URL-friendly slug.
60
+
All content for a new certification must reside within the `content/certifications/<your-organization-uuid>` directory. To keep content organized, each certification has its own folder named with a descriptive, URL-friendly slug.
38
61
39
-
The final URL will follow this pattern: `https://cloud.layer5.io/academy/content/certifications/orgID/<certification-folder-name>/`
62
+
The final URL will follow this pattern: `https://cloud.layer5.io/academy/content/certifications/<your-organization-uuid>/<certification-folder-name>/`
40
63
41
64
Below is the standard file structure:
42
65
43
66
```
44
-
content/certifications/
45
-
└── orgID/layer5-certification-exam/ <-- The <certification-name> directory
67
+
content/certifications/<your-organization-uuid>
68
+
└── layer5-certification-exam/ <-- The <certification-name> directory
46
69
├── _index.md <-- Defines the certification's metadata
47
70
├── exam-1.md <-- (Optional) A standard content page for introduction
48
71
├── optional-exam-2.md <-- An optional supplementary exam
@@ -62,7 +85,7 @@ Here's a complete example of the YAML frontmatter for a certification's `_index.
62
85
```yaml
63
86
---
64
87
type: "certification"
65
-
id: "445a80d2-1234-1234-1234-2329c5ddcdec"
88
+
id: "<your-certification-uuid>"
66
89
title: "Layer5 Network Certification"
67
90
description: "Validate your expertise in Layer5 networking technologies through comprehensive assessment"
68
91
banner: "images/layer5-icon.svg"
@@ -80,7 +103,7 @@ categories: "platform"
80
103
| Field | Required | Description |
81
104
| :--- | :--- | :--- |
82
105
|`type`| ✅ | Must be set to `"certification"` to identify this content correctly. |
83
-
|`id`| ✅ |A globally unique identifier (UUID) for the certification.|
106
+
|`id`| ✅ |**Crucial.** A stable UUID for tracking progress. **Do not change.**|
84
107
|`title`| ✅ | The human-readable title that will be displayed to users. |
85
108
|`description`| ✅ | A comprehensive summary of the certification's scope and objectives. |
86
109
|`weight`| - | Controls the display order (lower numbers appear first). Items are sorted alphabetically by title if not specified.|
0 commit comments