init commit

.bundle/config

@@ -0,0 +1,2 @@
+---
+BUNDLE_PATH: "vendor/bundle"

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/CONTRIBUTING.md

@@ -0,0 +1,17 @@
+# Contributing Guidelines
+
+Want to contribute to this repo? Great! We  :heart:  contributions. Just make sure to follow these guidelines.
+
+## New Feature or a Bug Fix?
+1. Fork the repo (you can ignore this step if you are a part of the HackCU team)
+2. Create a new branch with a descriptive name of the feature or the bug you are fixing.
+3. If you are a part of the HackCU team, push the branch to the remote so that others know that you are working on this branch. Otherwise, create a new issue mentioning that you would like to add a new feature or fix a bug you noticed. This lets us know that someone is already helping us fix the issue!
+4. Make changes and commit them. Your commit messages should be descriptive and imperative. Read [this](http://who-t.blogspot.com/2009/12/on-commit-messages.html) for guidelines.
+5. Test locally and make sure the website functions properly and you didn't break anything.
+6. Create a pull request with a descriptive title. Clearly document any changes you made. You should be able to explain why you made those changes.
+
+## Working on the Next Release?
+1. Work on the `dev` or `develop` branch
+2. Test locally and make sure the website functions properly and you didn't break anything.
+3. Create a pull request with a descriptive title. Clearly document any changes you made. You should be able to explain why you made those changes.
+

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,24 @@
+<!-- This form is for bug reports and feature requests-->
+
+## Is this a BUG REPORT or FEATURE REQUEST?
+
+
+## What happened
+<!--(Include screenshots when possible)-->
+
+## What you expected to happen
+
+## How to reproduce it (as minimally and precisely as possible)
+
+
+## Anything else we need to know?
+
+## Environment
+- Browser version (Ex: Google Chrome 62.0.3202.94 (64-bit)...):
+- Domain: 
+- Others:
+
+(Optional)
+- Ruby version (e.g. `ruby --version`)
+- OS (e.g. from /etc/os-release):
+- Jekyll version (e.g. `jekyll --version`):

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,25 @@
+<!--  Thanks for sending a pull request!  Here are some tips for you:
+1. If this is your first time, read our contributor guidelines  https://github.com/hackcu/splash-page/blob/master/.github/CONTRIBUTING.md
+-->
+
+## What this PR does / why we need it
+
+A few sentences describing the overall goals of the pull request's commits.
+
+## Related Issues
+<!--(optional) Fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged)-->
+
+Fixes #
+
+## Some questions
+<!-- You can leave this and check them once the PR has been created. -->
+
+- [ ] I have read the contributing guidelines
+- [ ] I abide by this repository Code of Conduct
+
+## Special notes for your reviewer
+
+(optional)
+
+## Additional Notes
+Do you want to add anything else? We :heart: to hear your opinions!

.gitignore

@@ -0,0 +1,4 @@
+.idea
+.DS_Store
+_site
+vendor

CNAME

@@ -0,0 +1 @@
+splash.hackcu.org

Gemfile

@@ -0,0 +1,8 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+
+gem "jekyll"

Gemfile.lock

@@ -0,0 +1,63 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    addressable (2.6.0)
+      public_suffix (>= 2.0.2, < 4.0)
+    colorator (1.1.0)
+    concurrent-ruby (1.1.4)
+    em-websocket (0.5.1)
+      eventmachine (>= 0.12.9)
+      http_parser.rb (~> 0.6.0)
+    eventmachine (1.2.7)
+    ffi (1.10.0)
+    forwardable-extended (2.6.0)
+    http_parser.rb (0.6.0)
+    i18n (0.9.5)
+      concurrent-ruby (~> 1.0)
+    jekyll (3.8.5)
+      addressable (~> 2.4)
+      colorator (~> 1.0)
+      em-websocket (~> 0.5)
+      i18n (~> 0.7)
+      jekyll-sass-converter (~> 1.0)
+      jekyll-watch (~> 2.0)
+      kramdown (~> 1.14)
+      liquid (~> 4.0)
+      mercenary (~> 0.3.3)
+      pathutil (~> 0.9)
+      rouge (>= 1.7, < 4)
+      safe_yaml (~> 1.0)
+    jekyll-sass-converter (1.5.2)
+      sass (~> 3.4)
+    jekyll-watch (2.1.2)
+      listen (~> 3.0)
+    kramdown (1.17.0)
+    liquid (4.0.1)
+    listen (3.1.5)
+      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.7)
+      ruby_dep (~> 1.2)
+    mercenary (0.3.6)
+    pathutil (0.16.2)
+      forwardable-extended (~> 2.6)
+    public_suffix (3.0.3)
+    rb-fsevent (0.10.3)
+    rb-inotify (0.10.0)
+      ffi (~> 1.0)
+    rouge (3.3.0)
+    ruby_dep (1.5.0)
+    safe_yaml (1.0.4)
+    sass (3.7.3)
+      sass-listen (~> 4.0.0)
+    sass-listen (4.0.0)
+      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.7)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  jekyll
+
+BUNDLED WITH
+   1.16.0

LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2017 HackCU
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

README.md

@@ -0,0 +1,42 @@
+<br>
+<p align="center">
+  <img alt="HackCU V" src="https://github.com/HackCU/splash-page/blob/master/img/hackcu_black.png" width="200"/>
+</p>
+<br>
+
+Off-season static page for HackCU. Allows users to subscribe to email list to be notified when applications get released.
+
+# Run project
+
+Needs: Ruby, `bundle`
+
+## Local 
+
+1. `git clone https://github.com/hackcu/splash-page && cd splash-page`
+2. `bundle install`
+3. `bundle exec jekyll serve --watch`
+
+## Deploy
+
+1. Push changes to master
+2. There's no `2`
+
+Deployment is done automatically by [GitHub pages](https://pages.github.com/). You don't need to do anything else than pushing to master.
+
+# Want to contribute?
+Follow these [guidelines](.github/CONTRIBUTING.md)
+
+# External libraries used
+
+- [Bootstrap](https://getbootstrap.com/docs/3.3/)
+- [jQuery](https://jquery.com/)
+- [PixiJS](http://www.pixijs.com/)
+- [Space stars](https://github.com/Reynau/space)
+
+# Want to contribute?
+
+Please read our [Code of Conduct](.github/CODE_OF_CONDUCT.md), then follow these [guidelines](.github/CONTRIBUTING.md)
+
+# License
+
+MIT © HackCU

_config.yml

@@ -0,0 +1 @@
+subscribe_endpoint: https://api.hackcu.org/slack/invite/