Github頁面添加隨機標籤到我的帖子

Question

如果您訪問我的網站，您會注意到最近的文章（在主頁上）標題包裹在<pre>標記中，並重復。我不知道爲什麼會發生這種情況。

這裏是正在顯示的帖子：

--- 
layout: default 
--- 

Stop distributing .doc files 
---------------------------- 
Monday March 19th, 2012 

`.doc` started as a file format used by many operating systems and used to store only plain-text. In the 90's, Microsoft decided to use the extension for Word -- their new word processor. Not only did they decide to use the extension, but they also broke the standard by using a proprietary format, instead of the plain-text most people were used to. Despite the `.doc` extension being more than **10 years old** and the fact that most documents formatted this way render horribly in operating systems other than Windows, I still regularly receive documents in this format. Stop it. 

However aggravating the above paragraph is, this article isn't solely targeted at the `.doc` extension -- it is a public plea for people to stop distributing application specific documents and to start distrubting all documents in `.pdf`. 

Yesterday I received an email from an engineering society I'm a part of. They were notifying all members of the upcoming annual general meeting that is taking place next week. I immediately lost interest in the email when I saw that their meeting schedule and their nomination form were both in `.docx` format. I don't like being forced to download the file, minimize my browser, launch an Office application (in my case, LibreOffice) and then read the content. Had it been distributed in `.pdf`, Chrome would have immediately opened a new tab for me displaying the document and giving me options to save, zoom or print it. I'm sure Firefox, Opera and (maybe) Internet Explorer have similar features. 

We are increasingly collaborating on the web, and the need for bulky desktop applications are almost gone with the wind. Had I not had an office application on my computer (which could have been possible seeing as I do most of my documentation and report with LaTeX), I would have had an extra step before viewing the content that was sent to me. It's not like it is difficult either. All major office applications I know of allow easy exporting to `.pdf` file format and LibreOffice also allows you to save a hybrid `.pdf` and `.odt` together in one file. This allows you to distribute the PDF as is and also open it for editing. 

There is virtually no need to distribute documents in any format, proprietary or not, other than PDF. Don't make your users work and fiddle with your flatform-specific or application-dependent documents. 

這裏是我的默認佈局（相關部分，您可以查看任何其他來源）：

<div id="right-side"> 

      {{ content }} 

      <div id="footer"> 
       <p> 
        &copy; {{ site.author.name }} 2012 with help from 
        <a href="http://jekyllbootstrap.com" target="_blank">Jekyll Bootstrap</a> 
       </p> 
      </div> 
     </div> 

你可以看到，佈局只是簡單地轉儲right-side div中的降價文件的內容。如果您訪問我的網站上的其他頁面/帖子，您會看到這些頁面可以正常工作，但不是主頁（儘管它們處於相同的標記格式並使用相同的佈局）。

任何想法？

Answer 1

問題是在your index page上的循環。縮進（有點）由Liquid保存：文本替換是一個文字替換，它意味着第一行將縮進，但後面的行不會縮進。 index.md（first.content已經是HTML）的降格處理髮生在Liquid運行後，所以縮進被解釋爲代碼塊。

在處理中的步驟（這不一定在每一步逐字輸出，但是這將是接近）：

{% for first in site.posts limit:1 %} 
    {{ first.title }} 
    {{ first.content }} 
{% endfor %} 

之後有液體運行index.md：

Stop distributing .doc files 
    <h2>[...]</h2> 

<p>Monday March 19th, 2012</p> 

[...] 

現在Markdown運行，並且縮進意味着前兩行是代碼塊：

<pre><code>Stop Distributing .doc Files 
&lt;h2 id='stop_distributing_doc_files'&gt;Stop distributing .doc files&lt;/h2&gt;</code></pre> 
<p>Monday March 19th, 2012</p> 

這可以通過沒有如此大的縮進for循環的元素來解決：使用4個空格或製表符縮進代碼塊。所以

{% for first in site.posts limit:1 %} 
    {{ first.title }} 
    {{ first.content }} 
{% endfor %}