dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Default options for script/proof (#5995) 

Merge pull request 5995
This commit is contained in:
Frank Taillandier 2017-03-31 04:02:04 +02:00 committed by jekyllbot
parent 711a8483c6
commit 0d02a25b04
5 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/_docs/posts.md
View File

@ -42,7 +42,7 @@ file. For example, the following are examples of valid post filenames:
<div class="note"> <div class="note">
<h5>ProTip™: Link to other posts</h5> <h5>ProTip™: Link to other posts</h5>
<p> <p>
Use the <a href="../templates/#post-url"><code>post_url</code></a> Use the <a href="../templates/#linking-to-posts"><code>post_url</code></a>
tag to link to other posts without having to worry about the URL's tag to link to other posts without having to worry about the URL's
breaking when the site permalink style changes. breaking when the site permalink style changes.
</p> </p>

4
docs/_docs/quickstart.md
View File

@ -4,7 +4,7 @@ permalink: /docs/quickstart/
--- ---
If you already have a full [Ruby](https://www.ruby-lang.org/en/downloads/) development environment with all headers and [RubyGems](https://rubygems.org/pages/download) installed (see Jekyll's [requirements](/docs/installation/#requirements/)), you can create a new Jekyll site by doing the following: If you already have a full [Ruby](https://www.ruby-lang.org/en/downloads/) development environment with all headers and [RubyGems](https://rubygems.org/pages/download) installed (see Jekyll's [requirements](/docs/installation/#requirements)), you can create a new Jekyll site by doing the following:
```sh ```sh
# Install Jekyll and Bundler gems through RubyGems # Install Jekyll and Bundler gems through RubyGems
@ -22,7 +22,7 @@ If you already have a full [Ruby](https://www.ruby-lang.org/en/downloads/) devel
# Now browse to http://localhost:4000 # Now browse to http://localhost:4000
``` ```
If you encounter any unexpected errors during the above, please refer to the already-mentioned [requirements](/docs/installation/#requirements/) page, as you might be missing development headers or other prerequisites. If you encounter any unexpected errors during the above, please refer to the already-mentioned [requirements](/docs/installation/#requirements) page, as you might be missing development headers or other prerequisites.
## About Bundler ## About Bundler

2
docs/_docs/themes.md
View File

@ -184,7 +184,7 @@ For example, if your theme has a `/_layouts/page.html` file, and a page has `lay
Any file in `/assets` will be copied over to the user's site upon build unless they have a file with the same relative path. You can ship any kind of asset here: SCSS, an image, a webfont, etc. These files behave like pages and static files in Jekyll: Any file in `/assets` will be copied over to the user's site upon build unless they have a file with the same relative path. You can ship any kind of asset here: SCSS, an image, a webfont, etc. These files behave like pages and static files in Jekyll:
- If the file has [YAML front matter](../docs/frontmatter/) at the top, it will be rendered. - If the file has [YAML front matter](/docs/frontmatter/) at the top, it will be rendered.
- If the file does not have YAML front matter, it will simply be copied over into the resulting site. - If the file does not have YAML front matter, it will simply be copied over into the resulting site.
This allows theme creators to ship a default `/assets/styles.scss` file which their layouts can depend on as `/assets/styles.css`. This allows theme creators to ship a default `/assets/styles.scss` file which their layouts can depend on as `/assets/styles.css`.

4
script/proof
View File

@ -9,7 +9,7 @@ function msg {
printf "\e[0;37m==> $1\e[0m\n" printf "\e[0;37m==> $1\e[0m\n"
} }
INGORE_HREFS=$(ruby -e 'puts %w{ IGNORE_HREFS=$(ruby -e 'puts %w{
Chrononaut Chrononaut
twitter.com twitter.com
nearlyfreespeech.net nearlyfreespeech.net
@ -32,4 +32,4 @@ bundle exec jekyll build -s $SOURCE -d $DESTINATION --trace
# 3. # 3.
msg "Proofing..." msg "Proofing..."
time bundle exec htmlproofer ./$DESTINATION --url-ignore $INGORE_HREFS $@ time bundle exec htmlproofer ./$DESTINATION --allow-hash-href --url-ignore $IGNORE_HREFS $@