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

Textile is only supported through a converter plugin (#7003) 

Merge pull request 7003
This commit is contained in:
Frank Taillandier 2018-05-09 13:45:18 +02:00 committed by jekyllbot
parent a59eaff789
commit e9b507a0df
4 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/_docs/pagination.md
View File

@ -14,7 +14,7 @@ your `_config.yml` under `plugins`. For Jekyll 2, this is standard.
<div class="note info"> <div class="note info">
<h5>Pagination only works within HTML files</h5> <h5>Pagination only works within HTML files</h5>
<p> <p>
Pagination does not work from within Markdown or Textile files from Pagination does not work from within Markdown files from
your Jekyll site. Pagination works when called from within the HTML your Jekyll site. Pagination works when called from within the HTML
file, named <code>index.html</code>, which optionally may reside in and file, named <code>index.html</code>, which optionally may reside in and
produce pagination from within a subdirectory, via the produce pagination from within a subdirectory, via the

5
docs/_docs/structure.md
View File

@ -5,7 +5,8 @@ permalink: /docs/structure/
Jekyll is, at its core, a text transformation engine. The concept behind the Jekyll is, at its core, a text transformation engine. The concept behind the
system is this: you give it text written in your favorite markup language, be system is this: you give it text written in your favorite markup language, be
that Markdown, Textile, or just plain HTML, and it churns that through a layout that Markdown, [Textile](https://github.com/jekyll/jekyll-textile-converter)
, or just plain HTML, and it churns that through a layout
or a series of layout files. Throughout that process you can tweak how you want or a series of layout files. Throughout that process you can tweak how you want
the site URLs to look, what data gets displayed in the layout, and more. This the site URLs to look, what data gets displayed in the layout, and more. This
is all done through editing text files; the static web site is the final is all done through editing text files; the static web site is the final
@ -185,7 +186,7 @@ An overview of what each of these does:
<tr> <tr>
<td> <td>
<p><code>index.html</code> or <code>index.md</code> and other HTML, <p><code>index.html</code> or <code>index.md</code> and other HTML,
Markdown, Textile files</p> Markdown files</p>
</td> </td>
<td> <td>
<p> <p>

4
docs/_docs/upgrading/2-to-3.md
View File

@ -44,6 +44,10 @@ For `site.collections.myCollection` in Jekyll 2, you now do:
This is a bit cumbersome at first, but is easier than a big `for` loop. This is a bit cumbersome at first, but is easier than a big `for` loop.
### Textile support
We dropped native support for Textile, from now on you have to install our [jekyll-textile-converter](https://github.com/jekyll/jekyll-textile-converter) plugin to work with Textile files.
### Dropped dependencies ### Dropped dependencies
We dropped a number of dependencies the Core Team felt were optional. As such, in 3.0, they must be explicitly installed and included if you use any of the features. They are: We dropped a number of dependencies the Core Team felt were optional. As such, in 3.0, they must be explicitly installed and included if you use any of the features. They are:

2
docs/index.html
View File

@ -21,7 +21,7 @@ overview: true
</div> </div>
<div class="unit one-third"> <div class="unit one-third">
<h2>Static</h2> <h2>Static</h2>
<p><a href="https://daringfireball.net/projects/markdown/">Markdown</a> (or <a href="http://redcloth.org/textile">Textile</a>), <a href="https://github.com/Shopify/liquid/wiki">Liquid</a>, HTML <span class="amp">&amp;</span> CSS go in. Static sites come out ready for deployment.</p> <p><a href="https://daringfireball.net/projects/markdown/">Markdown</a>, <a href="https://github.com/Shopify/liquid/wiki">Liquid</a>, HTML <span class="amp">&amp;</span> CSS go in. Static sites come out ready for deployment.</p>
<a href="/docs/templates/">Jekyll template guide &rarr;</a> <a href="/docs/templates/">Jekyll template guide &rarr;</a>
</div> </div>
<div class="unit one-third"> <div class="unit one-third">