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
Copy file name to clipboardExpand all lines: USER_GUIDE.md
+37-4Lines changed: 37 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,6 +74,7 @@ Typical actions:
74
74
-`Preview` (start/stop local preview server)
75
75
-`Export` (build LMS package locally)
76
76
-`Deploy` (publish to CourseCode Cloud, optional)
77
+
- Cloud deployment management for linked courses
77
78
- open in editor / reveal in Finder / open terminal
78
79
79
80
### Settings
@@ -114,7 +115,9 @@ Cloud is most helpful when you want to spend less time on packaging and file sha
114
115
115
116
What Cloud gives you:
116
117
- a hosted course version you can access online after deploy
117
-
- shareable preview links for reviewers and stakeholders
118
+
- a main preview link for reviewers and stakeholders
119
+
- password-protected preview sharing by default, with passwordless sharing as an explicit choice
120
+
- Production and Preview pointers so you can stage review versions without changing what learners see
118
121
- LMS format downloads later (SCORM/cmi5) from the same uploaded build
119
122
- simpler updates (redeploy once, then use Cloud for future downloads/sharing)
120
123
- cloud-managed runtime services (reporting/channel) without manual endpoint setup
@@ -150,9 +153,39 @@ If you sign in to CourseCode Cloud, Desktop can also support:
150
153
Typical non-technical workflow:
151
154
1. Build and test in Desktop with `Preview`
152
155
2. Click `Deploy` to publish to Cloud
153
-
3. Share the Cloud preview link with reviewers
154
-
4. Make fixes in Desktop and deploy again
155
-
5. Download the LMS package you need from Cloud when approved
156
+
3. Keep `Require password` on for the main preview link unless you intentionally want a passwordless review URL
157
+
4. Share the Cloud preview link with reviewers
158
+
5. Make fixes in Desktop and deploy again
159
+
6. Use the Cloud Deployments panel to move the Preview pointer for review or Production pointer when approved
160
+
7. Download the LMS package you need from Cloud when approved
161
+
162
+
### Managing Cloud Deployments in Desktop
163
+
164
+
For a linked Cloud course, Project Detail includes a Cloud Deployments panel. It is a focused Desktop subset of the Cloud web app.
165
+
166
+
Use it to:
167
+
- create, enable, disable, copy, or open the main preview link
168
+
- add, change, or remove the preview password
169
+
- extend preview expiry by seven days
170
+
- see the current Production and Preview pointer versions
171
+
- view recent deployments
172
+
- move the Preview pointer to a selected deployment
173
+
- move the Production pointer to a selected deployment when the course is not GitHub-linked
174
+
175
+
The main preview link follows the Preview pointer. That means the shared URL can stay the same while you choose which deployment reviewers see.
176
+
177
+
Desktop keeps advanced Cloud workflows in the Cloud web app, including multiple pinned stakeholder preview links, cleanup, analytics, and detailed audit exploration.
178
+
179
+
### GitHub-Linked Courses
180
+
181
+
If a course is linked to a GitHub repository, production deploys are managed by GitHub. Push to the repo to update Production.
182
+
183
+
Desktop still supports:
184
+
- preview-only deploys
185
+
- Preview pointer changes
186
+
- main preview link password/expiry management
187
+
188
+
Desktop disables Production pointer changes for GitHub-linked courses to avoid conflicting with the repository workflow.
156
189
157
190
Cloud features should always be labeled optional in Desktop UI/docs.
0 commit comments