├── assets ├── css │ └── style.scss ├── images │ ├── arrow-down.png │ └── octocat-small.png └── js │ └── scale.fix.js ├── .gitignore ├── thumbnail.png ├── Gemfile ├── script ├── bootstrap ├── cibuild ├── validate-html └── release ├── .travis.yml ├── another-page.md ├── _config.yml ├── _sass ├── dinky.scss ├── rouge-github.scss └── jekyll-theme-dinky.scss ├── .github ├── CODEOWNERS ├── workflows │ └── ci.yaml ├── no-response.yml ├── settings.yml ├── stale.yml └── config.yml ├── .rubocop.yml ├── _includes ├── head-custom.html └── head-custom-google-analytics.html ├── docs ├── SUPPORT.md ├── CODE_OF_CONDUCT.md └── CONTRIBUTING.md ├── jekyll-theme-dinky.gemspec ├── _layouts └── default.html ├── index.md ├── README.md └── LICENSE /assets/css/style.scss: -------------------------------------------------------------------------------- 1 | --- 2 | --- 3 | 4 | @import 'jekyll-theme-dinky'; 5 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | _site 2 | .sass-cache 3 | Gemfile.lock 4 | *.gem 5 | .jekyll-cache 6 | -------------------------------------------------------------------------------- /thumbnail.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/pages-themes/dinky/HEAD/thumbnail.png -------------------------------------------------------------------------------- /Gemfile: -------------------------------------------------------------------------------- 1 | # frozen_string_literal: true 2 | 3 | source "https://rubygems.org" 4 | 5 | gemspec 6 | -------------------------------------------------------------------------------- /script/bootstrap: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | set -e 4 | 5 | gem install bundler 6 | bundle install 7 | -------------------------------------------------------------------------------- /assets/images/arrow-down.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/pages-themes/dinky/HEAD/assets/images/arrow-down.png -------------------------------------------------------------------------------- /assets/images/octocat-small.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/pages-themes/dinky/HEAD/assets/images/octocat-small.png -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | language: ruby 2 | cache: bundler 3 | rvm: 2.6 4 | 5 | install: script/bootstrap 6 | script: script/cibuild 7 | -------------------------------------------------------------------------------- /another-page.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | --- 4 | 5 | ## Welcome to another page 6 | 7 | _yay_ 8 | 9 | [back](./) 10 | -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | title: Dinky theme 2 | description: Dinky is a red hot theme for GitHub Pages. 3 | show_downloads: true 4 | google_analytics: 5 | theme: jekyll-theme-dinky -------------------------------------------------------------------------------- /_sass/dinky.scss: -------------------------------------------------------------------------------- 1 | // Placeholder file. If your site uses 2 | // @import "{{ site.theme }}"; 3 | // Then using this theme with jekyll-remote-theme will work fine. 4 | @import "jekyll-theme-dinky"; 5 | -------------------------------------------------------------------------------- /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | # Require maintainer's :+1: for changes to the .github/ repo-config files 2 | # mainly due to https://github.com/probot/settings privilege escalation 3 | .github/* @pages-themes/maintainers 4 | -------------------------------------------------------------------------------- /.rubocop.yml: -------------------------------------------------------------------------------- 1 | inherit_gem: 2 | rubocop-github: 3 | - config/default.yml 4 | 5 | AllCops: 6 | Exclude: 7 | - _site/**/* 8 | - vendor/**/* 9 | 10 | Layout/LineLength: 11 | Enabled: false 12 | -------------------------------------------------------------------------------- /script/cibuild: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | set -e 4 | 5 | bundle exec jekyll build 6 | bundle exec htmlproofer ./_site --check-html --check-sri 7 | bundle exec rubocop -D --config .rubocop.yml 8 | bundle exec script/validate-html 9 | gem build jekyll-theme-dinky.gemspec 10 | -------------------------------------------------------------------------------- /_includes/head-custom.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | {% include head-custom-google-analytics.html %} 5 | 6 | 7 | 8 | 9 | 10 | -------------------------------------------------------------------------------- /.github/workflows/ci.yaml: -------------------------------------------------------------------------------- 1 | on: 2 | push: 3 | pull_request: 4 | types: [opened, synchronize] 5 | jobs: 6 | build: 7 | runs-on: ubuntu-latest 8 | name: script/cibuild 9 | steps: 10 | - uses: actions/checkout@v2 11 | - uses: ruby/setup-ruby@v1 12 | with: 13 | ruby-version: 2.7 14 | bundler-cache: true 15 | - name: build 16 | run: script/bootstrap 17 | - name: test 18 | run: script/cibuild 19 | -------------------------------------------------------------------------------- /_includes/head-custom-google-analytics.html: -------------------------------------------------------------------------------- 1 | {% if site.google_analytics %} 2 | 10 | {% endif %} 11 | -------------------------------------------------------------------------------- /assets/js/scale.fix.js: -------------------------------------------------------------------------------- 1 | fixScale = function(doc) { 2 | 3 | var addEvent = 'addEventListener', 4 | type = 'gesturestart', 5 | qsa = 'querySelectorAll', 6 | scales = [1, 1], 7 | meta = qsa in doc ? doc[qsa]('meta[name=viewport]') : []; 8 | 9 | function fix() { 10 | meta.content = 'width=device-width,minimum-scale=' + scales[0] + ',maximum-scale=' + scales[1]; 11 | doc.removeEventListener(type, fix, true); 12 | } 13 | 14 | if ((meta = meta[meta.length - 1]) && addEvent in doc) { 15 | fix(); 16 | scales = [.25, 1.6]; 17 | doc[addEvent](type, fix, true); 18 | } 19 | 20 | }; -------------------------------------------------------------------------------- /script/validate-html: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env ruby 2 | # frozen_string_literal: true 3 | 4 | require "w3c_validators" 5 | 6 | def validator(file) 7 | extension = File.extname(file) 8 | if extension == ".html" 9 | W3CValidators::NuValidator.new 10 | elsif extension == ".css" 11 | W3CValidators::CSSValidator.new 12 | end 13 | end 14 | 15 | def validate(file) 16 | puts "Checking #{file}..." 17 | 18 | path = File.expand_path "../_site/#{file}", __dir__ 19 | results = validator(file).validate_file(path) 20 | 21 | return puts "Valid!" if results.errors.empty? 22 | 23 | results.errors.each { |err| puts err.to_s } 24 | exit 1 25 | end 26 | 27 | validate "index.html" 28 | validate File.join "assets", "css", "style.css" 29 | -------------------------------------------------------------------------------- /.github/no-response.yml: -------------------------------------------------------------------------------- 1 | # Configuration for probot-no-response - https://github.com/probot/no-response 2 | 3 | # Number of days of inactivity before an Issue is closed for lack of response 4 | daysUntilClose: 14 5 | # Label requiring a response 6 | responseRequiredLabel: more-information-needed 7 | # Comment to post when closing an Issue for lack of response. Set to `false` to disable 8 | closeComment: > 9 | This issue has been automatically closed because there has been no response 10 | to our request for more information from the original author. With only the 11 | information that is currently in the issue, we don't have enough information 12 | to take action. Please reach out if you have or find the answers we need so 13 | that we can investigate further. 14 | -------------------------------------------------------------------------------- /docs/SUPPORT.md: -------------------------------------------------------------------------------- 1 | ## Where to get help 2 | 3 | If you think you've found a bug in the Dinky theme, please [check the existing issues](https://github.com/pages-themes/dinky/issues), and if no one has reported the problem, [open a new issue](https://github.com/pages-themes/dinky/issues/new). 4 | 5 | If you have a general question about the theme, how to implement it, or how to customize it for your site you have two options: 6 | 7 | 1. Search for your query on [`support.github.com`](https://support.github.com/?q=pages+Dinky+theme), which will also look for similar topics on [`github.community`](https://github.community/search?q=pages+Dinky+theme) 8 | 2. Ask your question of the Jekyll community on [talk.jekyllrb.com](https://talk.jekyllrb.com/) 9 | 3. [Contact GitHub Support](https://github.com/contact?form%5Bsubject%5D=GitHub%20Pages%20theme%20pages-themes/dinky) 10 | -------------------------------------------------------------------------------- /.github/settings.yml: -------------------------------------------------------------------------------- 1 | # Repository settings set via https://github.com/probot/settings 2 | 3 | repository: 4 | has_issues: true 5 | has_wiki: false 6 | has_projects: false 7 | has_downloads: false 8 | 9 | labels: 10 | - name: help wanted 11 | oldname: help-wanted 12 | color: 0e8a16 13 | - name: more-information-needed 14 | color: d93f0b 15 | - name: bug 16 | color: b60205 17 | - name: feature 18 | color: 1d76db 19 | - name: good first issue 20 | color: "5319e7" 21 | 22 | # Not currently implemented by probot/settings, but manually implemented in script/deploy 23 | branch_protection: 24 | restrictions: null 25 | enforce_admins: false 26 | required_status_checks: 27 | strict: true 28 | contexts: 29 | - "script/cibuild" # GitHub Actions CI workflow 30 | required_pull_request_reviews: 31 | require_code_owner_reviews: true 32 | -------------------------------------------------------------------------------- /.github/stale.yml: -------------------------------------------------------------------------------- 1 | # Configuration for probot-stale - https://github.com/probot/stale 2 | 3 | # Number of days of inactivity before an Issue or Pull Request becomes stale 4 | daysUntilStale: 60 5 | 6 | # Number of days of inactivity before a stale Issue or Pull Request is closed 7 | daysUntilClose: 7 8 | 9 | # Issues or Pull Requests with these labels will never be considered stale 10 | exemptLabels: 11 | - pinned 12 | - security 13 | 14 | # Label to use when marking as stale 15 | staleLabel: wontfix 16 | 17 | # Comment to post when marking as stale. Set to `false` to disable 18 | markComment: > 19 | This issue has been automatically marked as stale because it has not had 20 | recent activity. It will be closed if no further activity occurs. Thank you 21 | for your contributions. 22 | 23 | # Comment to post when closing a stale Issue or Pull Request. Set to `false` to disable 24 | closeComment: false 25 | 26 | # Limit to only `issues` or `pulls` 27 | # only: issues 28 | -------------------------------------------------------------------------------- /script/release: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | # Tag and push a release. 3 | 4 | set -e 5 | 6 | # Make sure we're in the project root. 7 | 8 | cd $(dirname "$0")/.. 9 | 10 | # Make sure the darn thing works 11 | 12 | bundle update 13 | 14 | # Build a new gem archive. 15 | 16 | rm -rf jekyll-theme-dinky-*.gem 17 | gem build -q jekyll-theme-dinky.gemspec 18 | 19 | # Make sure we're on the master branch. 20 | 21 | (git branch | grep -q 'master') || { 22 | echo "Only release from the master branch." 23 | exit 1 24 | } 25 | 26 | # Figure out what version we're releasing. 27 | 28 | tag=v`ls jekyll-theme-dinky-*.gem | sed 's/^jekyll-theme-dinky-\(.*\)\.gem$/\1/'` 29 | 30 | # Make sure we haven't released this version before. 31 | 32 | git fetch -t origin 33 | 34 | (git tag -l | grep -q "$tag") && { 35 | echo "Whoops, there's already a '${tag}' tag." 36 | exit 1 37 | } 38 | 39 | # Tag it and bag it. 40 | 41 | gem push jekyll-theme-dinky-*.gem && git tag "$tag" && 42 | git push origin master && git push origin "$tag" 43 | -------------------------------------------------------------------------------- /jekyll-theme-dinky.gemspec: -------------------------------------------------------------------------------- 1 | # frozen_string_literal: true 2 | 3 | Gem::Specification.new do |s| 4 | s.name = "jekyll-theme-dinky" 5 | s.version = "0.2.0" 6 | s.license = "CC0-1.0" 7 | s.authors = ["Diana Mounter", "GitHub, Inc."] 8 | s.email = ["opensource+jekyll-theme-dinky@github.com"] 9 | s.homepage = "https://github.com/pages-themes/dinky" 10 | s.summary = "Dinky is a Jekyll theme for GitHub Pages" 11 | 12 | s.files = `git ls-files -z`.split("\x0").select do |f| 13 | f.match(%r{^((_includes|_layouts|_sass|assets)/|(LICENSE|README)((\.(txt|md|markdown)|$)))}i) 14 | end 15 | 16 | s.required_ruby_version = ">= 2.4.0" 17 | 18 | s.platform = Gem::Platform::RUBY 19 | s.add_runtime_dependency "jekyll", "> 3.5", "< 5.0" 20 | s.add_runtime_dependency "jekyll-seo-tag", "~> 2.0" 21 | s.add_development_dependency "html-proofer", "~> 3.0" 22 | s.add_development_dependency "rubocop-github", "~> 0.16" 23 | s.add_development_dependency "w3c_validators", "~> 1.3" 24 | end 25 | -------------------------------------------------------------------------------- /.github/config.yml: -------------------------------------------------------------------------------- 1 | # Behaviorbot config. See https://github.com/behaviorbot/ for more information. 2 | # Note: Please Don't edit this file directly. 3 | # Edit https://github.com/pages-themes/maintenance-scripts instead. 4 | 5 | # Configuration for update-docs - https://github.com/behaviorbot/update-docs 6 | updateDocsComment: "Thanks for the pull request! If you are making any changes to the user-facing functionality, please be sure to update the documentation in the `README` or `docs/` folder alongside your change. :heart:" 7 | 8 | # Configuration for request-info - https://github.com/behaviorbot/request-info 9 | requestInfoReplyComment: Thanks for this. Do you mind providing a bit more information about what problem you're trying to solve? 10 | requestInfoLabelToAdd: more-information-needed 11 | 12 | # Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome 13 | #newIssueWelcomeComment: > 14 | # Welcome! 15 | 16 | # Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome 17 | newPRWelcomeComment: Welcome! Congrats on your first pull request to the Dinky theme. If you haven't already, please be sure to check out [the contributing guidelines](https://github.com/pages-themes/dinky/blob/master/docs/CONTRIBUTING.md). 18 | 19 | # Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge 20 | firstPRMergeComment: "Congrats on getting your first pull request to the Dinky theme merged! Without amazing humans like you submitting pull requests, we couldn’t run this project. You rock! :tada:

If you're interested in tackling another bug or feature, take a look at [the open issues](https://github.com/pages-themes/dinky/issues), especially those [labeled `help wanted`](https://github.com/pages-themes/dinky/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22)." 21 | -------------------------------------------------------------------------------- /_layouts/default.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | {% seo %} 8 | 9 | 10 | 11 | 14 | {% include head-custom.html %} 15 | 16 | 17 |
18 |
19 |

{{ site.title | default: site.github.repository_name }}

20 |

{{ site.description | default: site.github.project_tagline }}

21 | 22 | 29 | 30 | {% if site.github.is_project_page %} 31 |

This project is maintained by {{ site.github.owner_name }}

32 | {% endif %} 33 | 34 | {% if site.github.is_user_page %} 35 | 38 | {% endif %} 39 |
40 | 41 |
42 | {{ content }} 43 |
44 | 45 | 48 |
49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /index.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | --- 4 | 5 | Text can be **bold**, _italic_, or ~~strikethrough~~. 6 | 7 | [Link to another page](./another-page.html). 8 | 9 | There should be whitespace between paragraphs. 10 | 11 | There should be whitespace between paragraphs. We recommend including a README, or a file with information about your project. 12 | 13 | # Header 1 14 | 15 | This is a normal paragraph following a header. GitHub is a code hosting platform for version control and collaboration. It lets you and others work together on projects from anywhere. 16 | 17 | ## Header 2 18 | 19 | > This is a blockquote following a header. 20 | > 21 | > When something is important enough, you do it even if the odds are not in your favor. 22 | 23 | ### Header 3 24 | 25 | ```js 26 | // Javascript code with syntax highlighting. 27 | var fun = function lang(l) { 28 | dateformat.i18n = require('./lang/' + l) 29 | return true; 30 | } 31 | ``` 32 | 33 | ```ruby 34 | # Ruby code with syntax highlighting 35 | GitHubPages::Dependencies.gems.each do |gem, version| 36 | s.add_dependency(gem, "= #{version}") 37 | end 38 | ``` 39 | 40 | #### Header 4 41 | 42 | * This is an unordered list following a header. 43 | * This is an unordered list following a header. 44 | * This is an unordered list following a header. 45 | 46 | ##### Header 5 47 | 48 | 1. This is an ordered list following a header. 49 | 2. This is an ordered list following a header. 50 | 3. This is an ordered list following a header. 51 | 52 | ###### Header 6 53 | 54 | | head1 | head two | three | 55 | |:-------------|:------------------|:------| 56 | | ok | good swedish fish | nice | 57 | | out of stock | good and plenty | nice | 58 | | ok | good `oreos` | hmm | 59 | | ok | good `zoute` drop | yumm | 60 | 61 | ### There's a horizontal rule below this. 62 | 63 | * * * 64 | 65 | ### Here is an unordered list: 66 | 67 | * Item foo 68 | * Item bar 69 | * Item baz 70 | * Item zip 71 | 72 | ### And an ordered list: 73 | 74 | 1. Item one 75 | 1. Item two 76 | 1. Item three 77 | 1. Item four 78 | 79 | ### And a nested list: 80 | 81 | - level 1 item 82 | - level 2 item 83 | - level 2 item 84 | - level 3 item 85 | - level 3 item 86 | - level 1 item 87 | - level 2 item 88 | - level 2 item 89 | - level 2 item 90 | - level 1 item 91 | - level 2 item 92 | - level 2 item 93 | - level 1 item 94 | 95 | ### Small image 96 | 97 | ![Octocat](https://github.githubassets.com/images/icons/emoji/octocat.png) 98 | 99 | ### Large image 100 | 101 | ![Branching](https://guides.github.com/activities/hello-world/branching.png) 102 | 103 | 104 | ### Definition lists can be used with HTML syntax. 105 | 106 |
107 |
Name
108 |
Godzilla
109 |
Born
110 |
1952
111 |
Birthplace
112 |
Japan
113 |
Color
114 |
Green
115 |
116 | 117 | ``` 118 | Long, single-line code blocks should not wrap. They should horizontally scroll if they are too long. This line should be long enough to demonstrate this. 119 | ``` 120 | 121 | ``` 122 | The final element. 123 | ``` 124 | -------------------------------------------------------------------------------- /docs/CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | 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. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | 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. 28 | 29 | 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. 30 | 31 | ## Scope 32 | 33 | 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. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at opensource@github.com. 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. 38 | 39 | 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. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: http://contributor-covenant.org 46 | [version]: http://contributor-covenant.org/version/1/4/ 47 | -------------------------------------------------------------------------------- /_sass/rouge-github.scss: -------------------------------------------------------------------------------- 1 | .highlight table td { padding: 5px; } 2 | .highlight table pre { margin: 0; } 3 | .highlight .cm { 4 | color: #999988; 5 | font-style: italic; 6 | } 7 | .highlight .cp { 8 | color: #999999; 9 | font-weight: bold; 10 | } 11 | .highlight .c1 { 12 | color: #999988; 13 | font-style: italic; 14 | } 15 | .highlight .cs { 16 | color: #999999; 17 | font-weight: bold; 18 | font-style: italic; 19 | } 20 | .highlight .c, .highlight .cd { 21 | color: #999988; 22 | font-style: italic; 23 | } 24 | .highlight .err { 25 | color: #a61717; 26 | background-color: #e3d2d2; 27 | } 28 | .highlight .gd { 29 | color: #000000; 30 | background-color: #ffdddd; 31 | } 32 | .highlight .ge { 33 | color: #000000; 34 | font-style: italic; 35 | } 36 | .highlight .gr { 37 | color: #aa0000; 38 | } 39 | .highlight .gh { 40 | color: #999999; 41 | } 42 | .highlight .gi { 43 | color: #000000; 44 | background-color: #ddffdd; 45 | } 46 | .highlight .go { 47 | color: #888888; 48 | } 49 | .highlight .gp { 50 | color: #555555; 51 | } 52 | .highlight .gs { 53 | font-weight: bold; 54 | } 55 | .highlight .gu { 56 | color: #aaaaaa; 57 | } 58 | .highlight .gt { 59 | color: #aa0000; 60 | } 61 | .highlight .kc { 62 | color: #000000; 63 | font-weight: bold; 64 | } 65 | .highlight .kd { 66 | color: #000000; 67 | font-weight: bold; 68 | } 69 | .highlight .kn { 70 | color: #000000; 71 | font-weight: bold; 72 | } 73 | .highlight .kp { 74 | color: #000000; 75 | font-weight: bold; 76 | } 77 | .highlight .kr { 78 | color: #000000; 79 | font-weight: bold; 80 | } 81 | .highlight .kt { 82 | color: #445588; 83 | font-weight: bold; 84 | } 85 | .highlight .k, .highlight .kv { 86 | color: #000000; 87 | font-weight: bold; 88 | } 89 | .highlight .mf { 90 | color: #009999; 91 | } 92 | .highlight .mh { 93 | color: #009999; 94 | } 95 | .highlight .il { 96 | color: #009999; 97 | } 98 | .highlight .mi { 99 | color: #009999; 100 | } 101 | .highlight .mo { 102 | color: #009999; 103 | } 104 | .highlight .m, .highlight .mb, .highlight .mx { 105 | color: #009999; 106 | } 107 | .highlight .sb { 108 | color: #d14; 109 | } 110 | .highlight .sc { 111 | color: #d14; 112 | } 113 | .highlight .sd { 114 | color: #d14; 115 | } 116 | .highlight .s2 { 117 | color: #d14; 118 | } 119 | .highlight .se { 120 | color: #d14; 121 | } 122 | .highlight .sh { 123 | color: #d14; 124 | } 125 | .highlight .si { 126 | color: #d14; 127 | } 128 | .highlight .sx { 129 | color: #d14; 130 | } 131 | .highlight .sr { 132 | color: #009926; 133 | } 134 | .highlight .s1 { 135 | color: #d14; 136 | } 137 | .highlight .ss { 138 | color: #990073; 139 | } 140 | .highlight .s { 141 | color: #d14; 142 | } 143 | .highlight .na { 144 | color: #008080; 145 | } 146 | .highlight .bp { 147 | color: #999999; 148 | } 149 | .highlight .nb { 150 | color: #0086B3; 151 | } 152 | .highlight .nc { 153 | color: #445588; 154 | font-weight: bold; 155 | } 156 | .highlight .no { 157 | color: #008080; 158 | } 159 | .highlight .nd { 160 | color: #3c5d5d; 161 | font-weight: bold; 162 | } 163 | .highlight .ni { 164 | color: #800080; 165 | } 166 | .highlight .ne { 167 | color: #990000; 168 | font-weight: bold; 169 | } 170 | .highlight .nf { 171 | color: #990000; 172 | font-weight: bold; 173 | } 174 | .highlight .nl { 175 | color: #990000; 176 | font-weight: bold; 177 | } 178 | .highlight .nn { 179 | color: #555555; 180 | } 181 | .highlight .nt { 182 | color: #000080; 183 | } 184 | .highlight .vc { 185 | color: #008080; 186 | } 187 | .highlight .vg { 188 | color: #008080; 189 | } 190 | .highlight .vi { 191 | color: #008080; 192 | } 193 | .highlight .nv { 194 | color: #008080; 195 | } 196 | .highlight .ow { 197 | color: #000000; 198 | font-weight: bold; 199 | } 200 | .highlight .o { 201 | color: #000000; 202 | font-weight: bold; 203 | } 204 | .highlight .w { 205 | color: #bbbbbb; 206 | } 207 | .highlight { 208 | background-color: #f8f8f8; 209 | } 210 | -------------------------------------------------------------------------------- /docs/CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to the Dinky theme 2 | 3 | Hi there! We're thrilled that you'd like to contribute to the Dinky theme. Your help is essential for keeping it great. 4 | 5 | the Dinky theme is an open source project supported by the efforts of an entire community and built one contribution at a time by users like you. We'd love for you to get involved. Whatever your level of skill or however much time you can give, your contribution is greatly appreciated. There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, submitting bug reports and feature requests, helping other users by commenting on issues, or writing code which can be incorporated into the Dinky theme itself. 6 | 7 | Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests. 8 | 9 | 10 | ## Looking for support? 11 | 12 | We'd love to help. Check out [the support guidelines](SUPPORT.md). 13 | 14 | ## How to report a bug 15 | 16 | Think you found a bug? Please check [the list of open issues](https://github.com/pages-themes/dinky/issues) to see if your bug has already been reported. If it hasn't please [submit a new issue](https://github.com/pages-themes/dinky/issues/new). 17 | 18 | Here are a few tips for writing *great* bug reports: 19 | 20 | * Describe the specific problem (e.g., "widget doesn't turn clockwise" versus "getting an error") 21 | * Include the steps to reproduce the bug, what you expected to happen, and what happened instead 22 | * Check that you are using the latest version of the project and its dependencies 23 | * Include what version of the project your using, as well as any relevant dependencies 24 | * Only include one bug per issue. If you have discovered two bugs, please file two issues 25 | * Even if you don't know how to fix the bug, including a failing test may help others track it down 26 | 27 | **If you find a security vulnerability, do not open an issue. Please email security@github.com instead.** 28 | 29 | ## How to suggest a feature or enhancement 30 | 31 | If you find yourself wishing for a feature that doesn't exist in the Dinky theme, you are probably not alone. There are bound to be others out there with similar needs. Many of the features that the Dinky theme has today have been added because our users saw the need. 32 | 33 | Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and goals of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible, including describing the problem you're trying to solve. 34 | 35 | [Open an issue](https://github.com/pages-themes/dinky/issues/new) which describes the feature you would like to see, why you want it, how it should work, etc. 36 | 37 | 38 | 39 | ## Your first contribution 40 | 41 | We'd love for you to contribute to the project. Unsure where to begin contributing to the Dinky theme? You can start by looking through these "good first issue" and "help wanted" issues: 42 | 43 | * [Good first issues](https://github.com/pages-themes/dinky/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) - issues which should only require a few lines of code and a test or two 44 | * [Help wanted issues](https://github.com/pages-themes/dinky/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) - issues which may be a bit more involved, but are specifically seeking community contributions 45 | 46 | *p.s. Feel free to ask for help; everyone is a beginner at first* :smiley_cat: 47 | 48 | ## How to propose changes 49 | 50 | Here's a few general guidelines for proposing changes: 51 | 52 | * If you are making visual changes, include a screenshot of what the affected element looks like, both before and after. 53 | * Follow the [Jekyll style guide](https://ben.balter.com/jekyll-style-guide). 54 | * If you are changing any user-facing functionality, please be sure to update the documentation 55 | * Each pull request should implement **one** feature or bug fix. If you want to add or fix more than one thing, submit more than one pull request 56 | * Do not commit changes to files that are irrelevant to your feature or bug fix 57 | * Don't bump the version number in your pull request (it will be bumped prior to release) 58 | * Write [a good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) 59 | 60 | At a high level, [the process for proposing changes](https://guides.github.com/introduction/flow/) is: 61 | 62 | 1. [Fork](https://github.com/pages-themes/dinky/fork) and clone the project 63 | 2. Configure and install the dependencies: `script/bootstrap` 64 | 3. Make sure the tests pass on your machine: `script/cibuild` 65 | 4. Create a new branch: `git checkout -b my-branch-name` 66 | 5. Make your change, add tests, and make sure the tests still pass 67 | 6. Push to your fork and [submit a pull request](https://github.com/pages-themes/dinky/compare) 68 | 7. Pat your self on the back and wait for your pull request to be reviewed and merged 69 | 70 | **Interesting in submitting your first Pull Request?** It's easy! You can learn how from this *free* series [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github) 71 | 72 | ## Bootstrapping your local development environment 73 | 74 | `script/bootstrap` 75 | 76 | ## Running tests 77 | 78 | `script/cibuild` 79 | 80 | ## Code of conduct 81 | 82 | This project is governed by [the Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. 83 | 84 | ## Additional Resources 85 | 86 | * [Contributing to Open Source on GitHub](https://guides.github.com/activities/contributing-to-open-source/) 87 | * [Using Pull Requests](https://help.github.com/articles/using-pull-requests/) 88 | * [GitHub Help](https://help.github.com) 89 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # The Dinky theme 2 | 3 | [![.github/workflows/ci.yaml](https://github.com/pages-themes/dinky/actions/workflows/ci.yaml/badge.svg)](https://github.com/pages-themes/dinky/actions/workflows/ci.yaml) [![Gem Version](https://badge.fury.io/rb/jekyll-theme-dinky.svg)](https://badge.fury.io/rb/jekyll-theme-dinky) 4 | 5 | *Dinky is a Jekyll theme for GitHub Pages. You can [preview the theme to see what it looks like](http://pages-themes.github.io/dinky), or even [use it today](#usage).* 6 | 7 | ![Thumbnail of Dinky](thumbnail.png) 8 | 9 | ## Usage 10 | 11 | To use the Dinky theme: 12 | 13 | 1. Add the following to your site's `_config.yml`: 14 | 15 | ```yml 16 | remote_theme: pages-themes/dinky@v0.2.0 17 | plugins: 18 | - jekyll-remote-theme # add this line to the plugins list if you already have one 19 | ``` 20 | 21 | 2. Optionally, if you'd like to preview your site on your computer, add the following to your site's `Gemfile`: 22 | 23 | ```ruby 24 | gem "github-pages", group: :jekyll_plugins 25 | ``` 26 | 27 | ## Customizing 28 | 29 | ### Configuration variables 30 | 31 | Dinky will respect the following variables, if set in your site's `_config.yml`: 32 | 33 | ```yml 34 | title: [The title of your site] 35 | description: [A short description of your site's purpose] 36 | ``` 37 | 38 | Additionally, you may choose to set the following optional variables: 39 | 40 | ```yml 41 | show_downloads: ["true" or "false" (unquoted) to indicate whether to provide a download URL] 42 | google_analytics: [Your Google Analytics tracking ID] 43 | ``` 44 | 45 | ### Stylesheet 46 | 47 | If you'd like to add your own custom styles: 48 | 49 | 1. Create a file called `/assets/css/style.scss` in your site 50 | 2. Add the following content to the top of the file, exactly as shown: 51 | ```scss 52 | --- 53 | --- 54 | 55 | @import "{{ site.theme }}"; 56 | ``` 57 | 3. Add any custom CSS (or Sass, including imports) you'd like immediately after the `@import` line 58 | 59 | *Note: If you'd like to change the theme's Sass variables, you must set new values before the `@import` line in your stylesheet.* 60 | 61 | ### Layouts 62 | 63 | If you'd like to change the theme's HTML layout: 64 | 65 | 1. For some changes such as a custom `favicon`, you can add custom files in your local `_includes` folder. The files [provided with the theme](https://github.com/pages-themes/dinky/tree/master/_includes) provide a starting point and are included by the [original layout template](https://github.com/pages-themes/dinky/blob/master/_layouts/default.html). 66 | 2. For more extensive changes, [copy the original template](https://github.com/pages-themes/dinky/blob/master/_layouts/default.html) from the theme's repository
(*Pro-tip: click "raw" to make copying easier*) 67 | 3. Create a file called `/_layouts/default.html` in your site 68 | 4. Paste the default layout content copied in the first step 69 | 5. Customize the layout as you'd like 70 | 71 | ### Customizing Google Analytics code 72 | 73 | Google has released several iterations to their Google Analytics code over the years since this theme was first created. If you would like to take advantage of the latest code, paste it into `_includes/head-custom-google-analytics.html` in your Jekyll site. 74 | 75 | ### Overriding GitHub-generated URLs 76 | 77 | Templates often rely on URLs supplied by GitHub such as links to your repository or links to download your project. If you'd like to override one or more default URLs: 78 | 79 | 1. Look at [the template source](https://github.com/pages-themes/dinky/blob/master/_layouts/default.html) to determine the name of the variable. It will be in the form of `{{ site.github.zip_url }}`. 80 | 2. Specify the URL that you'd like the template to use in your site's `_config.yml`. For example, if the variable was `site.github.url`, you'd add the following: 81 | ```yml 82 | github: 83 | zip_url: http://example.com/download.zip 84 | another_url: another value 85 | ``` 86 | 3. When your site is built, Jekyll will use the URL you specified, rather than the default one provided by GitHub. 87 | 88 | *Note: You must remove the `site.` prefix, and each variable name (after the `github.`) should be indent with two space below `github:`.* 89 | 90 | For more information, see [the Jekyll variables documentation](https://jekyllrb.com/docs/variables/). 91 | 92 | ## Roadmap 93 | 94 | See the [open issues](https://github.com/pages-themes/dinky/issues) for a list of proposed features (and known issues). 95 | 96 | ## Project philosophy 97 | 98 | The Dinky theme is intended to make it quick and easy for GitHub Pages users to create their first (or 100th) website. The theme should meet the vast majority of users' needs out of the box, erring on the side of simplicity rather than flexibility, and provide users the opportunity to opt-in to additional complexity if they have specific needs or wish to further customize their experience (such as adding custom CSS or modifying the default layout). It should also look great, but that goes without saying. 99 | 100 | ## Contributing 101 | 102 | Interested in contributing to Dinky? We'd love your help. Dinky is an open source project, built one contribution at a time by users like you. See [the CONTRIBUTING file](docs/CONTRIBUTING.md) for instructions on how to contribute. 103 | 104 | ### Previewing the theme locally 105 | 106 | If you'd like to preview the theme locally (for example, in the process of proposing a change): 107 | 108 | 1. Clone down the theme's repository (`git clone https://github.com/pages-themes/dinky`) 109 | 2. `cd` into the theme's directory 110 | 3. Run `script/bootstrap` to install the necessary dependencies 111 | 4. Run `bundle exec jekyll serve` to start the preview server 112 | 5. Visit [`localhost:4000`](http://localhost:4000) in your browser to preview the theme 113 | 114 | ### Running tests 115 | 116 | The theme contains a minimal test suite, to ensure a site with the theme would build successfully. To run the tests, simply run `script/cibuild`. You'll need to run `script/bootstrap` once before the test script will work. 117 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | CC0 1.0 Universal 2 | 3 | Statement of Purpose 4 | 5 | The laws of most jurisdictions throughout the world automatically confer 6 | exclusive Copyright and Related Rights (defined below) upon the creator and 7 | subsequent owner(s) (each and all, an "owner") of an original work of 8 | authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the 11 | purpose of contributing to a commons of creative, cultural and scientific 12 | works ("Commons") that the public can reliably and without fear of later 13 | claims of infringement build upon, modify, incorporate in other works, reuse 14 | and redistribute as freely as possible in any form whatsoever and for any 15 | purposes, including without limitation commercial purposes. These owners may 16 | contribute to the Commons to promote the ideal of a free culture and the 17 | further production of creative, cultural and scientific works, or to gain 18 | reputation or greater distribution for their Work in part through the use and 19 | efforts of others. 20 | 21 | For these and/or other purposes and motivations, and without any expectation 22 | of additional consideration or compensation, the person associating CC0 with a 23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright 24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work 25 | and publicly distribute the Work under its terms, with knowledge of his or her 26 | Copyright and Related Rights in the Work and the meaning and intended legal 27 | effect of CC0 on those rights. 28 | 29 | 1. Copyright and Related Rights. A Work made available under CC0 may be 30 | protected by copyright and related or neighboring rights ("Copyright and 31 | Related Rights"). Copyright and Related Rights include, but are not limited 32 | to, the following: 33 | 34 | i. the right to reproduce, adapt, distribute, perform, display, communicate, 35 | and translate a Work; 36 | 37 | ii. moral rights retained by the original author(s) and/or performer(s); 38 | 39 | iii. publicity and privacy rights pertaining to a person's image or likeness 40 | depicted in a Work; 41 | 42 | iv. rights protecting against unfair competition in regards to a Work, 43 | subject to the limitations in paragraph 4(a), below; 44 | 45 | v. rights protecting the extraction, dissemination, use and reuse of data in 46 | a Work; 47 | 48 | vi. database rights (such as those arising under Directive 96/9/EC of the 49 | European Parliament and of the Council of 11 March 1996 on the legal 50 | protection of databases, and under any national implementation thereof, 51 | including any amended or successor version of such directive); and 52 | 53 | vii. other similar, equivalent or corresponding rights throughout the world 54 | based on applicable law or treaty, and any national implementations thereof. 55 | 56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, 57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and 58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright 59 | and Related Rights and associated claims and causes of action, whether now 60 | known or unknown (including existing as well as future claims and causes of 61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum 62 | duration provided by applicable law or treaty (including future time 63 | extensions), (iii) in any current or future medium and for any number of 64 | copies, and (iv) for any purpose whatsoever, including without limitation 65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes 66 | the Waiver for the benefit of each member of the public at large and to the 67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver 68 | shall not be subject to revocation, rescission, cancellation, termination, or 69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work 70 | by the public as contemplated by Affirmer's express Statement of Purpose. 71 | 72 | 3. Public License Fallback. Should any part of the Waiver for any reason be 73 | judged legally invalid or ineffective under applicable law, then the Waiver 74 | shall be preserved to the maximum extent permitted taking into account 75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver 76 | is so judged Affirmer hereby grants to each affected person a royalty-free, 77 | non transferable, non sublicensable, non exclusive, irrevocable and 78 | unconditional license to exercise Affirmer's Copyright and Related Rights in 79 | the Work (i) in all territories worldwide, (ii) for the maximum duration 80 | provided by applicable law or treaty (including future time extensions), (iii) 81 | in any current or future medium and for any number of copies, and (iv) for any 82 | purpose whatsoever, including without limitation commercial, advertising or 83 | promotional purposes (the "License"). The License shall be deemed effective as 84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the 85 | License for any reason be judged legally invalid or ineffective under 86 | applicable law, such partial invalidity or ineffectiveness shall not 87 | invalidate the remainder of the License, and in such case Affirmer hereby 88 | affirms that he or she will not (i) exercise any of his or her remaining 89 | Copyright and Related Rights in the Work or (ii) assert any associated claims 90 | and causes of action with respect to the Work, in either case contrary to 91 | Affirmer's express Statement of Purpose. 92 | 93 | 4. Limitations and Disclaimers. 94 | 95 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 96 | surrendered, licensed or otherwise affected by this document. 97 | 98 | b. Affirmer offers the Work as-is and makes no representations or warranties 99 | of any kind concerning the Work, express, implied, statutory or otherwise, 100 | including without limitation warranties of title, merchantability, fitness 101 | for a particular purpose, non infringement, or the absence of latent or 102 | other defects, accuracy, or the present or absence of errors, whether or not 103 | discoverable, all to the greatest extent permissible under applicable law. 104 | 105 | c. Affirmer disclaims responsibility for clearing rights of other persons 106 | that may apply to the Work or any use thereof, including without limitation 107 | any person's Copyright and Related Rights in the Work. Further, Affirmer 108 | disclaims responsibility for obtaining any necessary consents, permissions 109 | or other rights required for any use of the Work. 110 | 111 | d. Affirmer understands and acknowledges that Creative Commons is not a 112 | party to this document and has no duty or obligation with respect to this 113 | CC0 or use of the Work. 114 | 115 | For more information, please see 116 | 117 | -------------------------------------------------------------------------------- /_sass/jekyll-theme-dinky.scss: -------------------------------------------------------------------------------- 1 | @import "rouge-github"; 2 | @import url('https://fonts.googleapis.com/css?family=Arvo:400,700,400italic'); 3 | 4 | /* MeyerWeb Reset */ 5 | 6 | html, body, div, span, applet, object, iframe, 7 | h1, h2, h3, h4, h5, h6, p, blockquote, pre, 8 | a, abbr, acronym, address, big, cite, code, 9 | del, dfn, em, img, ins, kbd, q, s, samp, 10 | small, strike, strong, sub, sup, tt, var, 11 | b, u, i, center, 12 | dl, dt, dd, ol, ul, li, 13 | fieldset, form, label, legend, 14 | table, caption, tbody, tfoot, thead, tr, th, td, 15 | article, aside, canvas, details, embed, 16 | figure, figcaption, footer, header, hgroup, 17 | menu, nav, output, ruby, section, summary, 18 | time, mark, audio, video { 19 | margin: 0; 20 | padding: 0; 21 | border: 0; 22 | font: inherit; 23 | vertical-align: baseline; 24 | } 25 | 26 | 27 | /* Base text styles */ 28 | 29 | body { 30 | padding:10px 50px 0 0; 31 | font-family:"Helvetica Neue", Helvetica, Arial, sans-serif; 32 | font-size: 14px; 33 | color: #232323; 34 | background-color: #FBFAF7; 35 | margin: 0; 36 | line-height: 1.8em; 37 | -webkit-font-smoothing: antialiased; 38 | 39 | } 40 | 41 | h1, h2, h3, h4, h5, h6 { 42 | color:#232323; 43 | margin:36px 0 10px; 44 | } 45 | 46 | p, ul, ol, table, dl { 47 | margin:0 0 22px; 48 | } 49 | 50 | h1, h2, h3 { 51 | font-family: Arvo, Monaco, serif; 52 | line-height:1.3; 53 | font-weight: normal; 54 | } 55 | 56 | h1,h2, h3 { 57 | display: block; 58 | border-bottom: 1px solid #ccc; 59 | padding-bottom: 5px; 60 | } 61 | 62 | h1 { 63 | font-size: 30px; 64 | } 65 | 66 | h2 { 67 | font-size: 24px; 68 | } 69 | 70 | h3 { 71 | font-size: 18px; 72 | } 73 | 74 | h4, h5, h6 { 75 | font-family: Arvo, Monaco, serif; 76 | font-weight: 700; 77 | } 78 | 79 | a { 80 | color:#C30000; 81 | font-weight:200; 82 | text-decoration:none; 83 | } 84 | 85 | a:hover { 86 | text-decoration: underline; 87 | } 88 | 89 | a small { 90 | font-size: 12px; 91 | } 92 | 93 | em { 94 | font-style: italic; 95 | } 96 | 97 | strong { 98 | font-weight:700; 99 | } 100 | 101 | ul { 102 | list-style-position: inside; 103 | list-style: disc; 104 | padding-left: 25px; 105 | } 106 | 107 | ol { 108 | list-style-position: inside; 109 | list-style: decimal; 110 | padding-left: 25px; 111 | } 112 | 113 | blockquote { 114 | margin: 0; 115 | padding: 0 0 0 20px; 116 | font-style: italic; 117 | } 118 | 119 | dl, dt, dd, dl p { 120 | color: #444; 121 | } 122 | 123 | dl dt { 124 | font-weight: bold; 125 | } 126 | 127 | dl dd { 128 | padding-left: 20px; 129 | font-style: italic; 130 | } 131 | 132 | dl p { 133 | padding-left: 20px; 134 | font-style: italic; 135 | } 136 | 137 | hr { 138 | border:0; 139 | background:#ccc; 140 | height:1px; 141 | margin:0 0 24px; 142 | } 143 | 144 | /* Images */ 145 | 146 | img { 147 | position: relative; 148 | margin: 0 auto; 149 | max-width: 650px; 150 | padding: 5px; 151 | margin: 10px 0 32px 0; 152 | border: 1px solid #ccc; 153 | } 154 | 155 | p img, .emoji { 156 | display: inline; 157 | margin: 0; 158 | padding: 0; 159 | vertical-align: middle; 160 | text-align: center; 161 | border: none; 162 | } 163 | 164 | /* Code blocks */ 165 | 166 | code, pre { 167 | font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal, monospace; 168 | color:#000; 169 | font-size:14px; 170 | } 171 | 172 | pre { 173 | padding: 4px 12px; 174 | background: #FDFEFB; 175 | border-radius:4px; 176 | border:1px solid #D7D8C8; 177 | overflow: auto; 178 | overflow-y: hidden; 179 | margin-bottom: 32px; 180 | } 181 | 182 | 183 | /* Tables */ 184 | 185 | table { 186 | width:100%; 187 | } 188 | 189 | table { 190 | border: 1px solid #ccc; 191 | margin-bottom: 32px; 192 | text-align: left; 193 | } 194 | 195 | th { 196 | font-family: 'Arvo', Helvetica, Arial, sans-serif; 197 | font-size: 18px; 198 | font-weight: normal; 199 | padding: 10px; 200 | background: #232323; 201 | color: #FDFEFB; 202 | } 203 | 204 | td { 205 | padding: 10px; 206 | background: #ccc; 207 | } 208 | 209 | 210 | /* Wrapper */ 211 | .wrapper { 212 | width:960px; 213 | } 214 | 215 | 216 | /* Header */ 217 | 218 | header { 219 | background-color: #171717; 220 | color: #FDFDFB; 221 | width:170px; 222 | float:left; 223 | position:fixed; 224 | border: 1px solid #000; 225 | -webkit-border-top-right-radius: 4px; 226 | -webkit-border-bottom-right-radius: 4px; 227 | -moz-border-radius-topright: 4px; 228 | -moz-border-radius-bottomright: 4px; 229 | border-top-right-radius: 4px; 230 | border-bottom-right-radius: 4px; 231 | padding: 34px 25px 22px 50px; 232 | margin: 30px 25px 0 0; 233 | -webkit-font-smoothing: antialiased; 234 | } 235 | 236 | p.header { 237 | font-size: 16px; 238 | } 239 | 240 | h1.header { 241 | font-family: Arvo, sans-serif; 242 | font-size: 30px; 243 | font-weight: 300; 244 | line-height: 1.3em; 245 | border-bottom: none; 246 | margin-top: 0; 247 | } 248 | 249 | 250 | h1.header, a.header, a.name, header a{ 251 | color: #fff; 252 | } 253 | 254 | a.header { 255 | text-decoration: underline; 256 | } 257 | 258 | a.name { 259 | white-space: nowrap; 260 | } 261 | 262 | header ul { 263 | list-style:none; 264 | padding:0; 265 | } 266 | 267 | header li { 268 | list-style-type: none; 269 | width:132px; 270 | height:15px; 271 | margin-bottom: 12px; 272 | line-height: 1em; 273 | padding: 6px 6px 6px 7px; 274 | 275 | background: #AF0011; 276 | background: -moz-linear-gradient(top, #AF0011 0%, #820011 100%); 277 | background: -webkit-gradient(linear, left top, left bottom, color-stop(0%,#f8f8f8), color-stop(100%,#dddddd)); 278 | background: -webkit-linear-gradient(top, #AF0011 0%,#820011 100%); 279 | background: -o-linear-gradient(top, #AF0011 0%,#820011 100%); 280 | background: -ms-linear-gradient(top, #AF0011 0%,#820011 100%); 281 | background: linear-gradient(to top, #AF0011 0%,#820011 100%); 282 | 283 | border-radius:4px; 284 | border:1px solid #0D0D0D; 285 | 286 | -webkit-box-shadow: inset 0px 1px 1px 0 rgba(233,2,38, 1); 287 | box-shadow: inset 0px 1px 1px 0 rgba(233,2,38, 1); 288 | 289 | } 290 | 291 | header li:hover { 292 | background: #C3001D; 293 | background: -moz-linear-gradient(top, #C3001D 0%, #950119 100%); 294 | background: -webkit-gradient(linear, left top, left bottom, color-stop(0%,#f8f8f8), color-stop(100%,#dddddd)); 295 | background: -webkit-linear-gradient(top, #C3001D 0%,#950119 100%); 296 | background: -o-linear-gradient(top, #C3001D 0%,#950119 100%); 297 | background: -ms-linear-gradient(top, #C3001D 0%,#950119 100%); 298 | background: linear-gradient(to top, #C3001D 0%,#950119 100%); 299 | } 300 | 301 | a.buttons { 302 | -webkit-font-smoothing: antialiased; 303 | background: url(../images/arrow-down.png) no-repeat; 304 | font-weight: normal; 305 | text-shadow: rgba(0, 0, 0, 0.4) 0 -1px 0; 306 | padding: 2px 2px 2px 22px; 307 | height: 30px; 308 | } 309 | 310 | a.github { 311 | background: url(../images/octocat-small.png) no-repeat 1px; 312 | } 313 | 314 | a.buttons:hover { 315 | color: #fff; 316 | text-decoration: none; 317 | } 318 | 319 | 320 | /* Section - for main page content */ 321 | 322 | section { 323 | width:650px; 324 | float:right; 325 | padding-bottom:50px; 326 | } 327 | 328 | 329 | /* Footer */ 330 | 331 | footer { 332 | width:170px; 333 | float:left; 334 | position:fixed; 335 | bottom:10px; 336 | padding-left: 50px; 337 | } 338 | 339 | @media print, screen and (max-width: 960px) { 340 | 341 | div.wrapper { 342 | width:auto; 343 | margin:0; 344 | } 345 | 346 | header, section, footer { 347 | float:none; 348 | position:static; 349 | width:auto; 350 | } 351 | 352 | footer { 353 | border-top: 1px solid #ccc; 354 | margin:0 84px 0 50px; 355 | padding:0; 356 | } 357 | 358 | header { 359 | padding-right:320px; 360 | } 361 | 362 | section { 363 | padding:20px 84px 20px 50px; 364 | margin:0 0 20px; 365 | } 366 | 367 | header a small { 368 | display:inline; 369 | } 370 | 371 | header ul { 372 | position:absolute; 373 | right:130px; 374 | top:84px; 375 | } 376 | } 377 | 378 | @media print, screen and (max-width: 720px) { 379 | body { 380 | word-wrap:break-word; 381 | } 382 | 383 | header { 384 | padding:10px 20px 0; 385 | margin-right: 0; 386 | } 387 | 388 | section { 389 | padding:10px 0 10px 20px; 390 | margin:0 0 30px; 391 | } 392 | 393 | footer { 394 | margin: 0 0 0 30px; 395 | } 396 | 397 | header ul, header p.view { 398 | position:static; 399 | } 400 | } 401 | 402 | @media print, screen and (max-width: 480px) { 403 | 404 | header ul li.download { 405 | display:none; 406 | } 407 | 408 | footer { 409 | margin: 0 0 0 20px; 410 | } 411 | 412 | footer a{ 413 | display:block; 414 | } 415 | 416 | } 417 | 418 | @media print { 419 | body { 420 | padding:0.4in; 421 | font-size:12pt; 422 | color:#444; 423 | } 424 | } 425 | --------------------------------------------------------------------------------