Storing all documents(paperworks, Wiki, etc) for Website rebuilding project of Korean-American Scientists and Engineers Association - Wisconsin Chapter
After intense research on various static website builders, we decide to use Jekyll
The code related with this documentation is on repository KSEAWeb
All manuals of End-Users are located under UserGuide directory.
Last Update: Jun. 18. 2020
As this repository has been changed to public, I set some rules for pushing chnages to this repository
Permission granted to push directly to master
Someone who are responsible for code review and merge the pull request from others. But, still not granted direct push permission to master branch.
Follow the procedures written on Collaborators (Developers).
You are not allowed to pull directly to master, but you can make a new branch and write code there.
After you make new branch with descriptive name including your gitHub Username or FirstName, you should make a pull request to master. (example of branch name: Hyecheol_JekyllInstallProcedure
)
After making a pull request, CodeOnwer will check your code and merge it to master after review. At least one review is requried.
Note that if you submit more than one PRs from Repository, only the latest PR will be reviewed (others will be deleted). If you submit incompleted work, you can resubmit the PR after you finish your work. All new branches must be created based on the features you are working on.
NAME_DESCRIPTION
)You are not allowed to make any changes directly on this repository, but you can still read code and make fork of this code.
To make some contribution, please fork this repository and work there. Note that the the forked repository name must contains this repository name with short descriptions (Forked Repository name example: KSEAWebDocuments_JekyllInstallProcedure
)
After that, you can submit a pull request to this repository.
The procedures after you submit the pull request is same as collaborators'. Read the Collaborators' Guideline located above.
RepoName_DESCRIPTION
, On GitHub Web)To maintain high productivity of team and properly compensate for the contribution toward this project, we decided to calculate each person's contribution rate.
For each sub-projects and small tasks, score will be set based on the difficulty and expected work-hours to finish it. After each task finished, the score of the task will be divided to the participants of that task considering github statistics (number of commits, number of code line editted, and so on) and other adjustments.
Score will be maintained on separated ScoreBoard documents.
Depending on the score of contribution, contribution Badge will be given. By earning each contribution badge, some benefits will be given to each participants. Contributors without badge will not receive any benefit.
The estimated plan for this project is illustrated below
Contain other useful documents that is relevant to developing website using Jekyll
Containing design of the site, all of Desktop and Mobile site.
Only final exported prototype will be stored, the working copy is maintained on the other private repository.
Desktop Design
Mobile Design
Containing document related to using (installing) Jekyll
Compare Data File Types
Supplement of Directory Structure
Write about various type of data files (YAML, JSON, CSV), which jekyll uses to store variables(data) of website.
Directory Structure
Contains information of basic Jekyll's structure.
Write on how it works and how each files and directory (the components) are working to generate the website.
Process of Generating Theme
Review the overall procedure of making Jekyll Theme
Error While Installing Jekyll
This file has been generated to report errors while installing Jekyll, and report the solutions for those.
Jekyll Install Procedure (Ubuntu)
Containing procedures to install Jekyll, from the beginning (setting up the requirements)
Conduct research on the well-known static website builders (The one that receive more than 10K starts on github, data retrieved from staticgen
ComparingLanguages.md
As a further research, we compared three languages that used by the analyzed static website builders
Comparing Go, Ruby, JavaScript(Node.JS)