perun

Discuss perun static site generator
juhoteperi 2016-02-23T15:11:30.000010Z

Hmm, trying to understand what happened with atom and rss tasks.

juhoteperi 2016-02-23T15:11:51.000011Z

@adamfrey: :site-title and :base-url were the correct names: https://github.com/hashobject/perun/commit/5b7ca79e7130e6e237084a0b8138791915d752dd

juhoteperi 2016-02-23T15:12:01.000013Z

those names are specified in the spec

juhoteperi 2016-02-23T15:12:54.000014Z

Also, atom task is currently creating invalid content (https://t.co/6OAfa1EhJq), I'll fix that but first I need to get those options fixed

adamfrey 2016-02-23T15:15:35.000016Z

ok, I didn’t see the SPEC file. I just knew that the options specified by the task were not being passed to the feed generating code, so the rss and atom-feed tasks were unusable

juhoteperi 2016-02-23T15:16:13.000017Z

Hmm, I think the correct way forward is to revert patch, fix the task options and rename site-description to description as that is what spec defines

adamfrey 2016-02-23T15:16:26.000019Z

yeah, that’s sounds ok to me

juhoteperi 2016-02-23T15:32:56.000020Z

Hmm, fixing Atom feed properly needs real UUID:s for each post.

juhoteperi 2016-02-23T15:36:48.000021Z

We could have a UUID task which prints a warning and suggestion for UUID so user can add the uuid to entry metadata: "Found a entry x.md without uuid, please add following to the metadata: uuid: 1d04f707-4ec9-4a66-9d74-62c739550106"

juhoteperi 2016-02-23T15:54:13.000022Z

We should probably have pre-conditions/assertions/schema specs for properties defined in spec, but not sure if this should be separate task, or if that should be done everywhere the property is used (e.g. base-url)

juhoteperi 2016-02-23T15:54:33.000023Z

If the assertion is checked each time, it should only still be printed once per line for e.g. base-url

juhoteperi 2016-02-23T16:04:47.000024Z

Still few things to implement, but this should output valid Atom feed: https://github.com/hashobject/perun/pull/92