티스토리 수익 글 보기
The post New theme chooser for GitHub Pages appeared first on The GitHub Blog.
]]>- Create a new GitHub repository or go to an existing one.
- Open the theme chooser in the GitHub Pages section of your repository settings.
- Select a theme.
Using a Jekyll theme means that your website content lives in Markdown files, which you can edit as needed and manage using your favorite Git workflow.
As soon as you apply a Jekyll theme to your site, you can add more pages simply by committing new Markdown files.
The theme chooser replaces the old automatic page generator which didn’t use Jekyll. Rest assured, existing GitHub Pages created with the automatic page generator will automatically use a matching Jekyll theme the first time you use the theme chooser.
Finally, the Jekyll themes in the theme chooser are all open sourced on GitHub.
For additional information, check out the documentation.
The post New theme chooser for GitHub Pages appeared first on The GitHub Blog.
]]>The post Simpler GitHub Pages publishing appeared first on The GitHub Blog.
]]>
- Selecting master branch will publish your site from the
masterbranch. This is useful for repositories dedicated to website content. - Selecting master branch /docs folder will publish from the
/docsfolder of yourmasterbranch. This lets you maintain documentation and code together on one branch, and open source maintainers can accept contributions for both in a single pull request.
Rest assured that existing project pages which use a gh-pages branch will keep working just like before, as will user and organization pages published from the master branch.
Check out the documentation to learn more.
The post Simpler GitHub Pages publishing appeared first on The GitHub Blog.
]]>The post Upgrading your Textile posts to Markdown appeared first on The GitHub Blog.
]]>Starting May 1st, 2016, GitHub Pages will no longer support Textile. If you are currently using Textile (Redcloth) to author your Jekyll site, you’ll need to convert your site to use Markdown instead.
Here are some tips for converting from Textile to Markdown.
Manual conversion
On sites with just a few Textile pages, editing those by hand may be the fastest way to convert to Markdown. Here are some of the most important changes.
| Textile | Markdown | |
|---|---|---|
| headings | h1. text |
# text |
h2. text |
## text |
|
h3. text |
### text |
|
| links | "link-text (title)":url |
[link-text](url "title") |
| bullet lists | * item |
* item |
** nested item |
* indent nested item
|
|
| numbered lists | # item |
1. item |
## nested item |
1. indent nested item
|
|
| italics | _italics_ |
_italics_ |
| bold | *bold* |
**bold** |
code |
<code> code </code> |
|
| blockquotes | bq. text... |
> text... |
For more details refer to the Textile docs and the GFM cheatsheet
Automated conversion from .textile to .md with pandoc
Users with many Textile files in their Jekyll Pages site can leverage pandoc, a utility for converting between different markup formats.
The tomd shell script uses awk and sed to overcome the biggest limitations of pandoc, filtering out the sections listed below, which pandoc doesn’t recognize, and re-inserting them into the converted Markdown.
- YAML frontmatter at the top of .textile files
-
{% raw %}{% highlight %}{% endraw %}blocks -
<notextile>blocks
To run tomd
- Install pandoc from https://github.com/jgm/pandoc/releases or here.
- Download or clone tomd.
- Copy the
tomdscript and the two.awkfiles into your Jekyll project. - Invoke the script with
./tomdfrom inside your Jekyll project folder. - Validate the results.
The script will look for any .textile files in the _posts directory, convert them to .md, and leave backups of the original .textile files in a new directory called _old_posts. You can override the names of the directories with arguments to the script.
If everything works, you will see output like:
NOTE: This process may still produce some incorrect output, so check your results.
Known issues include:
- Lost CSS references e.g. from Textile
.p(classname) - Literal HTML mixed with Textile formatting e.g.
<sup>"textile-link-text":url</sup>
Running under Windows
The latest version of pandoc for Windows can be downloaded from https://github.com/jgm/pandoc/releases/.
In addition to pandoc, tomd requires a unix-y shell and utilities. The easiest way to get those for Windows is by installing the default set of cygwin utilities.
Before running tomd, use cygwin dos2unix and run it against the tomd file to remove extra linefeeds.
The output of running tomd in the cygwin shell should look very similar to the OSX output above.
The post Upgrading your Textile posts to Markdown appeared first on The GitHub Blog.
]]>