Octopress/Non-blog Octopress Site - Revision history

Admin at 11:17, 14 April 2014

2014-04-14T11:17:34Z

← Older revision		Revision as of 11:17, 14 April 2014
Line 1:		Line 1:
	This is a guide to using Octopress for a (mostly) non-blog site.		This is a guide to using Octopress for a (mostly) non-blog site. See an example of this workflow in action here: http://charlesreid1.github.io/cantera-book

	NOTE: This does not prevent you from using the blog features of Octopress. Fixed content can be served by Octopress alongside blog content. It just describes how to reorganize content to be less blog-centric.		NOTE: This does not prevent you from using the blog features of Octopress. Fixed content can be served by Octopress alongside blog content. It just describes how to reorganize content to be less blog-centric.

Admin: /* For Files in Subdirectory of Source Directory */

2014-04-14T07:51:21Z

For Files in Subdirectory of Source Directory

@@ Line 173: / Line 173: @@
 ==For Files in Subdirectory of Source Directory==
-If you are trying to link to another file from a subdirectory of the source directory, you'll need to modify the link schema a bit.
+===Link to Content in Same Directory===
 Let's say we're trying to add a link in <code>source/section1/chapter1.markdown</code> to the file <code>sources/test.html</code>, one directory up. Then our link schema would look like:
@@ Line 188: / Line 207: @@
 |<pre>[This links to our test](../test.html)</pre>
 |}
 [[Category:Octopress]]

Admin: /* Inter-Octopress Links */

2014-04-14T07:48:59Z

Inter-Octopress Links

← Older revision		Revision as of 07:48, 14 April 2014
Line 174:		Line 174:

	If you are trying to link to another file from a subdirectory of the source directory, you'll need to modify the link schema a bit.		If you are trying to link to another file from a subdirectory of the source directory, you'll need to modify the link schema a bit.

			Let's say we're trying to add a link in <code>source/section1/chapter1.markdown</code> to the file <code>sources/test.html</code>, one directory up. Then our link schema would look like:

			{\|
			\|-
			\|Location (project repo)
			\|\|<pre>cantera-book/octopress/source/test.markdown</pre>
			\|-
			\|Location (URL)
			\|<pre>charlesreid1.github.io/cantera-book/test.html</pre>
			\|-
			\|Corresponding Markdown code
			\|<pre>[This links to our test](../test.html)</pre>
			\|}

			NOTE: If you add a relative Markdown link to a file, it will create a link to that file IN THE SAME DIRECTORY. Thus, the Markdown:

			<pre>
			[Don't link this way](test.html)
			</pre>

			would create a (broken) link to:

			<pre>
			charelsreid1.github.io/cantera-book/section1/test.html
			</pre>




	[[Category:Octopress]]		[[Category:Octopress]]

Admin: /* For Content in Base Source Directory */

2014-04-14T07:45:55Z

For Content in Base Source Directory

← Older revision		Revision as of 07:45, 14 April 2014
Line 139:		Line 139:
	then it can link to other markdown files in the <code>source</code> directory by linking to the HTML file that the Markdown will turn into (once Jekyll is run via rake generate).		then it can link to other markdown files in the <code>source</code> directory by linking to the HTML file that the Markdown will turn into (once Jekyll is run via rake generate).

	~~Here is how you can~~ link to ~~other files from a file~~ in the ~~base source~~ directory:		===Link to Content in Same Directory===

			To link to content in the same directory, e.g., to link from index.html to test.html,

	{\|		{\|
			\|-
	\|Location (project repo)		\|Location (project repo)
			\|<pre>cantera-book/octopress/source/test.markdown</pre>
			\|-
	\|Location (URL)		\|Location (URL)
			\|<pre>charlesreid1.github.io/cantera-book/test.html</pre>
			\|-
	\|Corresponding Markdown code		\|Corresponding Markdown code
			\|<pre>[This links to our test](test.html)</pre>
			\|}

			===Link to Content in Subdirectory===

			To link to content in a subdirectory, e.g., to link from index.html to section1/chapter1.html,

			{\|
	\|-		\|-
	\|<pre>cantera-book/octopress/source/~~test~~.markdown~~</pre>~~		\|Location (project repo)
	~~\|<pre>charlesreid1.github.io/cantera-book/test.html</pre>~~		\|\|<pre>cantera-book/octopress/source/section1/chapter1.markdown</pre>
	~~\|<pre>[This links to our test](test.html)~~</pre>
	\|-		\|-
	\|~~<pre>cantera-book/octopress/source/section1/chapter1.markdown</pre>~~		\|Location (URL)
	\|<pre>charlesreid1.github.io/cantera-book/section1/chapter1.html</pre>		\|<pre>charlesreid1.github.io/cantera-book/section1/chapter1.html</pre>
			\|-
			\|Corresponding Markdown code
	\|<pre>[This links to chapter one](section1/chapter1.html)</pre>		\|<pre>[This links to chapter one](section1/chapter1.html)</pre>
	\|}		\|}

Admin: /* Non-Blog Landing Page */

2014-04-14T07:43:01Z

Non-Blog Landing Page

@@ Line 68: / Line 68: @@
 blog_index_dir  = 'source/blog'
 </pre>
 [[Category:Octopress]]

Admin at 02:15, 14 April 2014

2014-04-14T02:15:04Z

← Older revision		Revision as of 02:15, 14 April 2014
Line 68:		Line 68:
	blog_index_dir = 'source/blog'		blog_index_dir = 'source/blog'
	</pre>		</pre>


			[[Category:Octopress]]

Admin: /* Non-Blog Landing Page */

2014-04-14T02:14:51Z

Non-Blog Landing Page

@@ Line 21: / Line 21: @@
 </pre>
-Now we can either make a new index page with Markdown, or we can make an HTML page by hand.
+==Make New Index==
 The first way looks like this:
@@ Line 47: / Line 49: @@
 <pre>
 cp /path/to/my/index.html source/.
 </pre>

Admin: Created page with "This is a guide to using Octopress for a (mostly) non-blog site. NOTE: This does not prevent you from using the blog features of Octopress. Fixed content can be served by Octopr..."

2014-04-14T02:11:01Z

Created page with "This is a guide to using Octopress for a (mostly) non-blog site. NOTE: This does not prevent you from using the blog features of Octopress. Fixed content can be served by Octopr..."

New page

This is a guide to using Octopress for a (mostly) non-blog site.

NOTE: This does not prevent you from using the blog features of Octopress. Fixed content can be served by Octopress alongside blog content. It just describes how to reorganize content to be less blog-centric.

=Non-Blog Landing Page=

The first thing to do when deploying a non-blog site with Octopress is fixing the landing page so that it doesn't try and show the latest blog posts. This is straightforward to do.

==Move Blog Index==

First, we don't want to blow away our existing blog index, because we may want to keep using the blog feature. Assuming you're in your project's octopress directory,

<pre>
cd cantera-source/octopress/
</pre>

you can move the existing blog index from <code>source</code> to <code>source/blog</code>:

<pre>
mv source/index.html source/blog/index.html
</pre>

Now we can either make a new index page with Markdown, or we can make an HTML page by hand.

The first way looks like this:

<pre>
touch source/index.markdown
</pre>

and index.markdown should look like this:

<pre>
---
layout: default
---

# Howdy

Welcome to the index.
</pre>

(Or you can use whatever layout you want.)

If you have your own HTML file, you can just put it there:

<pre>
cp /path/to/my/index.html source/.
</pre>