Categories

[eshlox]

It would be great to have possibility to use categories, not just tags. ;-)

[asetsuna]

I also think categories are very important for separating posts. Pelican supports it while nikola not. So I have to escape from nikola.

[posativ]

Support for categories will make it definitely into the next major release (0.8).

[maphew]

This is possible now, from the github version; the below adapted from an email exchange between myself and Martin:

... I want example.com/Musings/foo-baz, as the permanent URL, where "Musings" is the primary or first tag assigned to the post.

the current syntax only allows access to a single attribute (e.g. :name gets the attribute "name" from the entry instance), but what you want is basically categories (I think) and you can achieve this with a custom attribute, let's call it "category":

---
title: Foo
category: musings  # or musings/baz
---

and add /:category/:slug/ as URL rule, so in conf.py:

    '/:category/:slug/': {'views': ['entry', 'draft']},    #new way 
    #'/:year/:slug/': {'views': ['entry', 'draft']},        #default blog way, now commented out

---

You'll need to delete the .cache and output before compiling again (the former to avoid tracebacks and the latter to avoid duplicates posts between the old and new path structures).

I'm using this method right now at www.maphew.com

[posativ]

You'll need to delete the .cache [...] to avoid tracebacks

This is definitely a bug, the cache should not throw tracebacks when you change your configuration.

[hooli]

Similar to maphew comment, I found this rule works, which might be helpful for 0.7

'/:topic/:slug.html': {'view': 'page', 'template': 'flatpage.html' , "if": lambda e: hasattr(e, 'topic') },
'/:slug.html': {'view': 'page', 'template': 'flatpage.html' , "if": lambda e: hasattr(e, 'topic') == False },

The page will use the second rule if it doesn't have a topic.

The initial category support looks great. Just wondered:

a) Would it be possible to have a list of root directories to exclude from being categorized?

b) Could be useful to have the full category path "x/y/z" as a variable for any route rule, in addition to :name on category views.

c) Presume infile metadata overriding the defaults for directory path and the category array will be available in the templates

[posativ]

The page will use the second rule if it doesn't have a topic.

Yes, I implemented the "if": lambda ... exactly for such purposes, but I am still not satisfied with this solution as the lambda expression grows bigger as you want more filtering rules. I still think about a exclusion of posts that match the "if": lambda-clause like this:

VIEWS = {
    '/:topic/slug.html': {..., 'if': lambda ..., exclude=True},
    '/:slug.html': {...}  # no lambda expression required
}

Should be possible with an ordered dict (some ast magic).

The initial category support looks great. Just wondered:

a) Would it be possible to have a list of root directories to exclude from being categorized?

It should be definitely possible to exclude certain root directories and/or sub directories. Maybe with a path translation lambda/function, where you can modify the directory inserted as :name, e.g.:

def foo(category):
    # do something with category, e.g. category.replace('topic/', '')
    return category

[...]

`/category/:name.html`: {'view': category, 'translate': foo},

b) Could be useful to have the full category path "x/y/z" as a variable for any route rule, in addition to :name on category views.

Should be possible, if you add e.g. /:category/:year-:month-:day/:slug.html as entry route. This replaces :category with entry.category which is either set in the metadata or retrieved from the path (but it is not affected by a path translation function mentioned above, though). (entry.category should probably always return the category name after the path translation has been performed.)

c) Presume infile metadata overriding the defaults for directory path and the category array will be available in the templates

Yes, that's still on my todo list.