title: How to use pelican to generate a hierarchical website, not a blog
body: <p>I'm trying to use Pelican to generate a hierarchy of .html files, with a hierarchy of .html and .md files as input. </p>
  
  <p>Pelican has a lot of great features, but it is focused on generating a <em>blog</em>, not a static, hierarchical website. Sure, it has that <code>pages</code> subdirectory, but it doesn't respect subfolders in that directory; instead, it tries to flatten all of the files it finds into the same directory, and then complains that it will "overwrite" files with the same slug.</p>
  
  <p>I'm used to managing large sets of web pages in subfolders. When I put <code>file.html</code> in subfolder <code>mysite/a</code>, I expect the URL to be something like <code>https://myserver/mysite/a/file.html</code>. But apparently Pelican (and Jekyll) think one folder should be enough for anybody. Am I missing something? Or is Pelican so focused on blogging they are just not up to the job of really generating and managing static sites?</p>
  
  <p>Pelican seems like really cool tool. The source is very well-written, and it has lots of nice options. But I'm starting to think that it's really not for generating static sites, but rather for generating static blogs. Is anyone else using it the way I'm suggesting?</p>