0ct0pu5/Pico
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

content-sample/index.md: Fix syntax

Browse source
This commit is contained in:
Daniel Rudolf 2015-12-21 03:24:32 +01:00
parent daca1b7495
commit fdf81672a8
1 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
content-sample/index.md
View file

@ -11,18 +11,18 @@ Congratulations, you have successfully installed [Pico](http://picocms.org/).
## Creating Content ## Creating Content
Pico is a flat file CMS. This means there is no administration backend or Pico is a flat file CMS. This means there is no administration backend or
database to deal with. You simply create `.md` files in the `content` folder and database to deal with. You simply create `.md` files in the `content` folder
those files become your pages. For example, this file is called `index.md` and and those files become your pages. For example, creating a file called
is shown as the main landing page. `index.md` will make it show as your main landing page.
When you install Pico, it comes with a `content-sample` folder. Inside this When you install Pico, it comes with a `content-sample` folder. Inside this
folder is a sample website that will display until you add your own content. folder is a sample website that will display until you add your own content.
You should create your own `content` folder in Pico's root directory and place You should create your own `content` folder in Pico's root directory and place
your files there. No configuration is required, Pico will automatically use the your files there. No configuration is required, Pico will automatically use the
`content` folder if it exists. `content` folder if it exists.
If you create a folder within the content folder (e.g. `content/sub`) and put an If you create a folder within the content folder (e.g. `content/sub`) and put
`index.md` inside it, you can access that folder at the URL an `index.md` inside it, you can access that folder at the URL
`http://example.com/?sub`. If you want another page within the sub folder, `http://example.com/?sub`. If you want another page within the sub folder,
simply create a text file with the corresponding name and you will be able to simply create a text file with the corresponding name and you will be able to
access it (e.g. `content/sub/page.md` is accessible from the URL access it (e.g. `content/sub/page.md` is accessible from the URL
@ -71,7 +71,7 @@ As a common practice, we recommend you to separate your contents and assets
(like images, downloads, etc.). We even deny access to your `content` directory (like images, downloads, etc.). We even deny access to your `content` directory
by default. If you want to use some assets (e.g. a image) in one of your content by default. If you want to use some assets (e.g. a image) in one of your content
files, you should create an `assets` folder in Pico's root directory and upload files, you should create an `assets` folder in Pico's root directory and upload
your assets there. You can then access them in your markdown using your assets there. You can then access them in your markdown using
<code>&#37;base_url&#37;/assets/</code> for example: <code>&#37;base_url&#37;/assets/</code> for example:
<code>!\[Image Title\](&#37;base_url&#37;/assets/image.png)</code> <code>!\[Image Title\](&#37;base_url&#37;/assets/image.png)</code>
@ -101,7 +101,7 @@ There are also certain variables that you can use in your text files:
can be specified using <code>&#37;base_url&#37;?sub/page</code> can be specified using <code>&#37;base_url&#37;?sub/page</code>
* <code>&#37;theme_url&#37;</code> - The URL to the currently used theme * <code>&#37;theme_url&#37;</code> - The URL to the currently used theme
* <code>&#37;meta.&#42;&#37;</code> - Access any meta variable of the current * <code>&#37;meta.&#42;&#37;</code> - Access any meta variable of the current
page, e.g. <code>&#37;meta.author&#37;</code> is replaced with `Joe Bloggs` page, e.g. <code>&#37;meta.author&#37;</code> is replaced with `Joe Bloggs`
### Blogging ### Blogging