Repository: pages-themes/modernist Branch: master Commit: 2efc28a182fa Files: 32 Total size: 42.5 KB Directory structure: gitextract_zxg97qob/ ├── .github/ │ ├── CODEOWNERS │ ├── config.yml │ ├── no-response.yml │ ├── settings.yml │ ├── stale.yml │ └── workflows/ │ ├── ci.yaml │ └── publish-gem.yml ├── .gitignore ├── .rubocop.yml ├── .travis.yml ├── Gemfile ├── LICENSE ├── README.md ├── _config.yml ├── _includes/ │ ├── head-custom-google-analytics.html │ └── head-custom.html ├── _layouts/ │ └── default.html ├── _sass/ │ ├── jekyll-theme-modernist.scss │ ├── modernist.scss │ └── rouge-base16-dark.scss ├── another-page.md ├── assets/ │ ├── css/ │ │ └── style.scss │ └── js/ │ └── scale.fix.js ├── docs/ │ ├── CODE_OF_CONDUCT.md │ ├── CONTRIBUTING.md │ └── SUPPORT.md ├── index.md ├── jekyll-theme-modernist.gemspec └── script/ ├── bootstrap ├── cibuild ├── release └── validate-html ================================================ FILE CONTENTS ================================================ ================================================ FILE: .github/CODEOWNERS ================================================ # Require maintainer's :+1: for changes to the .github/ repo-config files # mainly due to https://github.com/probot/settings privilege escalation .github/* @pages-themes/maintainers ================================================ FILE: .github/config.yml ================================================ # Behaviorbot config. See https://github.com/behaviorbot/ for more information. # Note: Please Don't edit this file directly. # Edit https://github.com/pages-themes/maintenance-scripts instead. # Configuration for update-docs - https://github.com/behaviorbot/update-docs 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:" # Configuration for request-info - https://github.com/behaviorbot/request-info requestInfoReplyComment: Thanks for this. Do you mind providing a bit more information about what problem you're trying to solve? requestInfoLabelToAdd: more-information-needed # Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome #newIssueWelcomeComment: > # Welcome! # Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome newPRWelcomeComment: Welcome! Congrats on your first pull request to the Modernist theme. If you haven't already, please be sure to check out [the contributing guidelines](https://github.com/pages-themes/modernist/blob/master/docs/CONTRIBUTING.md). # Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge firstPRMergeComment: "Congrats on getting your first pull request to the Modernist 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/modernist/issues), especially those [labeled `help wanted`](https://github.com/pages-themes/modernist/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22)." ================================================ FILE: .github/no-response.yml ================================================ # Configuration for probot-no-response - https://github.com/probot/no-response # Number of days of inactivity before an Issue is closed for lack of response daysUntilClose: 14 # Label requiring a response responseRequiredLabel: more-information-needed # Comment to post when closing an Issue for lack of response. Set to `false` to disable closeComment: > This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. ================================================ FILE: .github/settings.yml ================================================ # Repository settings set via https://github.com/probot/settings repository: has_issues: true has_wiki: false has_projects: false has_downloads: false labels: - name: help wanted oldname: help-wanted color: 0e8a16 - name: more-information-needed color: d93f0b - name: bug color: b60205 - name: feature color: 1d76db - name: good first issue color: "5319e7" # Not currently implemented by probot/settings, but manually implemented in script/deploy branch_protection: restrictions: null enforce_admins: false required_status_checks: strict: true contexts: - "script/cibuild" # GitHub Actions CI workflow required_pull_request_reviews: require_code_owner_reviews: true ================================================ FILE: .github/stale.yml ================================================ # Configuration for probot-stale - https://github.com/probot/stale # Number of days of inactivity before an Issue or Pull Request becomes stale daysUntilStale: 60 # Number of days of inactivity before a stale Issue or Pull Request is closed daysUntilClose: 7 # Issues or Pull Requests with these labels will never be considered stale exemptLabels: - pinned - security # Label to use when marking as stale staleLabel: wontfix # Comment to post when marking as stale. Set to `false` to disable markComment: > This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. # Comment to post when closing a stale Issue or Pull Request. Set to `false` to disable closeComment: false # Limit to only `issues` or `pulls` # only: issues ================================================ FILE: .github/workflows/ci.yaml ================================================ on: push: pull_request: types: [opened, synchronize] jobs: build: runs-on: ubuntu-latest name: script/cibuild steps: - uses: actions/checkout@v2 - uses: ruby/setup-ruby@v1 with: ruby-version: 3.2 bundler-cache: true - name: build run: script/bootstrap - name: test run: script/cibuild ================================================ FILE: .github/workflows/publish-gem.yml ================================================ name: Publish Gem on: release: types: [released] jobs: release: runs-on: ubuntu-latest steps: - name: Checkout uses: actions/checkout@v3 - name: Setup Ruby uses: ruby/setup-ruby@v1 with: ruby-version: '3.2' - name: Build gem run: | gem build github-pages.gemspec - name: Publish run: | gem push github-pages.gem --key ${{ secrets.PAGES_GEM_PUBLISH }} ================================================ FILE: .gitignore ================================================ _site .sass-cache Gemfile.lock *.gem .jekyll-cache/ .jekyll-cache ================================================ FILE: .rubocop.yml ================================================ inherit_gem: rubocop-github: - config/default.yml AllCops: Exclude: - _site/**/* - vendor/**/* Layout/LineLength: Enabled: false ================================================ FILE: .travis.yml ================================================ language: ruby cache: bundler rvm: 2.6 install: script/bootstrap script: script/cibuild ================================================ FILE: Gemfile ================================================ # frozen_string_literal: true source "https://rubygems.org" gemspec ================================================ FILE: LICENSE ================================================ CC0 1.0 Universal Statement of Purpose The laws of most jurisdictions throughout the world automatically confer exclusive Copyright and Related Rights (defined below) upon the creator and subsequent owner(s) (each and all, an "owner") of an original work of authorship and/or a database (each, a "Work"). Certain owners wish to permanently relinquish those rights to a Work for the purpose of contributing to a commons of creative, cultural and scientific works ("Commons") that the public can reliably and without fear of later claims of infringement build upon, modify, incorporate in other works, reuse and redistribute as freely as possible in any form whatsoever and for any purposes, including without limitation commercial purposes. These owners may contribute to the Commons to promote the ideal of a free culture and the further production of creative, cultural and scientific works, or to gain reputation or greater distribution for their Work in part through the use and efforts of others. For these and/or other purposes and motivations, and without any expectation of additional consideration or compensation, the person associating CC0 with a Work (the "Affirmer"), to the extent that he or she is an owner of Copyright and Related Rights in the Work, voluntarily elects to apply CC0 to the Work and publicly distribute the Work under its terms, with knowledge of his or her Copyright and Related Rights in the Work and the meaning and intended legal effect of CC0 on those rights. 1. Copyright and Related Rights. A Work made available under CC0 may be protected by copyright and related or neighboring rights ("Copyright and Related Rights"). Copyright and Related Rights include, but are not limited to, the following: i. the right to reproduce, adapt, distribute, perform, display, communicate, and translate a Work; ii. moral rights retained by the original author(s) and/or performer(s); iii. publicity and privacy rights pertaining to a person's image or likeness depicted in a Work; iv. rights protecting against unfair competition in regards to a Work, subject to the limitations in paragraph 4(a), below; v. rights protecting the extraction, dissemination, use and reuse of data in a Work; vi. database rights (such as those arising under Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, and under any national implementation thereof, including any amended or successor version of such directive); and vii. other similar, equivalent or corresponding rights throughout the world based on applicable law or treaty, and any national implementations thereof. 2. Waiver. To the greatest extent permitted by, but not in contravention of, applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and unconditionally waives, abandons, and surrenders all of Affirmer's Copyright and Related Rights and associated claims and causes of action, whether now known or unknown (including existing as well as future claims and causes of action), in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each member of the public at large and to the detriment of Affirmer's heirs and successors, fully intending that such Waiver shall not be subject to revocation, rescission, cancellation, termination, or any other legal or equitable action to disrupt the quiet enjoyment of the Work by the public as contemplated by Affirmer's express Statement of Purpose. 3. Public License Fallback. Should any part of the Waiver for any reason be judged legally invalid or ineffective under applicable law, then the Waiver shall be preserved to the maximum extent permitted taking into account Affirmer's express Statement of Purpose. In addition, to the extent the Waiver is so judged Affirmer hereby grants to each affected person a royalty-free, non transferable, non sublicensable, non exclusive, irrevocable and unconditional license to exercise Affirmer's Copyright and Related Rights in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the "License"). The License shall be deemed effective as of the date CC0 was applied by Affirmer to the Work. Should any part of the License for any reason be judged legally invalid or ineffective under applicable law, such partial invalidity or ineffectiveness shall not invalidate the remainder of the License, and in such case Affirmer hereby affirms that he or she will not (i) exercise any of his or her remaining Copyright and Related Rights in the Work or (ii) assert any associated claims and causes of action with respect to the Work, in either case contrary to Affirmer's express Statement of Purpose. 4. Limitations and Disclaimers. a. No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document. b. Affirmer offers the Work as-is and makes no representations or warranties of any kind concerning the Work, express, implied, statutory or otherwise, including without limitation warranties of title, merchantability, fitness for a particular purpose, non infringement, or the absence of latent or other defects, accuracy, or the present or absence of errors, whether or not discoverable, all to the greatest extent permissible under applicable law. c. Affirmer disclaims responsibility for clearing rights of other persons that may apply to the Work or any use thereof, including without limitation any person's Copyright and Related Rights in the Work. Further, Affirmer disclaims responsibility for obtaining any necessary consents, permissions or other rights required for any use of the Work. d. Affirmer understands and acknowledges that Creative Commons is not a party to this document and has no duty or obligation with respect to this CC0 or use of the Work. For more information, please see ================================================ FILE: README.md ================================================ # The Modernist theme [![.github/workflows/ci.yaml](https://github.com/pages-themes/modernist/actions/workflows/ci.yaml/badge.svg)](https://github.com/pages-themes/modernist/actions/workflows/ci.yaml) [![Gem Version](https://badge.fury.io/rb/jekyll-theme-modernist.svg)](https://badge.fury.io/rb/jekyll-theme-modernist) *Modernist is a Jekyll theme for GitHub Pages. You can [preview the theme to see what it looks like](http://pages-themes.github.io/modernist), or even [use it today](#usage).* ![Thumbnail of Modernist](thumbnail.png) ## Usage To use the Modernist theme: 1. Add the following to your site's `_config.yml`: ```yml remote_theme: pages-themes/modernist@v0.2.0 plugins: - jekyll-remote-theme # add this line to the plugins list if you already have one ``` 2. Optionally, if you'd like to preview your site on your computer, add the following to your site's `Gemfile`: ```ruby gem "github-pages", group: :jekyll_plugins ``` ## Customizing ### Configuration variables Modernist will respect the following variables, if set in your site's `_config.yml`: ```yml title: [The title of your site] description: [A short description of your site's purpose] ``` Additionally, you may choose to set the following optional variables: ```yml show_downloads: ["true" or "false" (unquoted) to indicate whether to provide a download URL] google_analytics: [Your Google Analytics tracking ID] ``` ### Stylesheet If you'd like to add your own custom styles: 1. Create a file called `/assets/css/style.scss` in your site 2. Add the following content to the top of the file, exactly as shown: ```scss --- --- @import "{{ site.theme }}"; ``` 3. Add any custom CSS (or Sass, including imports) you'd like immediately after the `@import` line *Note: If you'd like to change the theme's Sass variables, you must set new values before the `@import` line in your stylesheet.* ### Layouts If you'd like to change the theme's HTML layout: 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/modernist/tree/master/_includes) provide a starting point and are included by the [original layout template](https://github.com/pages-themes/modernist/blob/master/_layouts/default.html). 2. For more extensive changes, [copy the original template](https://github.com/pages-themes/modernist/blob/master/_layouts/default.html) from the theme's repository
(*Pro-tip: click "raw" to make copying easier*) 3. Create a file called `/_layouts/default.html` in your site 4. Paste the default layout content copied in the first step 5. Customize the layout as you'd like ### Customizing Google Analytics code 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. ### Overriding GitHub-generated URLs 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: 1. Look at [the template source](https://github.com/pages-themes/modernist/blob/master/_layouts/default.html) to determine the name of the variable. It will be in the form of `{{ site.github.zip_url }}`. 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: ```yml github: zip_url: http://example.com/download.zip another_url: another value ``` 3. When your site is built, Jekyll will use the URL you specified, rather than the default one provided by GitHub. *Note: You must remove the `site.` prefix, and each variable name (after the `github.`) should be indent with two space below `github:`.* For more information, see [the Jekyll variables documentation](https://jekyllrb.com/docs/variables/). ## Roadmap See the [open issues](https://github.com/pages-themes/modernist/issues) for a list of proposed features (and known issues). ## Project philosophy The Modernist 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. ## Contributing Interested in contributing to Modernist? We'd love your help. Modernist 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. ### Previewing the theme locally If you'd like to preview the theme locally (for example, in the process of proposing a change): 1. Clone down the theme's repository (`git clone https://github.com/pages-themes/modernist`) 2. `cd` into the theme's directory 3. Run `script/bootstrap` to install the necessary dependencies 4. Run `bundle exec jekyll serve` to start the preview server 5. Visit [`localhost:4000`](http://localhost:4000) in your browser to preview the theme ### Running tests 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. ================================================ FILE: _config.yml ================================================ title: Modernist theme description: Modernist is a theme for GitHub Pages. show_downloads: true google_analytics: theme: jekyll-theme-modernist ================================================ FILE: _includes/head-custom-google-analytics.html ================================================ {% if site.google_analytics %} {% endif %} ================================================ FILE: _includes/head-custom.html ================================================ {% include head-custom-google-analytics.html %} ================================================ FILE: _layouts/default.html ================================================ {% seo %} {% include head-custom.html %}

{% if site.description or site.github.project_tagline %}

{% endif %}

View the Project on GitHub {{ github_name }}

Download ZIP File
Download TAR Ball
View On GitHub

================================================ FILE: _sass/jekyll-theme-modernist.scss ================================================ @import "rouge-base16-dark"; @import url('https://fonts.googleapis.com/css?family=Lato:300italic,700italic,300,700'); html { background:#6C7989; background: #6C7989 linear-gradient(#6C7989, #434B55) fixed; height: 100%; } body { padding:50px 0; margin:0; font:14px/1.5 Lato, "Helvetica Neue", Helvetica, Arial, sans-serif; color:#555; font-weight:300; background:url('../images/checker.png') fixed; min-height: calc(100% - 100px); } .wrapper { width:740px; margin:0 auto; background:#DEDEDE; border-radius: 8px; box-shadow: rgba(#000, 0.2) 0 0 0 1px, rgba(#000, 0.45) 0 3px 10px; } header, section, footer { display:block; } a { color:#069; text-decoration:none; } p { margin:0 0 20px; padding:0; } strong { color:#222; font-weight:700; } header { border-radius: 8px 8px 0 0; background:#C6EAFA; background: linear-gradient(#DDFBFC, #C6EAFA); position:relative; padding:15px 20px; border-bottom:1px solid #B2D2E1; h1 { margin:0; padding:0; font-size:24px; line-height:1.2; color:#069; text-shadow:rgba(#fff, 0.9) 0 1px 0; } &.without-description h1 { margin:10px 0; } p { margin:0; color:#61778B; width:300px; font-size:13px; &.view { display:none; font-weight:700; text-shadow:rgba(#fff, 0.9) 0 1px 0; -webkit-font-smoothing:antialiased; a { color:#06c; } small { font-weight:400; } } } ul { margin:0; padding:0; list-style:none; position:absolute; z-index:1; right:20px; top:20px; height:38px; padding:1px 0; background:#5198DF; background: linear-gradient(#77B9FB, #3782CD); border-radius:5px; box-shadow: inset rgba(#fff, 0.45) 0 1px 0, inset rgba(#000, 0.2) 0 -1px 0; width:auto; &:before { content:''; position:absolute; z-index:-1; left:-5px; top:-4px; right:-5px; bottom:-6px; background:rgba(#000, 0.1); border-radius: 8px; box-shadow: rgba(#000, 0.2) 0 -1px 0, inset rgba(#fff, 0.7) 0 -1px 0; } li { width:79px; float:left; border-right:1px solid #3A7CBE; height:38px; &.single { border:none; } } li + li { width:78px; border-left:1px solid #8BBEF3; } li + li + li { border-right:none; width:79px; } a { line-height:1; font-size:11px; color:#fff; color:rgba(#fff, 0.8); display:block; text-align:center; font-weight:400; padding-top:6px; height:40px; text-shadow:rgba(#000, 0.4) 0 -1px 0; strong { font-size:14px; display:block; color:#fff; -webkit-font-smoothing:antialiased; } } } } section { padding:15px 20px; font-size:15px; border-top:1px solid #fff; background: linear-gradient(#fafafa, #DEDEDE 700px); border-radius: 0 0 8px 8px; position:relative; } h1, h2, h3, h4, h5, h6 { color:#222; padding:0; margin:0 0 20px; line-height:1.2; } p, ul, ol, table, pre, dl { margin:0 0 20px; } h1, h2, h3 { line-height:1.1; } h1 { font-size:28px; } h2 { color:#393939; } h3, h4, h5, h6 { color:#494949; } blockquote { margin:0 -20px 20px; padding:15px 20px 1px 40px; font-style:italic; background:#ccc; background:rgba(#000, 0.06); color:#222; } img { max-width:100%; } code, pre { font-family:Monaco, Bitstream Vera Sans Mono, Lucida Console, Terminal; color:#333; font-size:12px; overflow-x:auto; } pre { padding:20px; background: #3A3C42; color:#f8f8f2; margin:0 -20px 20px; code { color:#f8f8f2; } li & { margin-left:-60px; padding-left:60px; } } table { width:100%; border-collapse:collapse; } th, td { text-align:left; padding:5px 10px; border-bottom:1px solid #aaa; } dt { color:#222; font-weight:700; } th { color:#222; } small { font-size:11px; } hr { border:0; background:#aaa; height:1px; margin:0 0 20px; } kbd { background-color: #fafbfc; border: 1px solid #c6cbd1; border-bottom-color: #959da5; border-radius: 3px; box-shadow: inset 0 -1px 0 #959da5; color: #444d56; display: inline-block; font-size: 11px; line-height: 10px; padding: 3px 5px; vertical-align: middle; } footer { width:640px; margin:0 auto; padding:20px 0 0; color:#ccc; overflow:hidden; a { color:#fff; font-weight:bold; } p { float:left; } p + p { float:right; } } @media print, screen and (max-width: 740px) { body { padding:0; } .wrapper { border-radius: 0; box-shadow: none; width:100%; } footer { border-radius: 0; padding:20px; width:auto; p { float:none; margin:0; } p + p { float:none; } } } @media print, screen and (max-width:580px) { header ul { display:none; } header p.view { display:block; } header p { width:100%; } } @media print { header p.view a small:before { content:'at https://github.com/'; } } ================================================ FILE: _sass/modernist.scss ================================================ // Placeholder file. If your site uses // @import "{{ site.theme }}"; // Then using this theme with jekyll-remote-theme will work fine. @import "jekyll-theme-modernist"; ================================================ FILE: _sass/rouge-base16-dark.scss ================================================ /* generated by rouge http://rouge.jneen.net/ original base16 by Chris Kempson (https://github.com/chriskempson/base16) */ .highlight table td { padding: 5px; } .highlight table pre { margin: 0; } .highlight, .highlight .w { color: #d0d0d0; } .highlight .err { color: #151515; background-color: #ac4142; } .highlight .c, .highlight .cd, .highlight .cm, .highlight .c1, .highlight .cs { color: #888; } .highlight .cp { color: #f4bf75; } .highlight .nt { color: #f4bf75; } .highlight .o, .highlight .ow { color: #d0d0d0; } .highlight .p, .highlight .pi { color: #d0d0d0; } .highlight .gi { color: #90a959; } .highlight .gd { color: #ac4142; } .highlight .gh { color: #6a9fb5; font-weight: bold; } .highlight .k, .highlight .kn, .highlight .kp, .highlight .kr, .highlight .kv { color: #aa759f; } .highlight .kc { color: #d28445; } .highlight .kt { color: #d28445; } .highlight .kd { color: #d28445; } .highlight .s, .highlight .sb, .highlight .sc, .highlight .sd, .highlight .s2, .highlight .sh, .highlight .sx, .highlight .s1 { color: #90a959; } .highlight .sr { color: #75b5aa; } .highlight .si { color: #8f5536; } .highlight .se { color: #8f5536; } .highlight .nn { color: #f4bf75; } .highlight .nc { color: #f4bf75; } .highlight .no { color: #f4bf75; } .highlight .na { color: #6a9fb5; } .highlight .m, .highlight .mf, .highlight .mh, .highlight .mi, .highlight .il, .highlight .mo, .highlight .mb, .highlight .mx { color: #90a959; } .highlight .ss { color: #90a959; } ================================================ FILE: another-page.md ================================================ --- layout: default --- ## Welcome to another page _yay_ [back](./) ================================================ FILE: assets/css/style.scss ================================================ --- --- @import "jekyll-theme-modernist"; ================================================ FILE: assets/js/scale.fix.js ================================================ fixScale = function(doc) { var addEvent = 'addEventListener', type = 'gesturestart', qsa = 'querySelectorAll', scales = [1, 1], meta = qsa in doc ? doc[qsa]('meta[name=viewport]') : []; function fix() { meta.content = 'width=device-width,minimum-scale=' + scales[0] + ',maximum-scale=' + scales[1]; doc.removeEventListener(type, fix, true); } if ((meta = meta[meta.length - 1]) && addEvent in doc) { fix(); scales = [.25, 1.6]; doc[addEvent](type, fix, true); } }; ================================================ FILE: docs/CODE_OF_CONDUCT.md ================================================ # 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 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. 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/ ================================================ FILE: docs/CONTRIBUTING.md ================================================ # Contributing to the Modernist theme Hi there! We're thrilled that you'd like to contribute to the Modernist theme. Your help is essential for keeping it great. the Modernist 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 Modernist theme itself. 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. ## Looking for support? We'd love to help. Check out [the support guidelines](SUPPORT.md). ## How to report a bug Think you found a bug? Please check [the list of open issues](https://github.com/pages-themes/modernist/issues) to see if your bug has already been reported. If it hasn't please [submit a new issue](https://github.com/pages-themes/modernist/issues/new). Here are a few tips for writing *great* bug reports: * Describe the specific problem (e.g., "widget doesn't turn clockwise" versus "getting an error") * Include the steps to reproduce the bug, what you expected to happen, and what happened instead * Check that you are using the latest version of the project and its dependencies * Include what version of the project your using, as well as any relevant dependencies * Only include one bug per issue. If you have discovered two bugs, please file two issues * Even if you don't know how to fix the bug, including a failing test may help others track it down **If you find a security vulnerability, do not open an issue. Please email security@github.com instead.** ## How to suggest a feature or enhancement If you find yourself wishing for a feature that doesn't exist in the Modernist theme, you are probably not alone. There are bound to be others out there with similar needs. Many of the features that the Modernist theme has today have been added because our users saw the need. 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. [Open an issue](https://github.com/pages-themes/modernist/issues/new) which describes the feature you would like to see, why you want it, how it should work, etc. ## Your first contribution We'd love for you to contribute to the project. Unsure where to begin contributing to the Modernist theme? You can start by looking through these "good first issue" and "help wanted" issues: * [Good first issues](https://github.com/pages-themes/modernist/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 * [Help wanted issues](https://github.com/pages-themes/modernist/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 *p.s. Feel free to ask for help; everyone is a beginner at first* :smiley_cat: ## How to propose changes Here's a few general guidelines for proposing changes: * If you are making visual changes, include a screenshot of what the affected element looks like, both before and after. * Follow the [Jekyll style guide](https://ben.balter.com/jekyll-style-guide). * If you are changing any user-facing functionality, please be sure to update the documentation * 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 * Do not commit changes to files that are irrelevant to your feature or bug fix * Don't bump the version number in your pull request (it will be bumped prior to release) * Write [a good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) At a high level, [the process for proposing changes](https://guides.github.com/introduction/flow/) is: 1. [Fork](https://github.com/pages-themes/modernist/fork) and clone the project 2. Configure and install the dependencies: `script/bootstrap` 3. Make sure the tests pass on your machine: `script/cibuild` 4. Create a new branch: `git checkout -b my-branch-name` 5. Make your change, add tests, and make sure the tests still pass 6. Push to your fork and [submit a pull request](https://github.com/pages-themes/modernist/compare) 7. Pat your self on the back and wait for your pull request to be reviewed and merged **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) ## Bootstrapping your local development environment `script/bootstrap` ## Running tests `script/cibuild` ## Publishing Gem In order to publish the Gem bump the version in *this file*, commit, create a tag with the new version number, and finally push the commit and tag to the repo. ## Code of conduct This project is governed by [the Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. ## Additional Resources * [Contributing to Open Source on GitHub](https://guides.github.com/activities/contributing-to-open-source/) * [Using Pull Requests](https://help.github.com/articles/using-pull-requests/) * [GitHub Help](https://help.github.com) ================================================ FILE: docs/SUPPORT.md ================================================ ## Where to get help If you think you've found a bug in the Modernist theme, please [check the existing issues](https://github.com/pages-themes/modernist/issues), and if no one has reported the problem, [open a new issue](https://github.com/pages-themes/modernist/issues/new). 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: 1. Search for your query on [`support.github.com`](https://support.github.com/?q=pages+Modernist+theme), which will also look for similar topics on [`github.community`](https://github.community/search?q=pages+Modernist+theme) 2. Ask your question of the Jekyll community on [talk.jekyllrb.com](https://talk.jekyllrb.com/) 3. [Contact GitHub Support](https://github.com/contact?form%5Bsubject%5D=GitHub%20Pages%20theme%20pages-themes/modernist) ================================================ FILE: index.md ================================================ --- layout: default --- Text can be **bold**, _italic_, or ~~strikethrough~~. [Link to another page](./another-page.html). There should be whitespace between paragraphs. There should be whitespace between paragraphs. We recommend including a README, or a file with information about your project. # Header 1 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. ## Header 2 > This is a blockquote following a header. > > When something is important enough, you do it even if the odds are not in your favor. ### Header 3 ```js // Javascript code with syntax highlighting. var fun = function lang(l) { dateformat.i18n = require('./lang/' + l) return true; } ``` ```ruby # Ruby code with syntax highlighting GitHubPages::Dependencies.gems.each do |gem, version| s.add_dependency(gem, "= #{version}") end ``` #### Header 4 * This is an unordered list following a header. * This is an unordered list following a header. * This is an unordered list following a header. ##### Header 5 1. This is an ordered list following a header. 2. This is an ordered list following a header. 3. This is an ordered list following a header. ###### Header 6 | head1 | head two | three | |:-------------|:------------------|:------| | ok | good swedish fish | nice | | out of stock | good and plenty | nice | | ok | good `oreos` | hmm | | ok | good `zoute` drop | yumm | ### There's a horizontal rule below this. * * * ### Here is an unordered list: * Item foo * Item bar * Item baz * Item zip ### And an ordered list: 1. Item one 1. Item two 1. Item three 1. Item four ### And a nested list: - level 1 item - level 2 item - level 2 item - level 3 item - level 3 item - level 1 item - level 2 item - level 2 item - level 2 item - level 1 item - level 2 item - level 2 item - level 1 item ### Small image ![Octocat](https://github.githubassets.com/images/icons/emoji/octocat.png) ### Large image ![Branching](https://guides.github.com/activities/hello-world/branching.png) ### Definition lists can be used with HTML syntax.

Name: Godzilla
Born: 1952
Birthplace: Japan
Color: Green

``` 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. ``` ``` The final element. ``` ================================================ FILE: jekyll-theme-modernist.gemspec ================================================ # frozen_string_literal: true Gem::Specification.new do |s| s.name = "jekyll-theme-modernist" s.version = "0.2.0" s.license = "CC0-1.0" s.authors = ["Steve Smith", "GitHub, Inc."] s.email = ["opensource+jekyll-theme-modernist@github.com"] s.homepage = "https://github.com/pages-themes/modernist" s.summary = "Modernist is a Jekyll theme for GitHub Pages" s.files = `git ls-files -z`.split("\x0").select do |f| f.match(%r{^((_includes|_layouts|_sass|assets)/|(LICENSE|README)((\.(txt|md|markdown)|$)))}i) end s.required_ruby_version = ">= 2.4.0" s.platform = Gem::Platform::RUBY s.add_runtime_dependency "jekyll", "> 3.5", "< 5.0" s.add_runtime_dependency "jekyll-seo-tag", "~> 2.0" s.add_development_dependency "html-proofer", "~> 3.0" s.add_development_dependency "rubocop-github", "~> 0.16" s.add_development_dependency "w3c_validators", "~> 1.3" end ================================================ FILE: script/bootstrap ================================================ #!/bin/sh set -e gem install bundler bundle install ================================================ FILE: script/cibuild ================================================ #!/bin/sh set -e bundle exec jekyll build bundle exec htmlproofer ./_site --check-html --check-sri bundle exec rubocop -D --config .rubocop.yml bundle exec script/validate-html gem build jekyll-theme-modernist.gemspec ================================================ FILE: script/release ================================================ #!/bin/sh # Tag and push a release. set -e # Make sure we're in the project root. cd $(dirname "$0")/.. # Make sure the darn thing works bundle update # Build a new gem archive. rm -rf jekyll-theme-modernist-*.gem gem build -q jekyll-theme-modernist.gemspec # Make sure we're on the master branch. (git branch | grep -q 'master') || { echo "Only release from the master branch." exit 1 } # Figure out what version we're releasing. tag=v`ls jekyll-theme-modernist-*.gem | sed 's/^jekyll-theme-modernist-$.*$\.gem$/\1/'` # Make sure we haven't released this version before. git fetch -t origin (git tag -l | grep -q "$tag") && { echo "Whoops, there's already a '${tag}' tag." exit 1 } # Tag it and bag it. gem push jekyll-theme-modernist-*.gem && git tag "$tag" && git push origin master && git push origin "$tag" ================================================ FILE: script/validate-html ================================================ #!/usr/bin/env ruby # frozen_string_literal: true require "w3c_validators" def validator(file) extension = File.extname(file) if extension == ".html" W3CValidators::NuValidator.new elsif extension == ".css" W3CValidators::CSSValidator.new end end def validate(file) puts "Checking #{file}..." path = File.expand_path "../_site/#{file}", __dir__ results = validator(file).validate_file(path) return puts "Valid!" if results.errors.empty? results.errors.each { |err| puts err } exit 1 end validate "index.html" validate File.join "assets", "css", "style.css"