adding some info on binding in docs

1 files changed, 17 insertions, 1 deletions

diff --git a/docs/rendering.md b/docs/rendering.md
index 5b1dfe2..b7bc5f6 100644
--- a/docs/rendering.md
+++ b/docs/rendering.md
@@ -10,4 +10,20 @@ Rendering is split into 3 'registers'.
 ## RAL
 
 - RAL doesn't know what 'meshes' are or 'materials', it purely deals with buffers, textures, pipelines, etc. Those concepts
-  are left to the `Render` module.
\ No newline at end of file
+  are left to the `Render` module.
+
+## Render
+
+## Adding shader effects
+
+A few decisions have affected how shader data binding works in the RAL and if you're coming from purely OpenGL with floating uniforms like
+
+```glsl
+uniform mat4 viewProjection;
+```
+it might feel a little complicated. However, this setup helps us abstract over different graphics API backends as well as be more performant in the general case
+with more data uploaded in one call.
+Because of the lack of generics in C, we adopt a `void*` data with a function pointer returning a "layout" for bindings that the backend can then interpret in order
+to know how to bind that specific data. This means you will need to do a little bit of work creating a function for each shader data binding. We'll look at an example:
+
+**TODO: ShaderBinding / Layout example**
\ No newline at end of file