clo / cl-site public

Mariano Montone (@mmontone) on GitLab, 2018-10-13.

Erik Huelsmann (@ehuelsmann) on GitLab, 2018-10-13.

@mmontone are you 100% sure this actually does anything? I think this file isn't included in the published result...

Mariano Montone (@mmontone) on GitLab, 2018-10-13.

Yes, it does. They are styles for community page

Mariano Montone (@mmontone) on GitLab, 2018-10-13.

I can see that the file is being used because styles in the site actually change :)

Erik Huelsmann (@ehuelsmann) on GitLab, 2018-10-13.

Ok. I wonder how, because the file isn't here: https://common-lisp.net/static/css/

Mariano Montone (@mmontone) on GitLab, 2018-10-13.

It's included from here: https://common-lisp.net/layout_2018.css

We may want to revise that and put it in static folder.

Erik Huelsmann (@ehuelsmann) on GitLab, 2018-10-13.

Thanks. I missed that completely. I have to revise my own merge request which cleans up unused files.

Erik Huelsmann (@ehuelsmann) on GitLab, 2018-10-13.

I've actually revised it already. I'm wondering if the static assets really belong in content/static/ as it's really part of the template definition and not (mostly) part of the actual content.

Do we have good definitions what goes into layout and what goes into content?

Mariano Montone (@mmontone) on GitLab, 2018-10-13.

Mm..no, we don't have good definitions for that as far as I know.