What would it take to make the tour a library.

[CrowdHailer]

I would like to be able to write tours for other things, explained in Gleam.
For example things I would personally like to write are.

• An OTP tour
• Implementing typechecking in Gleam
• Implementing an interpreter in Gleam

It would be great if there was a way to something like the following

// my_tour.gleam
import gleam/tour

pub fn main() {
  tour.build("/build", pages())
}

fn pages() {
  [
    tour.Page(
      title: "Getting started with OTP",
      content: "First we need to introduce processes"
      code: "
        import gleam/otp

        // ..."
    )
  ]
}

I'm happy to help contribute to such a thing. But I think it needs a bit of design work to work out what the interface is and what should be exposed.

[lpil]

The tour hasn't really been designed to be used a library so it would be tricky, and OTP wouldn't be possible as it runs on JavaScript rather than Erlang.

[CrowdHailer]

Good point on OTP.

I understand that it was not designed this way. However if I found a way to make it more library friendly, would that be an interesting contribution. Or should I just be copy/pasting the code to my projects

[lpil]

Forking is probably the best for now as I'm not sure how we could make it into a library.