git ssb

Rendering posts example for documentation.

The best use case I've seen for depject is defining different renderers for different scuttlebutt message types. Perhaps we could use this use case for the examples, with some screenshots for different message types? (likes, follows, posts, etc.)

I might have a stab at this some time this week.

I agree that message renderers are a good concrete example that would be useful to someone coming to depject for an SSB project.

The nice thing about the existing examples (the animal noises) is that they work without tying into any other code outside of depject. I don't know if there are any projects outside of the SSB ecosystem that use depject, but I'm sure that Dominic's design was supposed to work outside of SSB.

I think we can have the advantages of both if the worked examples are SSB-inspired rather than directly using any interfaces beyond what's in depject. Maybe include a line like "Secure Scuttlebutt messages actually use a format much like this one" and "some SSB tools use depject code much like this to handle rendering". Maybe a couple of links straight to some relevant code.

Good point =]. I'll try to make it ssb inspired, rather than having to explain a bunch of ssb concepts and leak them into depject's READme =p.

I think I'm going to start with a 'menu items' example (when I next have time - already feeling guilty about not doing anything so far :P) as that's motivated as a use case for 'map' in the section above, and it's a good use case that's easy to give an example without references to external code.

hey @happy0 I only just saw this. I highly recommend tagging things with channels to help people know the space you're speaking into.

to my mind this is #depject and #ssb-learning and maybe #documentation

Cheers @mix . I wasn't actually aware that posts on github issues rendered within patchwork / patchbay, which is why I didn't bother.