Skip to content

Commit

Permalink
use-deliver/overview: Fill contents
Browse files Browse the repository at this point in the history
Fill contents for the introduction to the "Using and Delivering Content"
chapter.

Signed-off-by: Razvan Deaconescu <[email protected]>
  • Loading branch information
razvand committed Dec 28, 2023
1 parent e0decee commit 4efe309
Showing 1 changed file with 28 additions and 12 deletions.
40 changes: 28 additions & 12 deletions chapters/use-deliver/overview/reading/read.md
Original file line number Diff line number Diff line change
@@ -1,22 +1,38 @@
# Using and Delivering Content

Owner: Liza Babu
Reviewer: Ștefan Jumărea
With content being developed and available in the content repositories, educators can configure it, deploy it and use it for their educational activities.
Content can also be used by learners during self-study activities.
When educators use content, they both deliver it live, during educational activities, and make it available publicly for self-study activities.

Present:
As presented in [the "Building Blocks" section](../../../building-blocks/overview/reading/read.md), educators fork the content repository into a delivery repository.
They configure the content according to their own needs, preferences or specifics of the learner group.
They then use the deployment and publishing infrastructure to make the content available to learners, both during and outside educational activities.
Optionally, educators may also fork solution repositories into a solution delivery repositories.

- who the implementation specific repository is organized, by referring content in the content repository
- how components of the actual education delivery phase are used;
each is having a dedicated section

This chapter describes how each teaching activity is mapped to different types of content.

The mapping between teaching activities and types of content is presented in the [Introduction](../../../landing-page/read.md).

Sections:
Educators organize content for the different educational activities they employ.
The mapping between educational activities and types of content is presented in the [Introduction](../../../landing-page/read.md).
The topics presented in this chapter are dedicated to each educational activity:

- [Lectures](../../lectures/reading/read.md)
- [Practical Sessions](../../practical-sessions/reading/read.md)
- [Assignments](../../assignments/reading/read.md)
- [Tests](../../tests/reading/read.md)
- [Self-Study](../../self-study/reading/read.md)

In the ideal case, an educator is only required to update the `config.yaml` file in the delivery repository.
The rest of the content is left unaltered and is thus in perfect sync with the original content repository.

If changes to content are required, the educator is recommended to push the changes to the upstream content repository (hosted under the [`open-education-hub` GitHub organization](https://github.com/open-education-hub)).
The educator takes the role of contributor to the content repository.

Learners who want to contribute to content will do so in the delivery repository.
Eventually, the educator will push the contributions to the content repository.

It is recommended the educator be in active contact with the content developer / curator of the content repository for quick integration of contributions.
And for upstream updates to the delivery repository.

Note that each educator should adapt the use and delivery of content to their specifics.
The current methodology aims to leave as much freedom to the educator to customize the content and configuration.
It provides guides, best practices and recommendations.
Still, educators know best how to structure the content, how to select and blend existing topics for delivery.
Moreover, the methodology, being content-centric, makes no recommendations on the actual delivery methods and approaches used by educators during educational activities.

0 comments on commit 4efe309

Please sign in to comment.