just said
siteSourceDirectory := target.value / "web" / "public" / "main" / "examples"
A-Frame Hepek?
although it is more like a dynamic thing, probably more suited for ScalaJS
DOM manipulation etc
If someone has time: https://www.w3schools.com/icons/fontawesome5_intro.asp
e.g. with a definition like:
def syncAlt(mods: Seq[FaModifier] = Seq.empty, styles: Seq[StylePair] = Seq.empty)
0.4.0 is released! :smiley:
featuring Play framework support
I had no chance in previous days to follow all the occurred changes of the source code, but today I am trying to fix some of the Bulma issues although I found it already changed
I wanted to extract these "components" in a separate project
so it can be used in different contexts: Static site generator and Play framework
Play doesn't need some classes like StaticPage, blog support, automatic paths etc
I did some work on Bulma also, you probably saw that
Grid now works fine, forms need some more work :)
Also, started to extract these common classes like btnSuccess, btnDanger etc in Classes trait
yup, great :smile:
"hepek-components" should contain universal components
that work with both Bootstrap and Bulma
If you manage to make that work, it would be great :slight_smile:
otherwise, we'll leave them as is
see
GridComponents for example
so to wrap up my understanding:
hepek-components is for common scaffolding, while all the custom part should goes under hepek module itself
you can remove those enrichClass.. stuff
Is there a reason why you are using a snapshot scalatags version from
ba.sake instead of com.lihaoyi?