But the plan is also to start moving pieces of Jumpy into a

bones_runner

( or maybe

bones_app

, name subject to ideas ) crate, that provides a lot of things jumpy is doing itself right now like UI, localization, matchmaking, etc.

Once we get a few of those pieces moved into

bones_app

, then the current

jumpy

crate starts to disappear, and it becomes pretty much just

jumpy_core

as a "core" that gets run with

bones_app

.

Once we get to that point, that means you could make a

bomby

"bones core" that pretty much is just run with

bones_app

and you'll get networking, localization, settings, input, etc. essentially for free, with hardly any effort on your part.

Because the concept between the bones cores will all be similar.

----

Things are probably going to play out a little different than that, and we'll have more of an in-between in the short term, where

bones_app

is doing certain things for us, but there's still going to be some custom code in jumpy and bomby.

But that kind of shows the idea.

I just got the updated bones docs pushed.

I made an updated [introduction page](https://fishfolk.github.io/bones/introduction.html).

And added a basic [ECS tutorial](https://fishfolk.github.io/bones/ecs_tutorial/index.html).

There's more to add tutorials for still, but it's a good start.

Are you okay with tagging the current release v0.1.0? Even a v0.0.1 would be fine, as long as it gets a version other than 0, heh.

Yeah, I'd be good doing a

v0.1.0

.

I've run into fewer and fewer changes that I've needed to make, so now's not a bad time to make a first release.

Nice!

Maybe the docs can link out to one or two good examples of item implementations?

Sure, that's not a bad idea.

Show real world usage.

We’ll soon want dedicated tutorials for that, but for now just the code examples should suffice.

You think that should be in the bones docs, or the Jumpy docs, though?

The item example links.

I was actually thinking it’d be best to have it all in one book. All the games and bones together in one big resource. We wanna be bringing them all closer together anyhow.

Maybe some day Bones will outgrow the Fish series of games, but for now they’re all quite interdependent.

Ah, I see.

In that case, maybe it'd be good to do a proper fishfolks website with all the docs in it.

I can take the existing home page, and then create docs pages for bones and the games in it.

I could use the docs template I started with for the [Raui website](https://raui-labs.github.io/raui/) maybe.

Then we could just migrate our markdown docs from both Jumpy and bones into the new site.

So using Zola instead of mdBook?