Improvement: remove pages/ idiom now that non-page files can be served out of it #9

New Issue

bss · 2021-04-14T21:21:55-05:00

bss commented

2021-04-14 21:21:55 -05:00

Right now we have instance/pages/ and instance/media/, but if we're going to serve files directly from the same directory as markdown now (as of ced67bec8b), we don't really need the distinction and I think I should just flatten everything.

Right now we have `instance/pages/` and `instance/media/`, but if we're going to serve files directly from the same directory as markdown now (as of ced67bec8bbb2f8deb4992f3432da7241c90edac), we don't really need the distinction and I think I should just flatten everything.

bss commented

2021-04-14 21:40:27 -05:00

Actually, I shouldn't "flatten" everything because we need to protect config.py from being served, so I guess I should just keep instance/pages and maybe rename it to site or content or something.

Actually, I shouldn't "flatten" everything because we need to protect `config.py` from being served, so I guess I should just keep `instance/pages` and maybe rename it to `site` or `content` or something.

bss commented

2021-05-07 00:09:25 -05:00

Closing this, pages is fine enough for now.

Closing this, `pages` is fine enough for now.

bss closed this issue

2021-05-07 00:09:25 -05:00

Sign in to join this conversation.