Most collections in the system have at least one of these kinds of items.
- Question
- Video
- Photo
- Blog
- Place
- Product
- Testimonial
- Page
- Offer
- Database
Please read the Collections document to see how each of these are structured.
This is the minimum code you'll need to display any one of these collection items (example is a Blog post):
When creating a page to represent any of these, you also need to decide how its permalink is structured. Permalinks are the permanant URL's to all of these individual pages representing a single item. These links will never change once created.
Choosing your permalink structure.
When creating the URL you have certain segments available to you:
When creating the URL you have certain segments available to you:
:year
:monthnum
:day
:minute
:second
:id
:permalink (title converted to URL safe link, eg: "This is cool" = "this-is-cool")
:postname (same as permalink)
:category (permalink of category name)
:username (username of person who created the post)
:author (same as username)
:parent_permalink (if the post has a parent)
Examples:
/blog/:category/:permalink
Results in: /blog/business/10-things-to-do-in-new-york
Results in: /blog/business/10-things-to-do-in-new-york
/blog/:id
Results in: /blog/123
/:year/:month/:day/:permalink
Results in: /2013/04/28/10-to-things-to-do-in-new-york
You can use any of the segments to create permalinks of any complexity you like. You can also change the permalink structure at any time -- the old permalinks will still work (they will not change either).
Choose your permalink structure for maximum efficiency of your readers (and SEO).
Don't add too many segments. Too many permalink segments make it hard for your readers to type out the url.
Our favorite permalink is this one:
/:category/:permalink
This would give us a nice, simple permalink like:
/travel/10-things-to-do-in-new-york
Last updated 11 months ago