Hosted on:
This repo holds the site/docs for Basil.js. The current state of development (develop branch) can be found here basiljs2.netlify.com
- Ruby >= 2.6
- Ruby Bundler
- Node.js >= 10
If there are changes to the API of Basil.js you can update the data on this repo as follows.
git pull [email protected]:basiljs/basiljs.github.io.git
cd basiljs.github.io
# get all branches
git fetch -a
# get into the develop branch
# this is currently the one that serves the page
# your pull request should also be against develop not master (at the moment)
git checkout -b develop origin/develop
# now make your new branch based on develop
git checkout -b chore/update-docs
# build the new data source for the site
# This will:
# - Pull the Basil.js' branch `develop` with npm from GitHub (eventually this should be the master, not the develop branch).
# - Generate the file `./build-scripts/api/data.json` from `./node_modules/basiljs/basil.js` using [documentation.js](http://documentation.js.org/).
# - Generate the following files for the index.
# + `./_data/categories.json`
# + `./_data/cats-and-subcats.json`
# - Also generate all the files for the subpages of `_source/reference`.
npm run build:api-markup
# After that you can just commit all the changes and push it the repo again. Netlify will take care of the Jekyll build.
# Only add the files you really want to.
# Adding all with `git add .` is acutally not the right way
# use gits interactive mode or some more specific paths then `.`
git add -i
git commit -m "chore: Update Basil.js api to latest state [Add your favorite emoji here]"
# push current HEAD to remote
git push -u origin HEAD
# Now go to the GitHub UI and create your PR
# Against the develop branch (not master).This repo holds the site/docs for Basil.js. The current state of development (develop branch) can be found here basiljs2.netlify.com
To build these docs we are using Webpack and Jekyll. You need both of these to develop on this.
- Create a new branch based on branch
develop(see the code above for a how to 👆). - Do your thing
- Create a pull request against develop
Netlify will create a branch and deploy preview for you and you can see your changes online. Every push to your branch will trigger a new build and will be linked on the PR page.
To develop locally take a look at the steps below. 👇
# Ruby/Jekyll setup
gem install bundler
bundle install
# Node Webpack setup
npm install
# or
npm ciTo run the full development process you need to run Webpack and Jekyll side by side. They are combined in a script call dev.
npm run devYour site will be served from http://0.0.0.0:4000
Most of the Jekyll liquid magic happens in ./_source.
To develop in this run:
# whenever you want to work on the markup/content
# (the --limit_posts 1 --incremental flags are needed
# because we have lots of pages and need to speedup the build)
bundle exec jekyll serve --livereload --limit_posts 1 --incremental
# in a second shell session runTo work on the Javascript and SCSS of the site you need to run
# when you develop on it
# (starts the webpack dev watch build toolchain)
npm run webpack:devTo add a new gallery item you can duplicate the folder _source/gallery/example-gallery-item
There Need to be two images present.
- thumbnail.png with a size of 320 × 180 px (this will be used in the gallery overview)
- splash.png with a size of 1280 × 720 px (this will be used on the start page if featured is true)
You also should replace all the values in the frontmatter of the index.md file.
Please set your project first to publish: false and also the featured: false to get a review by the maintainers.
Resize and crop multiple images using mogrify
mogrify -resize 320x180^ -gravity Center -extent 320x180 -quality 100 -format png ./*/thumbnail.jpg
Copyright (c) 2013-2020 Basil.js
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.