Introducing Lektor – A Static File Content Management System For Python
1–10 of 94 posts
Re: Introducing Lektor – A Static File Content Management System For Python
#2Armin Ronacher just makes more and more awesome stuff. I think I'm going to ditch my pelican site, and go for Lektor.
Re: Introducing Lektor – A Static File Content Management System For Python
#3Direct links to project:
* Website: https://www.getlektor.com/
* Github: https://github.com/lektor/lektor
Would be really curious to hear how people like it :)
Re: Introducing Lektor – A Static File Content Management System For Python
#4I 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.
Re: Introducing Lektor – A Static File Content Management System For Python
#5Direct 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.
Re: Introducing Lektor – A Static File Content Management System For Python
#6I 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.
As he said in blog, another framework is not enough easy use for non-tech user
Re: Introducing Lektor – A Static File Content Management System For Python
#7Direct links to project: * Website: https://www.getlektor.com/ * Github: https://github.com/lektor/lektor Would be really curious to hear how people like it :)
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?
Re: Introducing Lektor – A Static File Content Management System For Python
#8I 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.
> for non-techy people I think it's still a big jump in terms of just opening up a tumblr blog
True, but that's not the audience anyways. The idea is that if you (as a web developer) want to make a portfolio site for a customer you could use lektor instead of wordpress or something like this. I generally always prefer static website generators for my own work but I cannot give it to a non technical person to fill with content. That's what motivated it.
But nobody needs to switch for anything. It's just another tool in the shed :)
Re: Introducing Lektor – A Static File Content Management System For Python
#9Direct links to project: * Website: https://www.getlektor.com/ * Github: https://github.com/lektor/lektor Would be really curious to hear how people like it :)
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 contain python code at all. They just sometimes contain little Jinja templates.
The idea is indeed that the GUI can eventually edit some of these things. It also is already used for `lektor plugins add` for instance which updates the project ini file.
Lastly the reason ini over yaml is purely that this can preserve comments and doing the same for yaml is a lot more work i did not have time for :)
Re: Introducing Lektor – A Static File Content Management System For Python
#10Direct 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.
> Is there a roadmap for contributing to the project? I failed to see one on github.
Nope. Hoping to get some feedback to see what people need. It does what I need pretty much at the moment. Just figured i add some docs and share it as some sort of Christmas or whatever else you celebrate present.