Changed the spacing so the line begins with `For a list of supported plugins`.
Why? I scanned this site many times looking for the supported list and couldn't see it, due to it being in the midst of a paragraph. IMHO, this is easier to scan and find.
* Update creating-a-github-pages-site-with-jekyll.md
The previous instructions for installing the `github-pages` gem via the Gemfile were confusing. If you search for `could not find gem github-pages` in your favorite search engine, you'll find many people didn't uncomment the line and/or tried to run `bundle update github-pages` instead of `bundle install`. This is my attempt to make things clearer by being more specific step by step.
* Update step 7 as well
I was initially focused on steps 8-10, but I thought I should try all of the commands to make sure everything works. As far as I can tell, you cannot pass in a version number to the `jekyll new` command, at least not the way it was documented here. Also, the Bundler section is more confusing than helpful because for `bundle exec` to work, a Gemfile must exist in the directory, but the instructions don’t mention that. Instead of adding more steps, I thought it was easier to skip that section.
Because people installing Jekyll today will have version 4.2.0, and because github-pages only supports 3.9.0, one must run `bundle update` instead of `bundle install` to resolve all dependencies.
* Update content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md
Co-authored-by: Ben Whetton <ben.whetton@gmail.com>
* Update content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md
Co-authored-by: Ben Whetton <ben.whetton@gmail.com>
* Update content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md
Co-authored-by: hubwriter <hubwriter@github.com>
* Update content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md
Co-authored-by: hubwriter <hubwriter@github.com>
* Update creating-a-github-pages-site-with-jekyll.md
Co-authored-by: Moncef Belyamani <moncef@example.com>
Co-authored-by: Ben Whetton <ben.whetton@gmail.com>
Co-authored-by: hubwriter <hubwriter@github.com>
* Fix errors in education product
* Fix errors in admin configuration docs
* Fix a few stray errors
* This works as is
* Sundry fixes picked up by Vale
* Another batch
* Today's batch of content fixes
* Sundry fixes
* More small updates
* Don't introduce a typo when we're trying to fix them
* Update content/admin/authentication/using-ldap.md
Co-authored-by: Laura Coursen <lecoursen@github.com>
Co-authored-by: Laura Coursen <lecoursen@github.com>
* chore: Add missing code fence languages
* Update content/actions/creating-actions/dockerfile-support-for-github-actions.md
* Add raw & endraw markers around shell content
See review comment by @rachmari
* Add raw & endraw markers around shell content
See review comment by @rachmari
* Remove language from code fences
to avoid the problem of replaceable text indicates like
<this> not showing up in the output page.
Co-authored-by: hubwriter <hubwriter@github.com>
Lately i'm working on an unofficial Chinese translation of GitHub Pages docs due to the incompletion of the original and currently there is no way to contribute translations to the docs. So, I hope that's ok to you guys.
The thing is, I'm seeing that this document is using both `<user>` and `<username>` as subdomain pronouns among the context. It's not a big problem, but in my opnion, this might cause some unnecessary confusion to some users.
If it was intended to be so, I'd like to know why?
Thank you!
Co-authored-by: hubwriter <hubwriter@github.com>
* Run script/new-versioning/update-not-fpt-conditionals.js
* Fix a few things
* Remove outdated versioning
* Fix broken link
Co-authored-by: jmarlena <6732600+jmarlena@users.noreply.github.com>
* ran script/remove-unused-assets.js (manually removed unused variables printed by the script)
* package-lock
* turn elsif into two ifs to prepare for running Liquid deprecation script
* ran script/remove-deprecated-enterprise-version-markup.js --release 2.14 (ONLY UPDATES LINE BREAKS ETC.)
* ran script/remove-deprecated-enterprise-version-markup.js --release 2.15
* ran script/remove-deprecated-enterprise-version-markup.js --release 2.17
* ran script/remove-deprecated-enterprise-version-markup.js --release 2.18
* update hardcoded test
* Update content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
* add currentVersion is NOT free-pro-team to conditional, to make sure the deprecation script does the right thing when it is time to deprecate 2.21
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
* Add back changes from prior to purge
* Manually fix some invalid Liquid
* Updoot render-content
* Improve test messages to show correct output
* Run el scripto
* Pass the remaining test
