I cannot see a page being generated for each tag listed in the YAML front matter about assemble.io HOT 6 CLOSED

Try downloading https://github.com/assemble/assemble-contrib-permalinks and have a look at the tests. In particular these tests. Be sure to open the compiled pages in the browser to see the result, it really helps to see them functioning (at least it did for me)

from assemble.io.

thx a lot for the quick response! :)

However I still don't get it. For example, the article in https://github.com/assemble/assemble-contrib-permalinks/blob/master/test/fixtures/pages/articles/bar.hbs has a bbb tag, but a bbb folder is nowhere to be found in https://github.com/assemble/assemble-contrib-permalinks/tree/master/test/actual. Which is contrary to saying "For each category and tag, Assemble will generate a page in the dest directory." and to what the example

<ul>
  {{#tags}} 
  <li><a href="/tag/{{tag}}.html">{{tag}}</a></li>
  {{/tags}}
</ul>

is suggesting at http://assemble.io/docs/options-collections.html#usage-examples.

But probably I'm just misunderstanding something here.

from assemble.io.

@manofewords I don't think the docs are completely correct on this (at this time). We had been planning a feature to be be able to create an "index" page for each tag, but that hasn't been implemented yet. I think @jonschlinkert has been able to create a similar effect using the permalinks plugin and specifying tags in the url structure, but I don't think it gets all the way to the "index" page.

Also, I think the example would work in that it would generate the markup, but there wouldn't be a {{tag}}.html page to point to.

Sorry for the confusion, there's a lot of things we talking about with features and sometimes the docs get left behind. Thanks for pointing this out because it's something that I need get better at keeping on top of.

from assemble.io.

excellent. Thanks for the clarifications! :)

from assemble.io.

I don't think the docs are completely correct on this (at this time)

Thanks @doowb, agreed. I think if you just follow the real-world examples you'll be better off. I am very, very close to having a refactor of docs done, after which it will be much easier for others to do PRs to add to them or fix them.

from assemble.io.

Closing since this seems to have been resolved. please reopen if necessary

from assemble.io.