Skip to content

Commit f2ed0b4

Browse files
Init website
1 parent 86654b6 commit f2ed0b4

File tree

9 files changed

+505
-2
lines changed

9 files changed

+505
-2
lines changed

.DS_Store

6 KB
Binary file not shown.

Gemfile

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
source 'https://rubygems.org'
2+
3+
gem "jekyll", "~> 4.3.4" # installed by `gem jekyll`
4+
# gem "webrick" # required when using Ruby >= 3 and Jekyll <= 4.2.2
5+
6+
gem "just-the-docs", "0.10.0" # pinned to the current release
7+
# gem "just-the-docs" # always download the latest release

Gemfile.lock

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
GEM
2+
remote: https://rubygems.org/
3+
specs:
4+
addressable (2.8.7)
5+
public_suffix (>= 2.0.2, < 7.0)
6+
colorator (1.1.0)
7+
concurrent-ruby (1.3.5)
8+
em-websocket (0.5.3)
9+
eventmachine (>= 0.12.9)
10+
http_parser.rb (~> 0)
11+
eventmachine (1.2.7)
12+
ffi (1.17.1)
13+
ffi (1.17.1-arm64-darwin)
14+
forwardable-extended (2.6.0)
15+
google-protobuf (3.25.5-arm64-darwin)
16+
google-protobuf (3.25.5-x86_64-linux)
17+
http_parser.rb (0.8.0)
18+
i18n (1.14.7)
19+
concurrent-ruby (~> 1.0)
20+
jekyll (4.3.4)
21+
addressable (~> 2.4)
22+
colorator (~> 1.0)
23+
em-websocket (~> 0.5)
24+
i18n (~> 1.0)
25+
jekyll-sass-converter (>= 2.0, < 4.0)
26+
jekyll-watch (~> 2.0)
27+
kramdown (~> 2.3, >= 2.3.1)
28+
kramdown-parser-gfm (~> 1.0)
29+
liquid (~> 4.0)
30+
mercenary (>= 0.3.6, < 0.5)
31+
pathutil (~> 0.9)
32+
rouge (>= 3.0, < 5.0)
33+
safe_yaml (~> 1.0)
34+
terminal-table (>= 1.8, < 4.0)
35+
webrick (~> 1.7)
36+
jekyll-include-cache (0.2.1)
37+
jekyll (>= 3.7, < 5.0)
38+
jekyll-sass-converter (3.0.0)
39+
sass-embedded (~> 1.54)
40+
jekyll-seo-tag (2.8.0)
41+
jekyll (>= 3.8, < 5.0)
42+
jekyll-watch (2.2.1)
43+
listen (~> 3.0)
44+
just-the-docs (0.10.0)
45+
jekyll (>= 3.8.5)
46+
jekyll-include-cache
47+
jekyll-seo-tag (>= 2.0)
48+
rake (>= 12.3.1)
49+
kramdown (2.5.1)
50+
rexml (>= 3.3.9)
51+
kramdown-parser-gfm (1.1.0)
52+
kramdown (~> 2.0)
53+
liquid (4.0.4)
54+
listen (3.9.0)
55+
rb-fsevent (~> 0.10, >= 0.10.3)
56+
rb-inotify (~> 0.9, >= 0.9.10)
57+
mercenary (0.4.0)
58+
pathutil (0.16.2)
59+
forwardable-extended (~> 2.6)
60+
public_suffix (6.0.1)
61+
rake (13.2.1)
62+
rb-fsevent (0.11.2)
63+
rb-inotify (0.11.1)
64+
ffi (~> 1.0)
65+
rexml (3.4.0)
66+
rouge (4.5.1)
67+
safe_yaml (1.0.5)
68+
sass-embedded (1.69.5)
69+
google-protobuf (~> 3.23)
70+
rake (>= 13.0.0)
71+
sass-embedded (1.69.5-arm64-darwin)
72+
google-protobuf (~> 3.23)
73+
terminal-table (3.0.2)
74+
unicode-display_width (>= 1.1.1, < 3)
75+
unicode-display_width (2.6.0)
76+
webrick (1.9.1)
77+
78+
PLATFORMS
79+
arm64-darwin
80+
x86_64-linux
81+
82+
DEPENDENCIES
83+
jekyll (~> 4.3.4)
84+
just-the-docs (= 0.10.0)
85+
86+
BUNDLED WITH
87+
2.5.15

LICENSE

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2022 just-the-docs
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

README.md

Lines changed: 174 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,174 @@
1-
# crup
2-
Codebase Ramp Up Program (CRUP) for New Members!
1+
# just-the-docs-template
2+
3+
This is a *bare-minimum* template to create a [Jekyll] site that:
4+
5+
- uses the [Just the Docs] theme;
6+
- can be built and published on [GitHub Pages];
7+
- can be built and previewed locally, and published on other platforms.
8+
9+
More specifically, the created site:
10+
11+
- uses a gem-based approach, i.e. uses a `Gemfile` and loads the `just-the-docs` gem;
12+
- uses the [GitHub Pages / Actions workflow] to build and publish the site on GitHub Pages.
13+
14+
To get started with creating a site, simply:
15+
16+
1. click "[use this template]" to create a GitHub repository
17+
2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions
18+
19+
If you want to maintain your docs in the `docs` directory of an existing project repo, see [Hosting your docs from an existing project repo](#hosting-your-docs-from-an-existing-project-repo).
20+
21+
After completing the creation of your new site on GitHub, update it as needed:
22+
23+
## Replace the content of the template pages
24+
25+
Update the following files to your own content:
26+
27+
- `index.md` (your new home page)
28+
- `README.md` (information for those who access your site repo on GitHub)
29+
30+
## Changing the version of the theme and/or Jekyll
31+
32+
Simply edit the relevant line(s) in the `Gemfile`.
33+
34+
## Adding a plugin
35+
36+
The Just the Docs theme automatically includes the [`jekyll-seo-tag`] plugin.
37+
38+
To add an extra plugin, you need to add it in the `Gemfile` *and* in `_config.yml`. For example, to add [`jekyll-default-layout`]:
39+
40+
- Add the following to your site's `Gemfile`:
41+
42+
```ruby
43+
gem "jekyll-default-layout"
44+
```
45+
46+
- And add the following to your site's `_config.yml`:
47+
48+
```yaml
49+
plugins:
50+
- jekyll-default-layout
51+
```
52+
53+
Note: If you are using a Jekyll version less than 3.5.0, use the `gems` key instead of `plugins`.
54+
55+
## Publishing your site on GitHub Pages
56+
57+
1. If your created site is `YOUR-USERNAME/YOUR-SITE-NAME`, update `_config.yml` to:
58+
59+
```yaml
60+
title: YOUR TITLE
61+
description: YOUR DESCRIPTION
62+
theme: just-the-docs
63+
64+
url: https://YOUR-USERNAME.github.io/YOUR-SITE-NAME
65+
66+
aux_links: # remove if you don't want this link to appear on your pages
67+
Template Repository: https://github.com/YOUR-USERNAME/YOUR-SITE-NAME
68+
```
69+
70+
2. Push your updated `_config.yml` to your site on GitHub.
71+
72+
3. In your newly created repo on GitHub:
73+
- go to the `Settings` tab -> `Pages` -> `Build and deployment`, then select `Source`: `GitHub Actions`.
74+
- if there were any failed Actions, go to the `Actions` tab and click on `Re-run jobs`.
75+
76+
## Building and previewing your site locally
77+
78+
Assuming [Jekyll] and [Bundler] are installed on your computer:
79+
80+
1. Change your working directory to the root directory of your site.
81+
82+
2. Run `bundle install`.
83+
84+
3. Run `bundle exec jekyll serve` to build your site and preview it at `localhost:4000`.
85+
86+
The built site is stored in the directory `_site`.
87+
88+
## Publishing your built site on a different platform
89+
90+
Just upload all the files in the directory `_site`.
91+
92+
## Customization
93+
94+
You're free to customize sites that you create with this template, however you like!
95+
96+
[Browse our documentation][Just the Docs] to learn more about how to use this theme.
97+
98+
## Hosting your docs from an existing project repo
99+
100+
You might want to maintain your docs in an existing project repo. Instead of creating a new repo using the [just-the-docs template](https://github.com/just-the-docs/just-the-docs-template), you can copy the template files into your existing repo and configure the template's Github Actions workflow to build from a `docs` directory. You can clone the template to your local machine or download the `.zip` file to access the files.
101+
102+
### Copy the template files
103+
104+
1. Create a `.github/workflows` directory at your project root if your repo doesn't already have one. Copy the `pages.yml` file into this directory. GitHub Actions searches this directory for workflow files.
105+
106+
2. Create a `docs` directory at your project root and copy all remaining template files into this directory.
107+
108+
### Modify the GitHub Actions workflow
109+
110+
The GitHub Actions workflow that builds and deploys your site to Github Pages is defined by the `pages.yml` file. You'll need to edit this file to that so that your build and deploy steps look to your `docs` directory, rather than the project root.
111+
112+
1. Set the default `working-directory` param for the build job.
113+
114+
```yaml
115+
build:
116+
runs-on: ubuntu-latest
117+
defaults:
118+
run:
119+
working-directory: docs
120+
```
121+
122+
2. Set the `working-directory` param for the Setup Ruby step.
123+
124+
```yaml
125+
- name: Setup Ruby
126+
uses: ruby/setup-ruby@v1
127+
with:
128+
ruby-version: '3.1'
129+
bundler-cache: true
130+
cache-version: 0
131+
working-directory: '${{ github.workspace }}/docs'
132+
```
133+
134+
3. Set the path param for the Upload artifact step:
135+
136+
```yaml
137+
- name: Upload artifact
138+
uses: actions/upload-pages-artifact@v1
139+
with:
140+
path: "docs/_site/"
141+
```
142+
143+
4. Modify the trigger so that only changes within the `docs` directory start the workflow. Otherwise, every change to your project (even those that don't affect the docs) would trigger a new site build and deploy.
144+
145+
```yaml
146+
on:
147+
push:
148+
branches:
149+
- "main"
150+
paths:
151+
- "docs/**"
152+
```
153+
154+
## Licensing and Attribution
155+
156+
This repository is licensed under the [MIT License]. You are generally free to reuse or extend upon this code as you see fit; just include the original copy of the license (which is preserved when you "make a template"). While it's not necessary, we'd love to hear from you if you do use this template, and how we can improve it for future use!
157+
158+
The deployment GitHub Actions workflow is heavily based on GitHub's mixed-party [starter workflows]. A copy of their MIT License is available in [actions/starter-workflows].
159+
160+
----
161+
162+
[^1]: [It can take up to 10 minutes for changes to your site to publish after you push the changes to GitHub](https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll#creating-your-site).
163+
164+
[Jekyll]: https://jekyllrb.com
165+
[Just the Docs]: https://just-the-docs.github.io/just-the-docs/
166+
[GitHub Pages]: https://docs.github.com/en/pages
167+
[GitHub Pages / Actions workflow]: https://github.blog/changelog/2022-07-27-github-pages-custom-github-actions-workflows-beta/
168+
[Bundler]: https://bundler.io
169+
[use this template]: https://github.com/just-the-docs/just-the-docs-template/generate
170+
[`jekyll-default-layout`]: https://github.com/benbalter/jekyll-default-layout
171+
[`jekyll-seo-tag`]: https://jekyll.github.io/jekyll-seo-tag
172+
[MIT License]: https://en.wikipedia.org/wiki/MIT_License
173+
[starter workflows]: https://github.com/actions/starter-workflows/blob/main/pages/jekyll.yml
174+
[actions/starter-workflows]: https://github.com/actions/starter-workflows/blob/main/LICENSE

_config.yml

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
title: CRUP
2+
description: A starter template using the Just the Docs theme
3+
theme: just-the-docs
4+
5+
# Where the site will live
6+
url: "https://anikasikka.github.io"
7+
baseurl: "/crup" # VERY IMPORTANT for project repos
8+
9+
# Add a GitHub link in the header
10+
aux_links:
11+
"View on GitHub": "https://github.com/anikasikka/crup"

_sass/color_schemes/custom.scss

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
@media (max-width: $content-width) {
2+
.content-nav {
3+
display: none;
4+
}
5+
}

docs/syllabus.md

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
title: Syllabus
3+
nav_order: 2
4+
layout: home
5+
---
6+
7+
## Syllabus
8+
9+
### Course Format
10+
- **Length**: 3 hours, once a week, in person (or hybrid, depending on availability).
11+
- **Time & Date**: Saturday or Sunday from 10am–1pm.
12+
13+
### Contact Information
14+
- **EdVPs**: Patrick Mendoza ([email protected]), Anika Sikka ([email protected])
15+
- **Mentored PMs**: Sarika Pasumarthy ([email protected]), Eduardo Lopez ([email protected])
16+
17+
### Prerequisites
18+
- Taken or concurrently enrolled in **CS 61A / Data 8** OR have previous coding experience
19+
- No prior industry experience
20+
- Little to no prior web dev experience
21+
- Completed **1 or fewer upper-division CS/Data Science technical courses** at UC Berkeley
22+
23+
### Desired Course Outcomes
24+
By the end of the 12 weeks, we hope you:
25+
- Are comfortable programming in **Python, JavaScript, HTML, CSS, and SQL**
26+
- Know common data structures (Arrays, LinkedLists, Trees, HashTables)
27+
- Are familiar with frameworks such as **React, Node.js, NPM, PyTorch, Pandas, NumPy, scikit-learn**
28+
- Have a basic understanding of **Databases**
29+
- Understand fundamental ML/AI concepts (optimization, neural networks)
30+
- Feel comfortable working in a **team environment**, similar to industry
31+
32+
### Course Content
33+
The course will roughly follow this outline (subject to change based on member needs, popularity, and resources):
34+
1. Programming in Python
35+
2. Data Structures
36+
3. SQL and Databases
37+
4. Introduction to SWE
38+
5. Math for ML
39+
6. Classical ML
40+
7. Deep Learning
41+
8. Introduction to MLE
42+
43+
### Course Outline
44+
- **Weeks 1–4**: Welcome! & Intro to Programming in Python, Data Structures, Web Development, and Introduction to SWE
45+
- **Weeks 5–8**: Databases, and Math for ML
46+
- **Weeks 9–12**: Classical ML, Deep Learning, and Introduction to MLE
47+
48+
### Homeworks
49+
Throughout the course, we’ll be releasing homeworks that accompany lectures.
50+
- **Deadline policy**: Homework must be submitted **before the next lecture** (no rolling extensions).
51+
- **Homework parties**: Weekly, right after lecture — a space to ask questions and work together with your fellow members.
52+
53+
⚠️ Failure to adhere to the above policies may impact your eligibility to become a **client developer** the following semester and to attend **Codebase social events**.
54+
55+
### Midterm
56+
Before switching to the ML portion of the curriculum, you’ll take a **60-minute midterm**.
57+
- Mirrors lecture examples & homework problems
58+
- Not designed to trick you — just to help us see how to best support the class
59+
- Scores will not be scrutinized heavily
60+
- 🎉 Expect some festivities after the exam!
61+
62+
### Final Project
63+
You’ll complete a **final course project** in teams of **3–4 people** (with 1–2 client devs and 1–2 mentored devs).
64+
- **Showcase**: At Codebase’s banquet, where you’ll present everything you’ve learned ⭐⭐⭐
65+
- **Requirements**: Must incorporate full stack, databases, SWE practices, and machine learning
66+
- **Logistics**: Details announced in **Week 10**
67+
68+
👉 Think of an issue that matters to you — in your life, your community, or the world — and build a **tech-powered solution**!

0 commit comments

Comments
 (0)