Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Web Development with Htmx, Type-Guided Components, Pure Python

getludic.dev

Post reply on HN
Print view View original

1–10 of 39 posts

Show HN: Web Development with Htmx, Type-Guided Components, Pure Python

#1

Post by paveldedik »

Ludic is my personal project I started working on as I saw an opportunity to write websites in Python without the need to use template engines and write complex JavaScript (thanks to htmx.org). Ludic prioritizes simplicity - no convoluted HTML, straightforward and responsive CSS, and minimal JavaScript requirements.

I'm looking for feedback for the documentation I was building:

* https://getludic.dev/docs/

This documentation showcases the range of features the framework offers, providing a comprehensive overview of its capabilities.

I would also appreciate if you checked the layouts section and tell me what you think:

* https://getludic.dev/catalog/layouts

Additionally, I've developed a convenient cookiecutter template:

* https://github.com/paveldedik/ludic-template

I eagerly await your feedback and insights as you explore these resources.

I believe Ludic can be expecialy good for personal blogs, project websites, in-browser slides, while using htmx.org properties to add interactivity.

Since my last update on Ludic, I've concentrated on the following areas:

* Building comprehensive documentation with Ludic to showcase its capabilities * Enhancing the UI components catalog * Crafting Layout Components inspired by the Every Layout Book * Introducing support for Themes

Future plans for Ludic include:

* Enhancing HTMX support with compatibility for HTMX 2.0 * Implementing speed improvements through caching * Expanding the features in the catalog * Improving typing support * Exploring the creation of a cookiecutter template for generating Ludic-powered slides

Show HN: Web Development with Htmx, Type-Guided Components, Pure Python
getludic.dev

Re: Show HN: Web Development with Htmx, Type-Guided Components, Pure Python

#4

Post by pbronez »

pbronez wrote: post #2

On mobile, when I hit the docs link, the actual content falls below the fold. The search bar and ToC take up the whole screen. Recommend you collapse the ToC to a menu button and shrink the search bar.

You might expand on your examples to demonstrate persistence. You mention that the cookie cutter template has “many modules are missing, such as models and database connections.” I think this is a meaningful gap to fill.

The initial button example might be a good one to build on. You could show how to persist the counter value in SQLite.

Re: Show HN: Web Development with Htmx, Type-Guided Components, Pure Python

#6

Post by pbronez »

pbronez wrote: post #4
pbronez wrote: post #2

On mobile, when I hit the docs link, the actual content falls below the fold. The search bar and ToC take up the whole screen. Recommend you collapse the ToC to a menu button and shrink the search bar.

You might expand on your examples to demonstrate persistence. You mention that the cookie cutter template has “many modules are missing, such as models and database connections.” I think this is a meaningful gap to fill. The initial button example might be a good one to build on. You could show how to persist the counter value in SQLite.

It would be nice to have a “next page” button at the bottom of the documentation pages, so you can read straight through without popping back up to the ToC.

Re: Show HN: Web Development with Htmx, Type-Guided Components, Pure Python

#7

Post by paveldedik »

pbronez wrote: post #6
pbronez wrote: post #4

Earlier quoted context omitted.

You might expand on your examples to demonstrate persistence. You mention that the cookie cutter template has “many modules are missing, such as models and database connections.” I think this is a meaningful gap to fill. The initial button example might be a good one to build on. You could show how to persist the counter value in SQLite.

It would be nice to have a “next page” button at the bottom of the documentation pages, so you can read straight through without popping back up to the ToC.

Thank you very much, really good advice here.
Post reply on HN