curriculum

The CYF Curriculum

https://github.com/codeyourfuture/curriculum

Science Score: 26.0%

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

  • 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 (11.1%) to scientific vocabulary

Keywords

cc-by-nc-sa-4 curriculum dpg hacktoberfest hugo javascript python sdg-4 sql swe
Last synced: 6 months ago · JSON representation

Repository

The CYF Curriculum

Basic Info
Statistics
  • Stars: 50
  • Watchers: 5
  • Forks: 96
  • Open Issues: 155
  • Releases: 0
Topics
cc-by-nc-sa-4 curriculum dpg hacktoberfest hugo javascript python sdg-4 sql swe
Created almost 3 years ago · Last pushed 6 months ago
Metadata Files
Readme Contributing Funding License Citation

README.md

Common Curriculum Platform

DPG Badge

[!TIP]
Our curriculum in action: https://curriculum.codeyourfuture.io
Curriculum platform docs: https://common.codeyourfuture.io

What is this?

This repo houses both our main curriculum content and our curriculum platform.

About our curriculum

Code Your Future is a volunteer-led community of tech professionals, and we teach people to code for free. We consider ourselves to be professionals helping other professionals, so our instructional approach is not hierarchical, and we encourage our volunteers to test out new material early and often. Our main curriculum (the repo you're looking at now) threads a coherent line through all of this activity, so whatever worlds we explore, everyone can come back here to find out what to do next.

Our curriculum content is all open source, and our teaching style is flipped classroom. This means that anyone should be able to follow the curriculum content independently. We offer mentoring and support to help people work through it, but the content does not assume a teacher/mentor will be present for programme delivery.

Our Global Syllabus Team is responsible for the overall direction of the main curriculum. They decide the strategy and accept new tested content into the core. Find out more by learning how to contribute.

Our curriculum and our curriculum platform are tightly integrated with GitHub. We want our learners to know how to use Git and GitHub and how modern development practices work, so we do almost everything right on GitHub. Learners submit their work by creating a pull request to the project repo. They plan their work using GitHub Projects, and they track their progress on the issues. We code review via the GitHub PR interface, and we have some automation and unit testing on quizzes and exercises/problems.

The curriculum content is developed in the Hugo module /common-content. This content is all headless blocks. It doesn't create any pages on your site unless you call it somewhere.

About the curriculum platform

Our self-developed curriculum platform is called Common. It is a white label multi-tenant platform for us and our code school friends to use to manage our curricula. It's built on top of Hugo and Netlify CMS.

The platform, layout, styles and components are all developed in the Hugo module /common-theme.

Multi-language support is provided by Hugo's i18n support.

Common is tightly integrated with GitHub. Really the main content should always be project work in GitHub repositories, and any site generated with Common should be a viewer for that content.

Each org or team configures its own Hugo site that mounts the common theme and content modules, and then makes any customisations they need and deploys it wherever they want. You can use any repo to do this and your site can be as simple as a hugo.toml and a content/_index.md. We'd love for you to use Common, too!

Examples

  • https://curriculum.codeyourfuture.io/
  • https://projects.codeyourfuture.io/
  • https://workshops.codeyourfuture.io/
  • https://programming.codeyourfuture.io/
  • https://curriculum.codeyourfuture.io/guides/
  • https://launch.codeyourfuture.io/
  • https://piscine.codeyourfuture.io/
  • https://sdc.codeyourfuture.io/
  • https://curriculum.migracode.org/

Developing a site

To develop a specific site, cd into the relevant sub-directory and follow the instructions in the README.md file.

To build a new site

  1. In the root of this repo, or in your own repo, run:

bash hugo new site org-{your-org-name} cd org-{your-org-name}

  1. Initialise your new site as a hugo module, as only modules can import modules:

zsh hugo mod init github.com/{your-org}/{your-repo}/{your-module}

Then add the common theme and content modules as hugo modules to hugo.toml:

toml [module] [[module.imports]] path = "github.com/CodeYourFuture/curriculum/common-theme" [[module.imports]] path = "github.com/CodeYourFuture/curriculum/common-content" [[module.imports.mounts]] source = "en" target = "content"

Look at the org-cyf and org-cyf-tracks examples for more details and options.

To customise the CSS, make a dir assets/custom-theme and throw any SCSS in there. It will be compiled and added last.

To add site logo/s, make a dir and add svgs to assets/custom-images/site-logo/. They will be added to the site header.

Add your content to content/ and customise the site config in config.toml. Please contribute any improvements you make back to the common theme and content modules.

For each module you import, add a replace directive to your go.mod file - if you forget to do this, you won't get live updates to your site when shared content changes. CI will remind you if you forget.

To locally develop your site

Check org-cyf/README.md on how to set up your local environment. Once that is done you can cd into the site you wish to develop, and run npm run start:dev to get a live preview.

Owner

  • Name: CodeYourFuture
  • Login: CodeYourFuture
  • Kind: organization
  • Email: contact@codeyourfuture.io
  • Location: London, Glasgow, Manchester, Birmingham, Rome, Cape Town

Coding School For Under-Represented People in Tech

Citation (CITATION.cff)


      

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 334
  • Total pull requests: 600
  • Average time to close issues: 2 months
  • Average time to close pull requests: 9 days
  • Total issue authors: 42
  • Total pull request authors: 55
  • Average comments per issue: 0.83
  • Average comments per pull request: 4.35
  • Merged pull requests: 413
  • Bot issues: 0
  • Bot pull requests: 6
Past Year
  • Issues: 163
  • Pull requests: 343
  • Average time to close issues: 20 days
  • Average time to close pull requests: 3 days
  • Issue authors: 20
  • Pull request authors: 44
  • Average comments per issue: 0.82
  • Average comments per pull request: 5.73
  • Merged pull requests: 224
  • Bot issues: 0
  • Bot pull requests: 6
Top Authors
Issue Authors
  • illicitonion (100)
  • SallyMcGrath (79)
  • moneyinthesky (34)
  • Dedekind561 (31)
  • kfklein15 (22)
  • Ara225 (10)
  • 40thieves (9)
  • fcaroline2020 (7)
  • pseudopilot (6)
  • ZacheeNiyokwizera (6)
  • AmyCYF (4)
  • JayMayer (3)
  • PERicci (3)
  • metinbaris (2)
  • esma-g (2)
Pull Request Authors
  • illicitonion (224)
  • SallyMcGrath (197)
  • kfklein15 (47)
  • Dedekind561 (43)
  • moneyinthesky (17)
  • 40thieves (12)
  • fcaroline2020 (10)
  • cjyuan (9)
  • LaraHuzjan (9)
  • dependabot[bot] (8)
  • sztupy (8)
  • metinbaris (6)
  • Ara225 (5)
  • sampennington (5)
  • AmyCYF (3)
Top Labels
Issue Labels
ITP (55) ITD (23) :gear: good first issue (16) :gear: bug (15) StrategyProgramme (14) SDC (13) up-for-grabs (9) help wanted (7) hacktoberfest (7) discussion (5) probably obsolete (5) :pencil2: Rewrite (5) blocked (4) 🐇 Size Small (3) 🔑 Priority Key (3) Piscine (3) CYF lore (2) 🎯 Topic Time Management (2) Hugo lore (2) refactor (1) :eyes: Review Testing (1) regex (1) :brain: Prep work (1) :eyes: Review Requirements (1) 🐂 Size Medium (1) 🏝️ Priority Stretch (1) 🎯 Topic Programming Fundamentals (1) 🎯 Topic Functional Programming (1) SDG-4 (1) 🎯 Topic Teamwork (1)
Pull Request Labels
ITP (11) dependencies (8) :gear: bug (6) blocked (3) pending_publish (3) draft (2) ITD (1) :brain: Prep work (1) 🎯 Topic Functional Programming (1) pending_review (1) decap-cms/draft (1) probably obsolete (1) Hugo lore (1) discussion (1)

Packages

  • Total packages: 1
  • Total downloads: unknown
  • Total dependent packages: 0
  • Total dependent repositories: 0
  • Total versions: 0
proxy.golang.org: github.com/CodeYourFuture/curriculum/tooling/go
  • Versions: 0
  • Dependent Packages: 0
  • Dependent Repositories: 0
Rankings
Forks count: 3.5%
Average: 5.4%
Dependent packages count: 5.9%
Stargazers count: 6.0%
Dependent repos count: 6.2%
Last synced: 8 months ago

Dependencies

package-lock.json npm
  • @codemirror/autocomplete 6.7.1
  • @codemirror/commands 6.2.4
  • @codemirror/lang-javascript 6.1.8
  • @codemirror/language 6.7.0
  • @codemirror/lint 6.2.1
  • @codemirror/search 6.4.0
  • @codemirror/state 6.2.0
  • @codemirror/view 6.12.0
  • @lezer/common 1.0.2
  • @lezer/highlight 1.1.4
  • @lezer/javascript 1.4.3
  • @lezer/lr 1.3.4
  • codemirror 6.0.1
  • crelt 1.0.6
  • prettier 2.8.8
  • prettier-plugin-go-template 0.0.13
  • style-mod 4.0.3
  • ulid 2.3.0
  • w3c-keyname 2.2.7
package.json npm
  • @codemirror/lang-javascript ^6.1.8
  • codemirror ^6.0.1
  • prettier ^2.8.8
  • prettier-plugin-go-template ^0.0.13