diff --git a/_sidebar.md b/_sidebar.md
index 564e9f8..2bf83e8 100644
--- a/_sidebar.md
+++ b/_sidebar.md
@@ -15,6 +15,7 @@
   - [Making Elements](/guide/making-elements)
   - [Compatibility](/guide/compatibility)
   - [Debugging](/guide/debugging)
+  - [Custom Rendering](/guide/custom-rendering)
   - [Contributing](/guide/contributing)
 
 - **Examples**
diff --git a/_sidebar.src.md b/_sidebar.src.md
index dd24587..ba60429 100644
--- a/_sidebar.src.md
+++ b/_sidebar.src.md
@@ -15,6 +15,7 @@
   - [Making Elements](/guide/making-elements)
   - [Compatibility](/guide/compatibility)
   - [Debugging](/guide/debugging)
+  - [Custom Rendering](/guide/custom-rendering)
   - [Contributing](/guide/contributing)
 
 - **Examples**
diff --git a/guide/custom-rendering.md b/guide/custom-rendering.md
new file mode 100644
index 0000000..4296ee9
--- /dev/null
+++ b/guide/custom-rendering.md
@@ -0,0 +1,64 @@
+# Custom Rendering
+
+To set up custom rendering, for example for use cases like custom post-processing
+effects, the underlying Three.js WebGL renderer and Lume's customized CSS renderer
+can be accessed from a `<lume-scene>` using the `.glRenderer` and `.cssRenderer`
+properties.
+
+```html
+<lume-scene id="some-scene"> ... </lume-scene>
+
+<script>
+	const someScene = document.getElementById('some-scene')
+
+	// Get the Three.js WebGLRenderer
+	const glRenderer = someScene.glRenderer
+</script>
+```
+
+The the scene's `drawScene` property can be assigned a new function to define
+how to renderer in any custom way. For example, here we render the scene with
+the scene's currently-active camera, which is what Lume does by default:
+
+```js
+someScene.drawScene = () => {
+	glRenderer.render(someScene.three, someScene.threeCamera)
+
+	// If you also need CSS rendering, don't forget to use cssRenderer here too.
+}
+```
+
+The `drawScene` function is automatically called any time the scene needs to
+re-render (for example due to changing attributes or properties of any Lume
+elements in the scene).
+
+If we want to implement custom [post-processing effects with
+Three.js](https://threejs.org/docs/index.html#manual/en/introduction/How-to-use-post-processing),
+we can do so:
+
+```js
+const composer = new EffectComposer(renderer)
+
+const renderPass = new RenderPass(someScene.three, someScene.threeCamera)
+composer.addPass(renderPass)
+
+const glitchPass = new GlitchPass()
+composer.addPass(glitchPass)
+
+const outputPass = new OutputPass()
+composer.addPass(outputPass)
+
+someScene.drawScene = () => {
+	// Ensure we render with whichever Lume camera is currently active (f.e. in
+	// case the user toggles the `active` attribute on various
+	// `<lume-perspective-camera>` elements).
+	renderPass.camera = scene.threeCamera
+
+	composer.render()
+
+	// If you also need CSS rendering, don't forget to use cssRenderer here too.
+}
+```
+
+Note, the [`postprocessing`](https://npmjs.com/postprocessing) package provides
+an alternative set of post-processing effects.