final-report

Final Report for the TeachBooks Wizzard

https://github.com/lopalov/final-report

Science Score: 44.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (14.0%) to scientific vocabulary
Last synced: 6 months ago · JSON representation ·

Repository

Final Report for the TeachBooks Wizzard

Basic Info
Statistics
  • Stars: 0
  • Watchers: 0
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created 9 months ago · Last pushed 9 months ago
Metadata Files
Readme License Code of conduct Citation

README.md

Your first TeachBook using the GitHub template

The template allows you to start your own TeachBook and hosting that TeachBook online without knowledge on Git, the Jupyter book package, python or anaconda. It doesn't elaborate on the collaborative functionalities of Git or how to edit the book. Please look at our manual (https://teachbooks.io/manual) to find more about that!

How to get started

How to use the template is demonstrated in the figure below, all steps are elaborated on in the following step-by-step tutorial.

Demonstration for a public repository Video available here

  1. To get started making your TeachBook with our functionalities, use the template TeachBook as template:

Use template

  1. Fill in a repository name, this name will be used in the future url of your book:

Create new repository

  1. You can choose for Private only if you've GitHub Pro, GitHub Team, GitHub Enterprise Cloud, or GitHub Enterprise Server. Otherwise, you won't be able to publish your TeachBook online. Furthermore, it prevents people from contributing to your book, making your book essentially 'closed' instead of 'open'. Note that the built book website is always public.

  2. change the baseurl and repositoryurl properties in `config.ymlunderhtmlandhtmlthemeoptionsto"https://.github.io//"and"https://github.com//"respectively. The end result should look like this: html: favicon : "figures/TB_favicon.ico" # Replace this with your own favicon baseurl : "https://<your_username>.github.io/<your_repository_name>/" ... html_theme_options: logo: ... repository_url: "https://github.com/<your_username>/<your_repository_name>" `

  3. You need to activate GitHub pages so that your website is published to the internet. As long as you don't do this your TeachBook is not published online. Actually, now that you've taken this template our workflow tries to publish it to GitHub pages, which you didn't have the chance to activate yet. That's why you probably received an email with 'call-deploy-book: Some jobs were not successful' and you see the failed job under Initial commit. You can activate GitHub pages by setting the source for GitHub pages to GitHub Actions under Settings - Pages - Build and deployment - Source - GitHub Actions:

Activate GitHub Pages

  1. Make an edit to the TeachBook by editing and committing changes to one of the files in the book/ subdirectory (available under Code). Now checkout the progress of the publishing workflow under Actions - All workflows - call-deploy-book -<the most recent workflow run>. Remember, the first commit which is there has failed because GitHub Pages wasn't activated at the time of Initial commit, you could also re-run that job if you don't want to make an edit. You can do so by running the workflow from Actions - All workflows - call-deploy-book - Initial commit - Re-run all jobs - Re-run jobs:

Action

  1. When the workflow has finished, visit your build TeachBook at https://<username or organiszation_name>.github.io/<repository_name> (case sensitive). For our example it is https://dummydocent.github.io/testbookfrom_template/ for the shown repository. These links are visible in the action's summary as well, as shown in the figure of step 4.

  2. For creating the PAT, the user has to click the "Don't have an access token?" hypertext, which will redirect them to the GitHub page for creating a token. After that the user will have to write down the name of the token in the input box for Token name, change repository access to all repositories and go under permissions/repository permissions and change contents to read and write. When clicking Generate token, the user will be redirected to a page which displays the token. They have to copy and store that if they don't want to redo the token creation process again. After that is done, the user can input the token into the input box under "Enter GitHub Access Token", which would allow them access to the rest of the GitHub functionality.

Reuse content

Feel free to reuse this content or contribute to it. Please give appropriate credit, provide a link to the license, and indicate if changes were made (CC BY 4.0 License)

The website (<book_website_url>) is created using the TeachBooks Python package. To recreate it you have two options (more information in the TeachBooks manual: - In the GitHub interface: fork this repository, enable Github Pages from the source GitHub actions (Settings - Code and automation - Pages - Build and deployment - Source - GitHub Actions), enable workflows (Actions - I understand my workflows, go ahead and enable them) and run the call-deploy-book workflow (Actions - call-deploy-book - Run workflow - Run workflow). The website is released on the URL as shown on the workflow summary when the workflow has finished (Actions - call-deploy-book - call-deploy-book - Summary). - On your own computer: clone this repository, install the required packages (pip install -r requirements.txt) and build the book (teachbooks build book). The website is stored locally in book/_build/index.html.

Owner

  • Login: Lopalov
  • Kind: user

Citation (CITATION.cff)

# This CITATION.cff file was generated with cffinit.
# Visit https://bit.ly/cffinit to generate yours today!

cff-version: 1.2.0
title: 'TeachBooks Template' # replace with your own book title when you use this template
authors: #replace with your own name(s) if you use this template
- email: info@teachbooks.io
  name: 'TeachBooks Development Team'
  website: 'https://teachbooks.io/'
message: 'If you use this teachbook, please cite it using these metadata.'
preferred-citation:
  type: book
  authors: #replace with your own name(s) if you use this template
  - email: info@teachbooks.io
    name: 'TeachBooks Development Team'
    website: 'https://teachbooks.io/'
#  - given-names: Tom
#    name-particle: van
#    family-names: Woudenberg
#    email: t.r.van.woudenberg@tudelft.nl
#    affiliation: TeachBooks
#    orcid: 'https://orcid.org/0000-0002-9536-061X'
  url: 'https://teachbooks.github.io/template/' # replace with your own URL (book website / publisher link) when you use this template
  identifiers:
    - type: url
      value: 'https://teachbooks.github.io/template/' # replace with your own URL when you use this template
      description: 'Published book on GitHub Pages'
    - type: url
      value: 'https://github.com/TeachBooks/template' # replace with your own URL when you use this template
      description: 'GitHub repository'
  abstract: >- # replace with your own abstract when you use this template
    The template allows you to start your own TeachBook and
    hosting that TeachBook online without knowledge on Git,
    the Jupyter book package, python or anaconda. It doesn't
    elaborate on the collaborative functionalities of Git or
    how to edit the book
  keywords: # replace with your own keywords when you use this template
    - TeachBooks
    - Template
    - 'Jupyter Book'
  title: 'TeachBooks Template' # replace with your own book title when you use this template
  institution:
    name: 'TeachBooks' # replace with your own institution when you use this template
  license: CC-BY-4.0
  license-url: 'https://creativecommons.org/licenses/by/4.0/'
  copyright: '© 2025 TeachBooks' # replace with your own affiliation / name when you use this template
  languages:
    - en # replace with your book language when you use this template
  contact: # replace with your own contact information when you use this template
  - email: info@teachbooks.io
    name: 'TeachBooks Development Team'

GitHub Events

Total
  • Member event: 1
  • Push event: 91
  • Pull request event: 1
  • Create event: 2
Last Year
  • Member event: 1
  • Push event: 91
  • Pull request event: 1
  • Create event: 2

Dependencies

.github/workflows/call-deploy-book.yml actions
requirements.txt pypi
  • download_link_replacer *
  • jupyterbook-patches *
  • sphinx-exercise *
  • sphinx-iframes *
  • sphinx-image-inverter *
  • sphinx-named-colors *
  • teachbooks *
  • teachbooks-sphinx-tippy *
  • teachbooks_software_project_extension_name ==0.1.3