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…
Introducing Lektor – A Static File Content Management System For Python
51–60 of 94 posts
Re: Introducing Lektor – A Static File Content Management System For Python
#52My 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…
Re: Introducing Lektor – A Static File Content Management System For Python
#53Earlier 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.)
Re: Introducing Lektor – A Static File Content Management System For Python
#54Re: Introducing Lektor – A Static File Content Management System For Python
#55I 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
#56If you're thinking that the scene of MVC JavaScript frameworks resembles more of the good ol' days of the Wild Wild West, wait to see how things are currently like on the SSG front.
Re: Introducing Lektor – A Static File Content Management System For Python
#57Earlier quoted context omitted.
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…
GravCMS perhaps? http://getgrav.org
Re: Introducing Lektor – A Static File Content Management System For Python
#58Armin, are you not afraid that having to install Lektor locally could be a serious obstacle for "people that have no understanding of programming"?
Re: Introducing Lektor – A Static File Content Management System For Python
#59I do have two questions, though. Why the new file extension (.lr) and the field separator?
Jekyll's front matter format is easier for most people - and my engine uses a plain newline to separate front matter from text, and supports multiple file extensions to make it easier for desktop editors.
Re: Introducing Lektor – A Static File Content Management System For Python
#60My 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…