sake92/hepek

Generate static sites directly from Scala code

Sakib Hadžiavdić

@sake92

https://github.com/sake92/play-hepek-example

Peter Pan

@P3trur0

hi @sake92 could you please explain how it now works in detail the hepek-components part?

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

Sakib Hadžiavdić

@sake92

@P3trur0 yeah, sorry about that.. :D

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

Sakib Hadžiavdić

@sake92

Makes sense? xD

Peter Pan

@P3trur0

Yup, I see. So basically the stuff in hepek Is no more necessary? For example all the components written so far

Sakib Hadžiavdić

@sake92

Well, hepek (SSG) depends on components

Peter Pan

@P3trur0

Since now there are Form and Grid ones in hepek-components, right?

Sakib Hadžiavdić

@sake92

they're just moved in a subproject

Peter Pan

@P3trur0

Ok, clear 🙂

Sakib Hadžiavdić

@sake92

If someone needs "a bunch of scalatags helpers" he can use hepek-components

yup, great :smile:

Peter Pan

@P3trur0

But for example, assuming we'd like to use Bulma CardComponent, do we have to import the new bulmatextclasses?

Sakib Hadžiavdić

@sake92

I didn't have time to migrate all those components

"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

Sakib Hadžiavdić

@sake92

We have an implementation for Bulma and for Bootstrap, and can easily switch from one to other

Peter Pan

@P3trur0

perfect then

so to wrap up my understanding: hepek-components is for common scaffolding, while all the custom part should goes under hepek module itself

Sakib Hadžiavdić

@sake92

Yes, kinda, use hepek for experimenting

Peter Pan

@P3trur0

ok :smile:

Sakib Hadžiavdić

@sake92

btw, i fixed that bug with repeating cls := ..

you can remove those enrichClass.. stuff

Peter Pan

@P3trur0

cool

Alex Bush

@alexjbush

Hey, I love this lib btw

Is there a reason why you are using a snapshot scalatags version from ba.sake instead of com.lihaoyi?

Sakib Hadžiavdić

@sake92

@alexjbush thanks, and welcome! :smiley:

there was a bug in scalatags, it merged repeated attributes

see lihaoyi/scalatags#182

I guess we could update it to scalatags 0.7.0 now :)

Alex Bush

@alexjbush

Ah great :D

Sakib Hadžiavdić

@sake92

object MultiPage extends Multi {

  def rends = Seq(PageImpl("1"), PageImpl("2"))
}

case class PageImpl(name: String) extends Renderable {

  override def relPath = Paths.get(s"examples/simple/multi/$name.txt")

  override def render = s"multi$name"
}

Finally got it working! :smile:

Could be that I broke something, please report if you find something

Anyway, new version of sbt-hepek is 0.2.0

it supports MultiRenderable

which enables you to render multiple pages from one template

you can call DB, Wordpress API or something dynamic now!

And got it rendered to static pages! :smiley:

Sakib Hadžiavdić

@sake92

New hepek SSG version is 0.6.0 with ScalaMultiRenderable support

Here's example how to use it: https://github.com/sake92/hepek-examples/tree/master/src/main/scala/examples/multi/wordpress

Where communities thrive

People

Repo info

Activity