|
1 | | -# Your first TeachBook using the GitHub template |
2 | | - |
3 | | -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! |
4 | | - |
5 | | -## How to get started |
6 | | - |
7 | | -How to use the template is demonstrated in the figure below, all steps are elaborated on in the following step-by-step tutorial. |
8 | | - |
9 | | - |
10 | | -Video available [here](https://youtu.be/nN3Oi_MVvF0) |
11 | | - |
12 | | - |
13 | | -1. To get started making your TeachBook with our functionalities, use the [template TeachBook](https://github.com/TeachBooks/main/template) as template: |
14 | | - |
15 | | - |
16 | | - |
17 | | -2. Fill in a repository name, this name will be used in the future url of your book: |
18 | | - |
19 | | - |
20 | | - |
21 | | -3. 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. |
22 | | - |
23 | | -4. 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`: |
24 | | - |
25 | | - |
26 | | - |
27 | | -5. 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`: |
28 | | - |
29 | | - |
30 | | - |
31 | | -6. 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/test_book_from_template/](https://dummydocent.github.io/test_book_from_template/) for the shown repository. These links are visible in the action's summary as well, as shown in the figure of step 4. |
32 | | - |
33 | | -7. Want to get started directly? Your book contains a few exercises to get your started! Visit `https://<username or organiszation_name>.github.io/<repository_name>/exercises/exercises` (case sensitive) to get started with the first ones to get the basics of how to interact with your book on GitHub. |
34 | | - |
35 | | - |
36 | | - |
37 | | -Additional tip: |
38 | | -Set the repository website as your GitHub Pages website under `Code`- `About` - `Settings icon` - `Website` - `Use your GitHub Pages Website` |
39 | | - |
40 | | - |
41 | | - |
42 | | -## Features |
43 | | -- A github repository structure for making a [Jupyter Book](https://github.com/executablebooks/jupyter-book) (`/book`) |
44 | | -- An empty TeachBook containing an intro page on root, an example markdown page, an example jupyter notebook page, an example references page. and an example credits page. (`/book/_toc.yml`, `/book/_config.yml`, `/book/credits.md`, `/book/intro.md`, `/book/references.md`, `/book/some_content/overview.md`, `/book/some_content/text_and_code.ipynb`) |
45 | | -- A file ready for adding references (`references.bib`, `/book/references.md`) |
46 | | -- An example favicon (web browser icon) (`/book/figures/favicon.ico`, `book/_config.yml`.) |
47 | | -- An example logo (`/book/figures/TUDelft_logo_rgb.png`, `/book/config.yml`) |
48 | | -- The configuration files set ready to make your Jupyter Notebooks pages work with [live code using our sphinx-thebe extension](https://teachbooks.io/manual/features/live_code.html) and our recommended settings (`/book/config.yml`) |
49 | | -- An example of setting up preprocessing your table of contents to hide certain draft chapters for eg. students (`_toc.yml`) |
50 | | -- A file containing all the recommended software packages (`requirements.txt`) |
51 | | -- A file containing the recommended license CC BY 4.0 (`LICENSE.md`) |
52 | | -- Our [GitHub workflow for publishing your TeachBook to GitHub Pages](https://github.com/TeachBooks/deploy-book-workflow) (`.github/workflow/call-deploy-book.yml`) |
53 | | -- A gitignore file containing standard python filetype to ignore (`.gitignore`) |
54 | | -- A readme containing information how to use the template, which can adjusted after using the template (`README.md`) |
55 | | - |
56 | | -## Contribute |
57 | | -This tool's repository is stored on [GitHub ](https://github.com/TeachBooks/template). The `README.md` of the branch `manual_description` is also part of the [TeachBooks manual ](https://teachbooks.io/manual/external/template/README.html) as a submodule. If you'd like to contribute, you can create a fork and open a pull request on the [GitHub repository ](https://github.com/TeachBooks/template). To update the `README.md` shown in the TeachBooks manual, create a fork and open a merge request for the [GitHub repository of the manual ](https://github.com/TeachBooks/manual). If you intent to clone the manual including its submodules, clone using: `git clone [email protected]:TeachBooks/manual.git`. |
58 | | - |
59 | | -## Template README |
60 | | -> Remove all of the above after you've taken this template and followed the instructions. The following lines are a template for your own README |
61 | | -
|
62 | | -# `<Book title>` |
63 | | - |
64 | | -`<description of book's content en target audience>` |
65 | | - |
66 | | -## Contributors |
67 | | -- `<list authors>` |
68 | | - |
69 | | -## Reuse content |
70 | | -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](https://creativecommons.org/licenses/by/4.0/)) |
71 | | - |
72 | | -The website (`<book_website_url>`) is created using the [TeachBooks Python package](https://github.com/TeachBooks/TeachBooks). To recreate it you have two options (more information in the [TeachBooks manual](https://teachbooks.io/manual/): |
73 | | -- 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). |
74 | | -- 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`. |
| 1 | +# Awesome Causal Inference with Python |
| 2 | + |
| 3 | +## 🛠️ 우리의 개발 문화 (Our Development Culture) |
| 4 | +**우리의 개발 문화** |
| 5 | +```python |
| 6 | +class CollaborationFramework: |
| 7 | + def __init__(self): |
| 8 | + self.tools = { |
| 9 | + 'communication': 'kakaoTalk', |
| 10 | + 'version_control': 'GitHub Projects', |
| 11 | + 'ci/cd': 'Github Actions', |
| 12 | + 'docs': 'TeachBooks' |
| 13 | + } |
| 14 | + |
| 15 | + def workflow(self): |
| 16 | + return """주간 사이클: |
| 17 | + [일요일 미팅 종료] |
| 18 | + ↓ (issue + reviewer + backup_reviewer 할당) |
| 19 | + [월~토요일 자정] |
| 20 | + 각자 issue 작업 |
| 21 | + 로컬 → 브랜치 push |
| 22 | + PR 생성 + 리뷰어 태그 |
| 23 | + ↓ |
| 24 | + [일요일 낮] |
| 25 | + 리뷰어 PR 리뷰 & 코멘트 |
| 26 | + ↓ |
| 27 | + [일요일 저녁] |
| 28 | + 미팅: |
| 29 | + - 리뷰어 발표 & assignee 발표 내용 보충 |
| 30 | + - 논의 → merge & issue close |
| 31 | + - 새로운 issue/reviewer 할당 |
| 32 | + ↓ |
| 33 | + [새로운 주차 사이클 시작]""" |
| 34 | +``` |
| 35 | + |
| 36 | + |
| 37 | +### 주차별 활동 (2025 가을 일정) |
| 38 | + |
| 39 | +| idx | Date | 미팅 | 불참 예정 | 토픽 발표 1 | 토픽 발표 2 | |
| 40 | +| --- | ---- | ---- | -------- | ----------- | ----------- | |
| 41 | +| 1 | 9/7 | ✅ | | | | |
| 42 | +| 2 | 9/14 | ✅ | | | | |
| 43 | +| 3 | 9/21 | ✅ | | | | |
| 44 | +| 4 | 9/28 | ✅ | | | | |
| 45 | +| 5 | 10/5 | ✅ | | | | |
| 46 | +| 6 | 10/12 | ✅ | | | | |
| 47 | +| 7 | 10/19 | ✅ | | | | |
| 48 | +| 8 | 10/26 | | — | — | — | |
| 49 | +| 9 | 11/2 | ✅ | | | | |
| 50 | +| 10 | 11/9 | ✅ | 권명석, 강산아 (학회) | | | |
| 51 | +| 11 | 11/16 | | — | — | — | |
| 52 | +| 12 | 11/23 | ✅ | | | | |
| 53 | +| 13 | 11/30 | ✅ | | | | |
| 54 | +| 14 | 12/7 | ✅ | | | | |
| 55 | +| 15 | 12/14 | ✅ | | | | |
| 56 | +| 16 | 12/21 | ✅ | | — | — | |
0 commit comments