octopress | 易学教程

markdown table with long lines

阅读更多关于 markdown table with long lines

问题 I am using markdown in order to create a table. My Description column contains very long texts and therefor it looks very bad on the markdown file when I wrap lines: Argument | Description | -------- | ----------- | appDir | The top level directory that contains your app. If this option is used then it assumed your scripts are in |a subdirectory under this path. This option is not required. If it is not specified, then baseUrl below is the anchor point for finding things. If this option is

markdown table with long lines

阅读更多关于 markdown table with long lines

Wrong number of arguments (1 for 2) while serving Jekyll

阅读更多关于 Wrong number of arguments (1 for 2) while serving Jekyll

问题 Fresh installation of Jekyll and Octopress. On starting the server, it yields: Homes-MacBook-Pro:octopress home$ jekyll serve Configuration file: /Users/home/octopress/_config.yml Source: source Destination: public Generating... error: wrong number of arguments (1 for 2). Use --trace to view backtrace on performing the trace: Homes-MacBook-Pro:octopress home$ jekyll serve --trace Configuration file: /Users/home/octopress/_config.yml Source: source Destination: public Generating... /Users/home

11个最流行的静态(博客)网站生成工具

阅读更多关于 11个最流行的静态(博客)网站生成工具

11个最流行的静态(博客)网站生成工具最近特别流行使用静态网站搭建博客，本博客就是host在GitHub Pages的静态网站。静态网站非常适合专注于内容的网站，例如，博客。那你可能会问，为什么不用大名顶顶的wordpress（动态网站）呢。静态网站和动态网站相比有如下好处：省钱。静态网站占用的系统资源少。如果挂到github pages上，只要注册一个域名就可以了。速度快。不经过php解析器，不用数据库，速度自然比动态网站快安全。由于静态网站的简洁，免疫很多web攻击方式。服务器端配置简单。只需要一个web server（apache、nginx）。非常容易维护。静态网站的缺点是功能弱，和用户的交互能力不强。静态网站生成工具能从简单的纯文本文件生成一个网站/博客。常用文本格式有reStructuredText和Markdown，我习惯使用Markdown。如果你想搭建自己的静态网站，你可以选用下面列出的11个工具。 Jekyll Jekyll 做为GitHub Pages的构建工具（Ruby语言），使它成为最流行的静态网站生成工具。Jekyll的流行也因为它非常简单，只需要基础的web开发基础。你可以使用它轻易的把文本转换为自定义的网站/博客。如果你有wordpress或其他博客站点，你可以导入到Jekyll中。Jekyll支持插件、标签等等。 Github

Invalid Byte Sequence in US-ASCII (Argument Error) 问题修复

阅读更多关于 Invalid Byte Sequence in US-ASCII (Argument Error) 问题修复

在使用Octopress（rake命令时报错） invalid byte sequence in US-ASCII (Argument Error) when I run rake 修复方法终端执行 1 export RUBYOPT = "-KU -E utf-8:utf-8" 或者将上面的代码内容放到.bashrc中。来源： oschina 链接： https://my.oschina.net/u/4312789/blog/4266881

Octopress not loading css

阅读更多关于 Octopress not loading css

问题 i'm having an issue configuring Octopress on Nginx When i run rake preview everything runs correctly i can acces http://xxx:4000 and the blog looks just fine when i run rake deploy i can still access blog on http://xxxx/octopress but looks like no css/js when i explore the code and try to reach screen.css the link to css is http://xxxx/stylesheets/screen.css but it must be http://xxxx/octopress/stylesheets/screen.css here are the extract on Rakefile and _config.yml conf # --------------------

Add properties to a page from a Jekyll plugin

阅读更多关于 Add properties to a page from a Jekyll plugin

问题 Say I want to have a page with content like this: <h1>{{page.comment_count}} Comment(s)</h1> {% for c in page.comment_list %} <div> <strong>{{c.title}}</strong><br/> {{c.content}} </div> {% endfor %} There are no variables on the page named comment_count or comment_list by default; instead I want these variables to be added to the page from a Jekyll plugin. Where is a safe place I can populate those fields from without interfering with Jekyll's existing code? Or is there a better way of

Git commit ERROR: Repository invalid

阅读更多关于 Git commit ERROR: Repository invalid

问题 I recently came across the octopress blogging platform and followed the installation instructions. I am hosting it on github using github pages. I created a repository and successfully managed to make an initial commit. My problem came when I tried to make another commit and this is the message I got: Immanuels-MacBook-Pro:octopress manuweg$ git add . Immanuels-MacBook-Pro:octopress manuweg$ git commit -m "Changed origin url" [source e0fff54] Changed origin url 1 files changed, 1 insertions(+

Discrepency in “rake preview” vs. “rake deploy”

阅读更多关于 Discrepency in “rake preview” vs. “rake deploy”

问题 I am having an issue where I can "rake preview" and view the site in a browser on localhost:4000 and everything seems to be displayed properly (fonts, styles, posts, text, asides, etc). However, when I "rake deploy" (which I have set to sync to Amazon S3), the site displays in such a way that it almost appears as if the CSS is missing, mis-configured, etc. I have verified that the path referenced for the "/stylesheets/screen.css" exists in S3 and that the browser can open it. I have even done

Discrepency in “rake preview” vs. “rake deploy”

阅读更多关于 Discrepency in “rake preview” vs. “rake deploy”