Skip to content

Commit 2691cec

Browse files
committed
deploy updates
1 parent d586e41 commit 2691cec

19 files changed

+36
-114
lines changed

_images/chat_button.png

-11.4 KB
Binary file not shown.
-8.43 KB
Binary file not shown.
-58.3 KB
Binary file not shown.

_images/shared1.png

-129 KB
Binary file not shown.

_images/student_question.png

-22.5 KB
Binary file not shown.

_sources/chat.rst.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ Side Chat
117117
At the top right in the Files toolbar for any open file, there is a chat icon: |comment-icon|.
118118
This opens up a chatroom which is *specific to that file*.
119119
This is commonly used to discuss the content of the given worksheet or notebook,
120-
e.g. :ref:`students asking teachers/TAs <teaching-chatrooms>`.
120+
e.g. students asking teachers/TAs.
121121

122122
.. image:: img/sagews-side-chat-a.png
123123
:align: center

_sources/jupyter-enhancements.rst.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,7 @@ widgets in CoCalc
186186
##########################
187187

188188
`Jupyter Widgets`_ are Python objects that let you build interactive GUIs for your Jupyter notebooks. CoCalc Jupyter notebooks combine the interactive capabilities of Jupyter widgets with the usual advanced features of the CoCalc platform, including
189-
:ref:`real-time collaboration <multi-user-edit>`, :doc:`TimeTravel <time-travel>`, and :ref:`side chat <side-chat>`.
189+
real-time collaboration, :doc:`time-travel`, and :ref:`side-chat`.
190190

191191
A good way to get started using Jupyter widgets is to go through the `Widget List`_ in the main widgets documentation.
192192

_sources/markdown.rst.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ Enhanced features in CoCalc Markdown
7575
@-mentions
7676
***********************************
7777

78-
See :ref:`@Mention collaborators in chat <at-mention-chat>`.
78+
See :ref:`@Mention collaborators in chat <chat-at-mentions>`.
7979

8080
***********************************
8181
Checkboxes
Lines changed: 10 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -1,59 +1,25 @@
11
.. index:: Courses; ending
22

3-
=====================
43
After the Course Ends
54
=====================
65

7-
Here are some suggestions on wrapping up after a course you managed with CoCalc comes to an end.
8-
9-
.. contents::
10-
:local:
11-
:depth: 2
12-
13-
.. index:: Courses; hide/delete projects
14-
.. _hide-delete-student-projects:
15-
16-
Hide or Delete Student Projects
17-
===============================
18-
19-
To keep the project list from becoming cluttered, an instructor may choose to hide or delete all student projects when a course ends. Student projects may be hidden using the :ref:`"Hide" batch operation <project_batch>` in the project list. Student projects may be deleted - which marks them as deleted for all students as well as the instructor - in the course file **Configuration** tab with the "Delete all Student Projects..." button, or with the :ref:`"Delete" batch operation <project_batch>` in the project list.
20-
21-
*NOTE: Upgrades to student projects may only be removed by the account that added them. If a course administrator initially upgraded student projects, then a
22-
teaching assistant with a different account deletes student projects, the upgrades will remain on the deleted projects. See the next section to recover upgrades in this case.*
23-
24-
.. index:: Courses; recover upgrades
25-
.. _recover-upgrades:
26-
27-
Remove License or Upgrades from Student Projects
28-
==================================================
6+
By default, nothing happens with the course file or students projects once the course is over. In particular, instructors and students still have access to all projects and files. However, you may want to take some actions yourself.
297

30-
Licenses
31-
--------
8+
Remove License
9+
--------------
3210

33-
If you applied a license to the course under Configuration, you will probably want to remove it after the course ends. Stopped projects do not use license resources, but a student project from a course that has ended could use license resources, for example if restarted by a student looking over work in the old course.
11+
If you purchased a dedicated course license that expires after the course ends, there is no harm in leaving it attached to the course. But if you are using an ongoing subscription or a license purchased for multiple terms, you may want to remove that license from completed courses. Otherwise former students may use some of the seats and not leave enough for incoming classes.
3412

35-
Upgrades
36-
--------
13+
Delete Student Projects
14+
-----------------------
3715

38-
If you used one of the older course upgrade plans, note that upgrades applied to student projects may be re-used on other projects after the course ends. Upgrades remain valid until their expiration date.
16+
Student projects may be deleted in the course file **Actions** tab with the **Delete all Student Projects...** button. You may want to do it if your do NOT want them to have access to the course materials in the future.
3917

40-
To recover upgrades from student projects, i.e. to remove them from student projects and return them to the pool of available upgrades, the owner of the account that originally applied the upgrades can do a :ref:`"Remove Upgrades..." batch operation <project_batch>`, after selecting the desired projects with either search text or hashtag. Or, if student projects are to be deleted, the owner of the upgrades can open the course file **Configuration** tab and click "Delete all Student Projects...".
4118

4219
.. index:: Courses; access after end
4320
.. _access-after-end:
4421

45-
Student Access After Course Ends
46-
======================================
47-
48-
**Question:** My students have been asking whether they can keep using their CoCalc account after this course ends. I assume that their account **and projects** will remain active, but revert to the settings associated with a free account and projects. Is that correct? If not, is there anything they need to do to use their accounts in the future?
49-
50-
**Answer:** Yes, they will have full access, though they may need to take an extra step to ensure they can easily login.
51-
52-
The detail is how they are authenticated with CoCalc. For example, in case they exclusively use a Google account associated with your-college.edu, and the university revokes their account, they would be unable to access CoCalc without adding another access method.
53-
54-
For cases like that, instruct your students to **make sure they have a password set in their account settings**. Then, they can always access their course projects by accessing their account via an email address and password. Later, they can change their email address, while keeping access to their projects. In account settings, students can also associate their account with Facebook (or Github or Twitter), and login using one of those providers.
55-
56-
If the instructor has marked the student project Deleted, the student may still see the project in the project list by selecting the checkbox for Deleted projects.
57-
58-
22+
Student Account Access
23+
----------------------
5924

25+
If students were using dedicated SSO through your institution or Google login associated to their university accounts, they may not be able to log into their accounts after graduation, i.e. when their university logins are disabled. The most reliable solution in such a situation is to download files that students want to keep, and upload them to CoCalc using "personal accounts" linked to personal emails, if desired.

_static/custom.css

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,6 @@ nav.wy-nav-top {
1212
background: #4375c1;
1313
}
1414

15-
.wy-body-for-nav {
16-
max-width: 2000px; /* Adjust this value as needed */
17-
width: 100%;
18-
padding: 20px;
19-
box-sizing: border-box;
20-
}
21-
2215
/* role: strike and :strike:`...` */
2316
span.strike {
2417
text-decoration: line-through;
@@ -38,10 +31,7 @@ div.sphinxsidebar h3 {
3831
}
3932

4033
div.body {
41-
display: flex;
42-
justify-content: center;
43-
margin: 0;
44-
padding: 0;
34+
max-width: 900px;
4535
}
4636

4737
/* https://github.com/sagemathinc/cocalc-doc/issues/4 */

0 commit comments

Comments
 (0)