Does it support some kind of live preview mode (like with HarpJS) ?
Introducing Lektor – A Static File Content Management System For Python
81–90 of 94 posts
Re: Introducing Lektor – A Static File Content Management System For Python
#82In my view a content only API would be more disruptive. A smart content API as a service could be used for any project. Give it a beautiful interface for authors and focus on the writing experience.
Maybe this is Mediums potential new market/ platform. What if you could grab and query your content with a smart api with graphql? No updates, servers, etc.
Any new project I used, I grab my content from this saas and use whatever tech/framework I want. Why aren't more devs looking at this as an option going forward?
Re: Introducing Lektor – A Static File Content Management System For Python
#83I'm really suffering from an acute case of Analysis Paralysis when it comes to Static Site Generators. The offerings on the market are overwhelming and you don't know which one to pick, do you go with an incumbent or mainstream like Jekyll with a huge selection of functionality at your disposal or go for the underdog and minimal one offering just the basics or just build your own framework and adapt to the evolving n…
Re: Introducing Lektor – A Static File Content Management System For Python
#84Respectfully, I don't think this puts this project outside the scope of any other static site generators as listed. In my view a content only API would be more disruptive. A smart content API as a service could be used for any project. Give it a beautiful interface for authors and focus on the writing experience. Maybe this is Mediums potential new market/ platform. What if you could grab and query your content with…
The only thing it's missing from your description is graphql. :)
Re: Introducing Lektor – A Static File Content Management System For Python
#85I 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
#86I'm really suffering from an acute case of Analysis Paralysis when it comes to Static Site Generators. The offerings on the market are overwhelming and you don't know which one to pick, do you go with an incumbent or mainstream like Jekyll with a huge selection of functionality at your disposal or go for the underdog and minimal one offering just the basics or just build your own framework and adapt to the evolving n…
Re: Introducing Lektor – A Static File Content Management System For Python
#87Earlier quoted context omitted.
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?
I build this originally for myself and i don't use python 3. I'm happy to accept patches for python 3. I think it should not be hard.
Great to see another useful bit of software created. Did you miss the opportunity to build it in Python3?
Re: Introducing Lektor – A Static File Content Management System For Python
#88Earlier quoted context omitted.
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
#89Earlier quoted context omitted.
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.
https://web.archive.org/web/20020210134317/http://www.blogge... it was shut down in 2010 http://blogger-ftp.blogspot.com/2010/01/deprecating-ftp.html
Re: Introducing Lektor – A Static File Content Management System For Python
#90Earlier quoted context omitted.
What other static file CMS are you using?
I don't use a static file "CMS", but I use my own generator[1] which I made because I wanted something really fast. If you want a flat file cms, then a Google search will throw a lot of them. Kirby is the most popular, IMO. But it's not FLOSS. PicoCMS ticks all those boxes though. [1] https://github.com/pawandubey/griffin