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

41–50 of 94 posts

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

#41

Post by ngrilly »

the_mitsuhiko wrote: post #38
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.

I think that's why we have so many static site generators. However programmers typically end up just making the static site generator which is why there was nothing like Lektor before (to the best of my knowledge at least).

I remember that Blogger, in the beginning, used to work as a static site generator. You edited your posts in the user interface, and you could publish the result to a static hosting via FTP.

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

#43

Post by crdoconnor »

the_mitsuhiko wrote: post #35
crdoconnor wrote: post #28

Earlier quoted context omitted.

>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 :) Was that the only thing that bothered you about YAML/pyyaml or were there other things you'd like to see fixed?

YAML is really quite complex. I like it in general but it's impossible to dump the data out without destroying the structure of the file (throw away comments, change whitespace, formatting style etc.)

Did you look at https://pypi.python.org/pypi/ruamel.yaml ?

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

#45

Post by the_mitsuhiko »

crdoconnor wrote: post #43
the_mitsuhiko wrote: post #35

Earlier quoted context omitted.

YAML is really quite complex. I like it in general but it's impossible to dump the data out without destroying the structure of the file (throw away comments, change whitespace, formatting style etc.)

Did you look at https://pypi.python.org/pypi/ruamel.yaml ?

Nope. Did not see it. That's neat though. Would probably have done it differently in that case, but no real reason to switch now.

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

#46

Post by currysausage »

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.

Let's not forget that Lektor solves actual problems. Show me another CMS that offers:

- Static HTML export with elegant dependency tracking by design (reducing attack vectors and maintenance cost on the frontend server)

- Admin interface (I can't tell a non-techie to connect via SSH, fire up vi and run Jekyll)

- Flexible content structure (Title/Author/Content doesn't really scale beyond a simple blog)

- Elegant design and implementation (I could do anything with WordPress and half a dozen plugins, but I fail to even find a bare-bones theme without kilobytes of code that I will never need; the whole ecosystem revolves around the novice user who understandably prefers "quick and dirty" over touching code)

I have been looking for a CMS that fulfills these exact criteria for quite some time. Lektor looks ideal for projects where the developer prepares a non-trivial page structure (think book listings, music albums, anything that goes beyond bold and italic), but the client should be able to edit content. Thank you, Armin!

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

#47

Post by gotchange »

currysausage wrote: post #46
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.

Let's not forget that Lektor solves actual problems. Show me another CMS that offers: - Static HTML export with elegant dependency tracking by design (reducing attack vectors and maintenance cost on the frontend server) - Admin interface (I can't tell a non-techie to connect via SSH, fire up vi and run Jekyll) - Flexible content structure (Title/Author/Content doesn't really scale beyond a simple blog) - Elegant desi…

Did you test this generator in production? If not, the verdict is not out yet on Lektor and remains to be seen how it will fare in production environments and on the battlefields.

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

#50

Post by gotchange »

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 you go along.
Post reply on HN