Welcome to the code repository for the BEN Website!
This project was made with Github Pages, Jekyll, and Materialize (not version 1.0). If you are unfamiliar with these tools, read through the documentation. Pay attention to all of the components and styles available to you.
Each folder is divided into parent links, its sub-links and the SCSS / compiled CSS that goes along with it.
Repeated sections, like the Footer and Header are in the Components section and are loaded through js/main.js
.
- Knowledge of SCSS and CSS
- Use of the CLI
- How to FORK GitHub repositories, close issues, make decent commits, and pull requests
- Use of a text editor like Atom or Sublime
Technically, you could open up the index page and follow from there, but if you'd like for things to update on demand to make development easier, follow these steps:
-
Fork the repo at
https://github.com/blockchainedu/ben-website
-
Clone your repo:
$ git clone [email protected]:<username>/ben-website.git
- Create a new branch:
$ git checkout -b develop-<some-new-feature>
- Install the project's requirements. Ruby must be installed. Full instructions here: https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/
$ gem install bundler
$ bundle install
- Start the website up:
$ bundle exec jekyll serve
- Go to http://localhost:4000 if it doesn't load automatically.
SCSS is a CSS preprocessing language [and the latest version of Sass (Syntactically Awesome Style Sheets) syntax], which means it makes it easier to write CSS for the front-end. You can use variables, nest selectors, create mixins, etc. You can learn more about SCSS at http://sass-lang.com/documentation/file.SCSS_FOR_SASS_USERS.html
.
You will see that there are several SCSS and CSS files in the project. The CSS has been compiled from the SCSS files.
If you're developing with npm start
, then your scss files should be compiled into minified css files automatically.
If you have any difficulties with setup, do not hesitate to contact us @ [email protected].
- Choose an issue for the project to work on.
- Make sure you are in your own development branch (should be titled
development-(yourName)
) - When you want to commit something that will close an issue, you must use ONE of the keywords
close
,closes
,closed
,fix
,fixes
,fixed
,resolve
,resolves
, ORresolved
followed by the issue number to close it. I.e.Closes #10 - Add any other details here
. Learn more about closing issues at GitHub Help - Closing Issues using Keywords - When you are ready to share your changes with the organization, follow the instructions at GitHub Help - Creating a Pull Request.
- The organization will review your pull request and merge changes if approved.
- Pat yourself on the back for contributing!