Code for Kansas City Website
Clone or download
Pull request Compare This branch is 404 commits ahead of Code4HR:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
_includes
_layouts
_posts
blog
css
fonts
images
js
misc
people
presentations/project-centering-2015-07-27
project-hub
save-hackkc
tests/spec
.gitignore
101 Hacking - 2018.pdf
101Hacking.pdf
CNAME
Clinnovation_LTPP_LTL_Poster.jpg
README.md
Report-Out-Recruitment-2016.html
_config.yml
about.md
bower.json
code-of-conduct.md
codeacross2016-data.html
codeacross2016-projects.html
codeacross2016.html
delivered.md
favicon.ico
hackkc-code-of-conduct.md
hackkc-faq.md
hackkc-how-to-contribute.md
hackkc.html
hackkc2016.html
hackkc2017.html
hackkc2018-discovery.html
hackkc2018.html
hackkc2018_draft1.html
hangout.html
header.html
header_ndoch.html
index.html
kck.pdf
ltpp-expungement.html
nav-bar.html
oldhack.html
orientation.md
p.html
package.json
past-events.html
paul.html
project.html
should-i-attend-hackkc.html
welcome.md
wh.html

README.md

Stories in Ready

code4hr.org

The website for the Code for Kansas City Brigade

Goals

  1. Explain what Code for KC is and the type of work we do.
  2. To celebrate our events, projects, and discussions!
  3. Encourage current and new members to participate with clear ways to get involved.
  4. Was forked from Code for Hampton Roads

Tech

Built using Jekyll, Bootstrap, and Google Sheets

Contributing

Running the Site Locally on Your Computer

To run the site locally on your own computer (most helpful for previewing your own changes), you will need Jekyll installed (click here for Jekyll installation instructions.)

Fork and clone the repository, then run the following command in the root directory of the repo:

jekyll serve

or

jekyll serve --watch which will watch for changes to files.

Your computer should now be serving your local copy of the site at:

http://0.0.0.0:4000.

Submitting a Pull Request

  1. Fork the project.
  2. Remove CNAME
  3. Create a topic branch.
  4. Implement your feature or bug fix.
  5. Commit and push your changes.
  6. Submit a pull request.