Ideas for Lektor Serverless

10 Ideas For Lektor Serverless

• Add an “Access Log” section to the admin that pulls data from CloudWatch into the Lektor site’s repository

• Add “scheduled posts” to the admin

• Make sure there is a draft status that works with the scheduled posts.

• What are my options for running Gitweb inside of a Lektor Serverless site?

• What are the options for pulling RSS data into a Lektor Serverless site?

• Report AWS costs inside of admin.

• If all of the site content, templates, etc. is on S3, and the Lektor code is on Lambda, what does it look like to edit the site locally and then deploy updates?

• Since deployment of the actual site is always to S3, change the admin interface and functionality so the user doesn’t have to configure anything, they just click “Deploy” and Lektor Serverless knows how to do everything.

• One click export of everything (HTML and Lektor templates, content) to a ZIP File for download.

• Start producing a variety of templates and themes, standardize templates to making moving content between templates easier.