# Logs for #nikola for 2016-02-25

15:13:38 <davidak> hello. i am planing to migrate a wordpress and a dokuwiki to nikola. it will have a very minimalistic design where you can find articles from tags or archive. how can i structure pages so users find interesting topics? can i also display pages on tag pages? my first idea was a 'all pages' site, but that would be very chaotic because i have all topics i'm interested in there…
15:15:36 <davidak> are there maybe good examples of websites with lots of pages how to present them?
15:52:22 <ChrisWarrick> davidak: Search, related articles (via a plugin and some JS), STORY_INDEX for a basic list of everything
15:53:13 <davidak> is there a related articles plugin for nikola?
15:53:17 <ChrisWarrick> davidak: yes
15:54:23 <ChrisWarrick> davidak: or maybe not. https://plugins.getnikola.com/#recent_posts_json is sort of close; I guess you could somehow adapt it to your needs
16:02:59 <davidak> can i also display pages on tag pages?
16:03:10 <davidak> by default there are only articles
16:04:34 <davidak> i will look into the conf.py but maybe you know IF that is possible?
16:08:44 <ChrisWarrick> davidak: pages don’t support tags, sorry
16:10:08 <davidak> when i use nikola new_page, there is tags etc in the template
16:10:25 <ChrisWarrick> davidak: we ignore that though
16:10:31 <davidak> oh
16:10:40 <ChrisWarrick> davidak: we use the same template for posts and pages, with only the word post/page changing
16:11:01 <davidak> so i should create an issue to change that :D
16:11:09 <davidak> and then change it :D
16:11:27 <davidak> (when i have free time)
16:11:33 <ChrisWarrick> davidak: no
16:12:21 <ChrisWarrick> davidak: we’re reluctant to supporting page tags, and changing the templates is problematic
16:13:00 <davidak> ok
16:30:49 <davidak> is there a discussion to maybe allow tags in posts optionally?
16:31:06 <davidak> i found https://github.com/getnikola/nikola/issues/2107
16:33:20 <ChrisWarrick> davidak: not sure; you can always create one
16:34:16 <davidak> that issue implies that post (should) have tags
16:34:58 <ChrisWarrick> a post may have tags. a page does not have tags.
16:35:52 <davidak> the assumption of the issue: "we have a post / page. It has a tag"
16:37:33 <ChrisWarrick> Whatever.
16:38:30 <ChrisWarrick> A post may have 0, 1, 2, or as many tags as you can fit in RAM/the filesystem/…. A page does not care about its tags, other than special tags like mathjax, but we do not do any of the tag-specific pages for them
16:39:26 <davidak> as i understand the text in the linked issue, it is planned that pages do have tags just like posts
16:40:22 <ChrisWarrick> it only says “page” once in that context
16:40:30 <davidak> yes
16:40:49 <davidak> do i understand that wrong?
16:40:59 <ChrisWarrick> I don’t interpret it as “let’s have page tags”. And, to be honest, it would be quite hard to make look and work good
16:41:25 <ChrisWarrick> Actually, I think I just came up with the perfect solution for you.
16:42:03 <davidak> just use posts for all content? :D
16:42:18 <ChrisWarrick> It’s our favorite hack, the post list directive.
16:42:28 <ChrisWarrick> You can ask it to display posts and pages at once.
16:42:42 <ChrisWarrick> You can’t ask for pages only, though (at least right now, make an issue or even a PR for it)
16:42:57 <ChrisWarrick> https://getnikola.com/handbook.html#post-list
16:44:08 <davidak> looks good, thank you
16:44:57 <gour> ChrisWarrick: hiya, should i take silence on the list in regard to my post as clear sign there is no interest for Nikola to be flat-file cms?
16:45:18 <ChrisWarrick> gour: You’re assuming I know the minds of Nikola users.
16:45:38 <ChrisWarrick> gour: I do know that our definitions of CMS differ dramatically.
16:45:46 <gour> ChrisWarrick: well, at least devs, to some extent :-)
16:46:32 <ChrisWarrick> ralsina: Please try and respond to gour’s e-mail to nikola-discuss about flat file CMS, if you have the time and an idea.
16:48:02 <ChrisWarrick> gour: to me, a CMS involves an admin panel and is usable by non-tech-savvy users.  Nikola does not have a good admin panel (coil is so-so) and it requires Unix skills.
16:49:16 <ChrisWarrick> WordPress install instructions: 1. get an account on any shared hosting server, even a free one.  2. download a zipball, extract, upload files to server.  3. open webby installer.  4. welcome to wordpress. “techy” things end here.
16:50:32 <ChrisWarrick> Nikola install instructions: 1. Install a Python interpreter of the right version. 2. Install virtualenv and pip. 3. Install Nikola; you will need to take extra care for lxml and Pillow. 4. Run nikola init. 5. Run nikola build whenever you write a post in a cryptic plain text format. 6. To deploy, run nikola deploy, which requires messing with some Python syntax
16:51:12 <gour> ChrisWarrick: well, Grav is usable even without admin panel...Lektor is also interesting as 'desktop' app...the point is that for some sites with more than one user, one needs an easy(er) way for some user to contribute content...
16:51:26 <ChrisWarrick> gour: Lektor is as much of a desktop app as Coil.
16:52:17 <ChrisWarrick> It’s just a Flask server that you run locally. Something you can do with Coil just fine.
16:52:35 <gour> ChrisWarrick: but it handles, afaik, media, while with Coil only plain text pages are possible, right?
16:59:01 <ChrisWarrick> gour: Define plain text pages?
16:59:38 <gour> ChrisWarrick: e.g. without images
16:59:40 <ChrisWarrick> gour: It’s true Coil does not support image uploads.
16:59:44 <ChrisWarrick> gour: But you can add existing images.
17:00:23 <gour> well, usually one who submits new post, has some new media to add as well...
17:01:02 <ChrisWarrick> gour: Adding image uploads, especially now with the image rendering architecture in Nikola, should take you a few hours to implement
19:48:47 <travis-ci> Wheelhouse build by Chris Warrick: The build has errored. See https://travis-ci.org/getnikola/wheelhouse/builds/111836358.
19:49:03 <travis-ci> Wheelhouse build by requires.io: The build has errored. See https://travis-ci.org/getnikola/wheelhouse/builds/111836370.
19:52:32 <ChrisWarrick> (ignore those)
22:40:45 <[Tritium]> calling build repeatedly will trigger copy_assets: ... code.css no matter if something has changed or not
22:43:29 <[Tritium]> touch theme/<my theme>/assets/css/code.css fixed that