But to give you some idea about my current hobby project. I have monorepo with backend written in Ktor, Android app, iOS app, one module shared across all platforms and one module shared for frontend. So I hope Kobweb will fill the "web frontend" part nicely.

Yeah, I definitely want to add codelabs to introduce the concepts of Kobweb incrementally.

Kobweb is a small crutch I think for Android devs, thanks to its own Modifier class and a few other classes copied over (kind of) from Jetpack Compose, but ultimately the developer still needs to learn JavaScript and CSS APIs.

Note that the blog article linked to above refers to https://bitspittle.dev/blog/2022/kotlinsite which could be a good skim.

I've come to terms with using CSS but I hope I won't have to touch JavaScript a lot 😅 Thanks for the articles 👍

Ah, no JS. You are always writing Kotlin. But the Kotlin is often a thin layer over JS code.

(This isn't Kobweb, btw, but Kotlin/JS itself. For example, you read https://developer.mozilla.org/en-US/docs/Web/API/Window/location but use https://kotlinlang.org/api/latest/jvm/stdlib/org.w3c.dom/-window/location.html)

Good 😄 I have some experience with Kotlin JS (made my own library for Kotlin JVM/JS back in the day) but you scared me with the "developer still needs to learn JavaScript" 😄

Ha, I'll be careful in the future

Btw is there a way to donate and support the project?

Oh, no need at this point. But thanks for the offer!

I think the best way to support the project would be if people end up using it, creating cool stuff, and sharing what they created

Code contributions would be welcome too, or even just if you see typos or other confusing things in the code, just let me know so I can fix it.

Feels like a lot of care went into this project and it would be really sad seeing it die in a year or two so when you open some way of donation, be sure to let me know 👍

So for background, I've got enough savings to run for quite a while. My thought has always been I don't want to make money on Kobweb itself, but maybe I build something with Kobweb that makes money.

I'm assuming at some point Kobweb stabilizes a bit and doesn't need as much energy put into it. If that assumption turns out wrong, then I may revisit my original plan 🙂

You're a good person for asking though. I agree that open source needs more of that!

To be honest, I've never donated to any open source project but Kobweb just amazed me reading through the readme. The fact that you have CLI tool for quickly starting the project, a bunch of demos, gradle plugin and so on... I just felt like this is a passion project worth following

It's definitely a passion project 🙂 and one I plan to use myself. Thanks for the very kind words.

Welcome! I'd love to know the sorts of pain points people are having with Kotlin webdev in general, what kind of projects people are working on / want to work on, what they hope Kobweb might fix, etc.. Just lurking is fine too!

So I've read the articles and came with questions as promised 😄 You mentioned that you wanted full stack solution but you are focusing on static layouts for now. Maybe this is stupid question but what is the other side of "static site". Server-side rendering? Is that something Kobweb supports? Maybe I need to visit your Readme again 😅

Nice to see you got your channel 🙂

Thanks for being the inspiration to take this step! For those who don't know him, Ivan is working on #decouple , a project you might be interested in. The library is an approach to abstract Compose concepts so you can declare widgets at a common layer in a multiplatform project. FAQ here: https://gitlab.com/opensavvy/decouple/-/blob/main/FAQ.md#how-does-decouple-fit-with-other-compose-based-ui-projects

I did a quick view over decouple, the API looks good. A bit simpler/cleaner than decompose. Any reason why Gitlab and not GitHub? Never used gitlab before, do they have stars, sponsorship and the kind of social features GitHub has? I might create an account later to be able to star it

@David Herman I would be interested to learn more about static deployment with Kobweb as I could be interested by leveraging a variation of that in Spring for server-side rendering. I have read https://bitspittle.dev/blog/2022/staticdeploy, and tried https://bitspittle.github.io/kobweb-ghp-demo/. What I would like to understand more is how you switch from the static to the dynamic version. Is there a mechanism to hydrate the server-side generated HTML with handlers, etc?

Is there a way to combine multiple `ComponentStyle`s into on

ComponentStyle

? And is that even something I want to do? I have

MaterialShadowStyle

and now I am creating some specific component that should have this shadow. Is my only option to combine modifiers in the composable?

Compose 1.3.1 (tied to Kotlin 1.8.10) was released two days ago. Kobweb 0.12.1 has just been published, to support it.

Kobweb 0.12.3 was published today. Compared to 0.12.1 I announced two weeks ago, this release adds: • radial gradient support via a Kotlin-idiomatic API • various server improvements including better dependency support (dependencies can use reflection / services now) and crash stack reporting • simplified the API around configuring where links open (in place vs. new tab) https://github.com/varabyte/kobweb/releases/tag/v0.12.3

I am extremely proud to mention that one of Kobweb's users, Stevdza-San (YouTube channnel here), has just released a course on using Compose for Web to develop websites, featuring Kobweb.