计算机科学与技术网页设计与制作

# [Basically Basic Jekyll Theme][1] [](https://github.com/mmistakes/jekyll-theme-basically-basic/blob/master/LICENSE) [](https://jekyllrb.com/) [](https://rubygems.org/gems/jekyll-theme-basically-basic) [](https://www.paypal.me/mmistakes) [](https://www.buymeacoffee.com/mmistakes) Basically Basic is a [Jekyll theme](https://jekyllrb.com/docs/themes/) meant as a substitute for the default [Minima](https://github.com/jekyll/minima), with a few enhancements thrown in for good measure: - Clean responsive design with [six customizable skins](#skin) - Curriculum Vitæ/Resume layout powered by [JSON data](http://registry.jsonresume.org/) - About page layout - Site-wide search provided by [Algolia](https://www.algolia.com/) or [Lunr](https://lunrjs.com/). - Disqus Comments and Google Analytics support - SEO best practices via [Jekyll SEO Tag](https://github.com/jekyll/jekyll-seo-tag/) **If you enjoy this theme, please consider sponsoring:** [](https://www.buymeacoffee.com/mmistakes) [](https://www.paypal.me/mmistakes) [![Basically Basic live preview][2]][1] [1]: https://mmistakes.github.io/jekyll-theme-basically-basic/ [2]: https://cloud.githubusercontent.com/assets/1376749/24117647/6dede894-0d81-11e7-9c2c-f19bea45e219.jpg (live preview) ## Installation If you're running Jekyll v3.5+ and self-hosting you can quickly install the theme as a Ruby gem. If you're hosting with GitHub Pages you can install as a remote theme or directly copy all of the theme files (see [structure](#structure) below) into your project. ### Ruby Gem Method 1. Add this line to your Jekyll site's `Gemfile`: ```ruby gem "jekyll-theme-basically-basic" ``` 2. Add this line to your Jekyll site's `_config.yml` file: ```yaml theme: jekyll-theme-basically-basic ``` 2. Then run [Bundler](http://bundler.io/) to install the theme gem and dependencies: ```terminal bundle install ``` ### GitHub Pages Method GitHub Pages has added [full support](https://github.com/blog/2464-use-any-theme-with-github-pages) for any GitHub-hosted theme. 1. Replace `gem "jekyll"` with: ```ruby gem "github-pages", group: :jekyll_plugins ``` 2. Run `bundle update` and verify that all gems install properly. 3. Add `remote_theme: "mmistakes/jekyll-theme-basically-basic@1.4.5"` to your `_config.yml` file. Remove any other `theme:` or `remote_theme:` entries. --- **Note:** Your Jekyll site should be viewable immediately at <http://USERNAME.github.io>. If it's not, you can force a rebuild by **Customizing Your Site** (see below for more details). If you're hosting several Jekyll based sites under the same GitHub username you will have to use Project Pages instead of User Pages. Essentially you rename the repo to something other than **USERNAME.github.io** and create a `gh-pages` branch off of `master`. For more details on how to set things up check [GitHub's documentation](https://help.github.com/articles/user-organization-and-project-pages/). #### Remove the Unnecessary If you forked or downloaded the `jekyll-theme-basically-basic` repo you can safely remove the following files and folders: - `.editorconfig` - `.gitattributes` - `.github` - `.scss-lint.yml` - `CHANGELOG.md` - `jekyll-theme-basically-basic.gemspec` - `LICENSE` - `Rakefile` - `README.md` - `screenshot.png` - `/docs` - `/example` ## Upgrading If you're using the Ruby Gem or remote theme versions of Basically Basic, upgrading is fairly painless. To check which version you are currently using, view the source of your built site and you should something similar to: ``` <!-- Basically Basic Jekyll Theme 1.4.5 Copyright 2017-2018 Michael Rose - mademistakes.com | @mmistakes Free for personal and commercial use under the MIT license https://github.com/mmistakes/jekyll-basically-theme/blob/master/LICENSE --> ``` At the top of every `.html` file, `/assets/css/main.css`, and `/assets/js/main.js`. ### Ruby Gem Simply run `bundle update` if you're using Bundler (have a `Gemfile`) or `gem update jekyll-theme-basically-basic` if you're not. ### Remote Theme Verify you have the [latest version](https://github.com/mmistakes/jekyll-theme-basically-basic/releases) assigned in `_config.yml` ``` remote_theme: "mmistakes/jekyll-theme-basically-basic@1.4.5" ``` Note: If `@x.x.x` is omitted the theme's current `master` branch will be used. It is advised to ["lock" `remote_theme`](https://github.com/benbalter/jekyll-remote-theme#declaring-your-theme) at a specific version to avoid introducing breaking changes to your site. The next step requires rebuilding your [GitHub Pages](https://pages.github.com/) site so it can pull down the latest theme updates. This can be achieved by pushing up a commit to your GitHub repo. An empty commit will get the job done too if you don't have anything to push at the moment: ```terminal git commit --allow-empty -m "Force rebuild of site" ``` ### Use Git If you want to get the most out of the Jekyll + GitHub Pages workflow, then you'll need to utilize Git. To pull down theme updates you must first ensure there's an upstream remote. If you forked the theme's repo then you're likely good to go. To double check, run `git remote -v` and verify that you can fetch from `origin https://github.com/mmistakes/jekyll-theme-basically-basic.git`. To add it you can do the following: ```terminal git remote add upstream https://github.com/mmistakes/jekyll-theme-basically-basic.git ``` #### Pull Down Updates Now you can pull any commits made to theme's `master` branch with: ```terminal git pull upstream master ``` Depending on the amount of customizations you've made after forking, there's likely to be merge conflicts. Work through any conflicting files Git flags, staging the changes you wish to keep, and then commit them. ### Update Files Manually Another way of dealing with updates is [downloading the theme](https://github.com/mmistakes/jekyll-theme-basically-basic/archive/master.zip) --- replacing your layouts, includes, and assets with the newer ones manually. To be sure that you don't miss any changes it's probably a good idea to review the theme's [commit history](https://github.com/mmistakes/jekyll-theme-basically-basic/commits/master) to see what's changed since. Here's a quick checklist of the important folders/files you'll want to be mindful of: | Name | | | ---- | --- | | `_layouts` | Replace all. Apply edits if you customized any layouts. | | `_includes` | Replace all. Apply edits if you customized any includes. | | `assets` | Replace all. Apply edits if you customized stylesheets or scripts. | | `_sass` | Replace all. Apply edits if you customized Sass partials. | | `_data/theme.yml` | Safe to keep. Verify that there were no major structural changes or additions. | | `_config.yml` | Safe to keep. Verify that there were no major structural changes or additions. | --- **Note:** If you're not seeing the latest version, be sure to flush browser and CDN caches. Depending on your hosting environment older versions of `/assets/css/main.css`, `/assets/js/main.js`, or `*.html` may be cached. ## Structure Layouts, includes, Sass partials, and data files are all placed in their default location