That's a lot of questions, but this may help.
I think your interpretation of "sections" is correct.
The number used for the value of things like includeContent and hideContainers is not an ID. It's either 1 or 0 (meaning yes and no). IOW, &includeContent=`1` means "yes, I'm going to show the content field, so include it and &includeContent=`0` means the opposite.
The &parents property value(s) are the IDs of resources you want to show the children of(i.e., sections).
The &includeTvs property value is the IDs of the TVs you're going to show.
New Resource does mean New Document.
If you have a TV called "tags" you don't need to create another one, but you do need to make sure it's attached to the BlogPostTemplate.
When you use a tag like this:
It will always show the value for the current document. That's not what you want for a listing of blog posts because you want the values from many different documents. In a Tpl chunk, you always use this form:
Tags that start with the + token are placeholder tags. The snippet that retrieves the documents (e.g. getResources) will replace them with the field from each document as it retrieves them.
The tags that start with a ~ are link tags. They get converted to URLs So the example below is a placeholder tag inside a link tag:
The inside tag will be replaced with the ID of the resource (document) and the outer tag will then be replaced with the URL of that document. So the tag will be converted first to something like this:
Then to something like this:
http://alias-of-document-12
So if you have a document titled "Home Page" with an alias of "home-page", when the snippet retrieves that document this:
<a href="[[~[[+id]]]]>[[+pagetitle]]</a>
Will get converted to this:
<a href="http://home-page.html">Home Page</a>
If none of that solves your problems, post the full snippet tag you're using to retrieve the blog posts and the code of the Tpl chunk it uses.
[ed. note: BobRay last edited this post 15 years ago.]