admin2/manual_teachbooks
1
0
Fork 0
mirror of https://github.com/TeachBooks/manual.git synced 2026-11-13 14:55:51 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

updated badges

Browse source
This commit is contained in:
Tom van Woudenberg 2024-11-29 11:18:13 +01:00
parent 1f0b0f47ee
commit f33cb3f75f
4 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
book/basic-features/utterances.md
View file

@ -1,6 +1,6 @@
# Discussions in your book: Utterances
{bdg-muted}`Javascript script`
{bdg-white}`GitHub app and Javascript script`
[Utterances 🔮](https://utteranc.es/) is a lightweight open-source widget which allows you, your colleages and your students to discuss stuff in a blog post in your book. It is build on GitHub issues, so requires a GitHub repository, although the book can be hosted anywhere (so also on GitLab).

2
book/features/HTML_javascript.md
View file

@ -5,7 +5,7 @@
This section is useful for user type 5.
```
{bdg-info}`iframe`
{bdg-danger}`iframe`
In this section, we will discuss how to [create](creating_basic_HTML_elements.md) and [embed](adding_HTML_elements.md) interactive HTML/Javascript elements created in HTML/JavaScript in a TeachBook. These HTML/Javascript element work very fluently and don't require a python kernel running in the background.

2
book/features/adding_HTML_elements.md
View file

@ -1,6 +1,6 @@
# Adding interactive HTML/JavaScript elements
{bdg-info}`iframe`
{bdg-danger}`iframe`
In this section, we will discuss how to embed interactive elements created in HTML/JavaScript in a TeachBook. If you are interested in learning how to create these elements yourself, we will discuss an example in the [next article](creating_basic_HTML_elements.md). As an example, let us discuss how to embed an interactive 3D model of a subsurface environment I created:

4
book/features/overview.md
View file

@ -7,12 +7,12 @@ Since the list of TeachBook features is getting quite long, we have grouped them
Additionally, not all features are built using the same type of sourcecode. For transparency, tags will help differentiate between the different backgrounds of the features:
- {bdg-warning}`Javascript overlay`
- {bdg-success}`Chrome Extension`
- {bdg-muted}`GitHub App and Javascript script`
- {bdg-white}`GitHub App and Javascript script`
- {bdg-secondary}`Python Package`
- {bdg-light}`GitHub Reusable Action`
- {bdg-dark}`Git Workflow`
- {bdg-primary}`Sphinx Extension`
- {bdg-info}`iframe`
- {bdg-danger}`iframe`
Finally, the purpose, installation process and usage of each features is elaborated on in the respective sub-sections.