more docs

crates/crabslab/README.md

@@ -1,12 +1,52 @@
-<div align="center">
-    <img src="crabslab.png" alt="slabcraft for crabs" width="512" />
+<div style="float: right; padding: 1em;">
+    <img src="https://github.com/schell/renderling/blob/main/crates/crabslab/crabslab.png?raw=true" alt="slabcraft for crabs" width="256" />
 </div>
 
 ## What
 
 `crabslab` is a slab implementation focused on marshalling data between CPUs and GPUs.
 
-### example
+[See the example below](#example).
+
+## But Why?
+It's hard to get data onto GPUs in the form you expect.
+
+To marshall your data correctly you must know about the alignment and sizes of the underlying representation of your data.
+This will often surprise you!
+
+Working with a slab on the other hand, only requires that your types can be written into an array and read from an array.
+
+### Opinion
+Working with _shaders_ is much easier using a slab.
+
+Shader code can be written in Rust with [`rust-gpu`](https://github.com/EmbarkStudios/rust-gpu),
+which will enable you to use this crate on both CPU and GPU code.
+
+### rust-gpu
+This crate was made to work with [`rust-gpu`](https://github.com/EmbarkStudios/rust-gpu/).
+Specifically, with this crate it is possible to pack your types into a buffer on the CPU
+and then read your types from the slab on the GPU (in Rust).
+
+### Other no-std platforms
+Even though this crate was written with `rust-gpu` in mind, it should work in other `no-std`
+contexts.
+
+## And How
+`crabslab` includes:
+* a few traits:
+  - `Slab`
+  - `GrowableSlab`
+  - `SlabItem`
+* a derive macro for `SlabItem` for your structs
+* a few new structs for working with slabs
+  - `Id`
+  - `Array`
+  - `Offset`
+* a helper struct `CpuSlab` which wraps `Vec<u32>` or `WgpuBuffer`
+* a feature-gated helper for using slabs with `wgpu` - `WgpuBuffer`
+  - [example](src/wgpu_slab.rs#L344)
+
+# Example
 ```rust
 use crabslab::{CpuSlab, Slab, GrowableSlab, SlabItem, Id};
 use glam::{Vec3, Vec4};
@@ -52,41 +92,3 @@ let (light_id, slab) = cpu_code();
 // marshalling your data depends on which GPU library you are using...
 shader_code(light_id, &slab);
 ```
-
-## But Why?
-It's hard to get data onto GPUs in the form you expect.
-
-To marshall your data correctly you must know about the alignment and sizes of the underlying representation of your data.
-This will often surprise you!
-
-Working with a slab on the other hand, only requires that your types can be written into an array and read from an array.
-
-### Opinion
-Working with _shaders_ is much easier using a slab.
-
-Shader code can be written in Rust with [`rust-gpu`](https://github.com/EmbarkStudios/rust-gpu),
-which will enable you to use this crate on both CPU and GPU code.
-
-### rust-gpu
-This crate was made to work with [`rust-gpu`](https://github.com/EmbarkStudios/rust-gpu/).
-Specifically, with this crate it is possible to pack your types into a buffer on the CPU
-and then read your types from the slab on the GPU (in Rust).
-
-### Other no-std platforms
-Even though this crate was written with `rust-gpu` in mind, it should work in other `no-std`
-contexts.
-
-## And How
-`crabslab` includes:
-* a few traits:
-  - `Slab`
-  - `GrowableSlab`
-  - `SlabItem`
-* a derive macro for `SlabItem` for your structs
-* a few new structs for working with slabs
-  - `Id`
-  - `Array`
-  - `Offset`
-* a helper struct `CpuSlab` which wraps `Vec<u32>` or `WgpuBuffer`
-* a feature-gated helper for using slabs with `wgpu` - `WgpuBuffer`
-  - [example](src/wgpu_slab.rs#L344)