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

71–80 of 94 posts

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

#71

Post by hanniabu »

the_mitsuhiko wrote: post #65
hanniabu wrote: post #60

Earlier quoted context omitted.

A few alternatives.... http://getgrav.org/ http://getcockpit.com/ http://harpjs.com/

Correct me if I'm wrong but they are either hosted CMS solutions (Grav, Cockpit) or static website generators (Harp) like Jekyll and friends.

Harp actually is a static generator (didn't think it was, never used before).

And yes, Grav and Cockpit are self-hosted flat-file CMS, but now that you ask makes me confused. I was under the impression that Lektor was similar where you have a flat-file CMS and whenever a change is made, the static files are created.

My second guess is that this actually a CMS that exists locally and deploys static files when a change is made?

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

#72

Post by jnbiche »

gotchange wrote: post #50
vinceguidry wrote: post #29

My feeling is that every serious programmer will end up inventing tools like this simply because the overhead of incorporating other people's tools eventually starts to overtake the overhead of maintaining one's own system.

That's the problem with Static Site Generators (SSG) in general. They're opinionated by nature and the learning curve could prove steep to process all the details of the configurations necessary to get the maximum mileage out of the framework but as you dig deeper and deeper, you realize that you'd be better off building your own framework that's fit to your objectives and use cases and improve and expand on that as…

I disagree. The great thing about SSGs like Jekyll and Middleman is that they're very easy to build plugins for. Jekyll in particular is easy to learn, and easy to expand. I honestly can't imagine a bona fide programmer having that much difficulty picking up Jekyll.

If you did want to build a custom SSG, I think you're best bet is starting from Gulp, and building from there. At least then you can leverage the Gulp ecosystem instead of re-building everything yourself.

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

#73

Post by detaro »

hanniabu wrote: post #71
the_mitsuhiko wrote: post #65

Earlier quoted context omitted.

Correct me if I'm wrong but they are either hosted CMS solutions (Grav, Cockpit) or static website generators (Harp) like Jekyll and friends.

Harp actually is a static generator (didn't think it was, never used before). And yes, Grav and Cockpit are self-hosted flat-file CMS, but now that you ask makes me confused. I was under the impression that Lektor was similar where you have a flat-file CMS and whenever a change is made, the static files are created. My second guess is that this actually a CMS that exists locally and deploys static files when a change…

Lektor is a static site generator: it generates a "compiled" version of the site that is uploaded to a simple web server, without any server-side scripts running. If you want to edit something, you run it locally, make your changes, generate new files and copy those to the web server.

The key addition is that there is a nice UI for adding content in the system running locally, so it can be used by less technical users that might not feel comfortable with writing in text files with special tags/metadata, as traditional static generators require.

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

#75

Post by programminggeek »

This looks really interesting. I always love seeing new static site builders. Each one is a bit different, which is cool.

I'm working on making hosting for static sites easier. My static hosting service is still in beta, but we have a sign up form if people are interested. http://www.statichosting.co/

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

#76

Post by the_mitsuhiko »

voltagex_ wrote: post #58
ngrilly wrote: post #44

Armin, are you not afraid that having to install Lektor locally could be a serious obstacle for "people that have no understanding of programming"?

I wonder how hard it'd be to bundle up into a single executable that the user could run. I know I've been battling with Python -> exe tools ever since I started using Python, though.

There is a bundled cersion for osx with a ui. Just didn't have the time to do it for windows and linux.

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

#78

Post by wuster »

dwightgunning wrote: post #24

This looks great! The native desktop app is a powerful way to drive adoption with non-technical people. Cactus was on the right track with that although I'm fairly sure the author, Koen Bok is now focussed on his company, Framer. Are there plans to build clients for other platforms? I guess the community can jump in at any time. Sidenote: do people know of native clients for the other major static site generators lik…

I want to also vote up Cactus despite the lack of attention paid to it lately. IMO it's very well designed and deserves to be worked on by a wider community.

It's open sourced via BSD 3 clause: https://github.com/koenbok/cactus

I especially liked the "deploy to s3" feature, IMO the cheapest way to run a highly scalable static site today.

Alternatively, a "deploy to GitHub page" would be neat as well.

I would work on extending Cactus if it was a bigger problem personally, but so far what's released fits my needs already.

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

#79

Post by jeffwidman »

> Lektor belongs to a separate org and the project does not use any resources only I have access to (other than the domain name and the server travis-CI deploys to).

Really appreciate you starting it out this way from the getgo.

> Because I run so many Open Source projects and maintenance of all of them turns out to be tricky I figured I do this better this time around.

Looking forward to seeing Flask & Flask-SQLAlchemy moved to a dedicated Flask org on github. Ideally with another person or two having Pypi creds for pushing releases.

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

#80

Post by hasenj »

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 :)

I always love your work, Armin. Definitely sounds like something I've been looking for for ages. Definitely will give it a try.
Post reply on HN