Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Lektor – A Static File Content Management System For Python

lucumr.pocoo.org

Post reply on HN
Print view View original

11–20 of 94 posts

Re: Introducing Lektor – A Static File Content Management System For Python

#11

Post by detaro »

the_mitsuhiko wrote: post #9
detaro wrote: post #7

Earlier quoted context omitted.

the ini-file configuration seems a bit strange to me(esp since it seems to be ini-files that occasionally contain python code). Why did you go with them instead of making these python classes? To allow the GUI to edit parts of them as well?

> the ini-file configuration seems a bit strange to me(esp since it seems to be ini-files that occasionally contain python code). Why did you go with them instead of making these python classes? To allow the GUI to edit parts of them as well? I grew to heavily dislike the idea of just executing random code to configure things. Impossible to expose to tools, even harder to reason about it. Note that these files do not…

Thanks. Yes, the code-as-configuration thing is difficult, it invites people to do very strange things sometimes.

    [children]
    replaced_with = site.query('/projects').filter(F.categories.contains(this))
(from the categories example) looked a lot like embedded code to me ;)

Re: Introducing Lektor – A Static File Content Management System For Python

#12

Post by the_mitsuhiko »

detaro wrote: post #11
the_mitsuhiko wrote: post #9

Earlier quoted context omitted.

> the ini-file configuration seems a bit strange to me(esp since it seems to be ini-files that occasionally contain python code). Why did you go with them instead of making these python classes? To allow the GUI to edit parts of them as well? I grew to heavily dislike the idea of just executing random code to configure things. Impossible to expose to tools, even harder to reason about it. Note that these files do not…

Thanks. Yes, the code-as-configuration thing is difficult, it invites people to do very strange things sometimes. [children] replaced_with = site.query('/projects').filter(F.categories.contains(this)) (from the categories example) looked a lot like embedded code to me ;)

Since there is no SQL I'm using the expression language from the templates for queries :)

Re: Introducing Lektor – A Static File Content Management System For Python

#13

Post by qwertyuiop924 »

I always love Armin's stuff. In quality, it's often near that oh-so-very-special spot that is reserved for Steve Yegge's best posts. Now I will simultaneously be lynched by both the people who think that Steve sucks, and the people who think that Steve's stuff is 1 million times better than anything Armin could ever post. Not to mention 500 other groups who I don't even know.

Re: Introducing Lektor – A Static File Content Management System For Python

#14

Post by techdragon »

the_mitsuhiko wrote: post #3

Direct links to project: * Website: https://www.getlektor.com/ * Github: https://github.com/lektor/lektor Would be really curious to hear how people like it :)

It's quite late for me so I've only had time to read the documentation, but so far I love what I see. I've had a goal of building the static site tool I've wanted to use for a long time now, name chosen and everything, but you may have built something nice enough I don't need to.

If this is as nice yo use as the documentation leads me to believe it will be, I may just turn some of my existing exploratory code into plugins for this instead of building my own entire tool around them.

Re: Introducing Lektor – A Static File Content Management System For Python

#15

Post by subnaught »

bliti wrote: post #5
the_mitsuhiko wrote: post #3

Direct links to project: * Website: https://www.getlektor.com/ * Github: https://github.com/lektor/lektor Would be really curious to hear how people like it :)

Very nice. I had been building the same thing after wanting something more than pelican and less than wordpress. This seems to fit perfectly. Is there a roadmap for contributing to the project? I failed to see one on github.

Would you mind listing some specific features you're interested in? I ask because I've recently switched from WordPress to Pelican, and I'm quite happy, so far at least.

Re: Introducing Lektor – A Static File Content Management System For Python

#16

Post by Torgo »

pkd wrote: post #4

I love Armin's work, especially Flask, but this seems like lot of other products out there. I have no incentive to switch to this from the generator I'm already using, and for non-techy people I think it's still a big jump in terms of just opening up a tumblr blog.

What other static file CMS are you using?

Re: Introducing Lektor – A Static File Content Management System For Python

#19

Post by freyr »

the_mitsuhiko wrote: post #3

Direct links to project: * Website: https://www.getlektor.com/ * Github: https://github.com/lektor/lektor Would be really curious to hear how people like it :)

You need to make sure you have the following software installed on your computer:

- Python 2.7 (not Python 3.x)

I've read some of your remarks about Python 3, but it seemed like you were (at least begrudgingly) accepting the shift to Python 3. So why no forwards compatibility here? Any plans to support Python 3 in the future?

Re: Introducing Lektor – A Static File Content Management System For Python

#20

Post by mxuribe »

This is great! I'm using pelican and while a very good tool, I was considering building out a desktop/local-front-end for it...But this is MUCH better than what I could build (with my current level of expertise)...i think i'll be using this, and seriously consider contributing! Kudos @mitsuhiko!
Post reply on HN