Skip to content

Commit 3acaa62

Browse files
authored
Update README.md
1 parent 75de86f commit 3acaa62

File tree

1 file changed

+2
-10
lines changed

1 file changed

+2
-10
lines changed

README.md

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,10 @@ Copyright and license free library of shaders and explanations to empower develo
88

99
So you want to add your own articles or other stuff to this project. That's awesome, there's just a few rules for contribution.
1010

11-
### Rule 1
12-
Use the ShaderToy uniforms in all of your code.
11+
If the ShaderToy uniforms (below) has a variable for something you need in your shader, use it. If not, follow the ShaderToy naming style and explain what the variable is in your article. An example of this would be if you need the camera position for your shader to function. Define it as `iCameraPosition`, and also specify the type. So, `uniform vec3 iCameraPosition`.
1312

1413
```js
15-
Shader Inputs
14+
// ShaderToy uniforms
1615
uniform vec3 iResolution; // viewport resolution (in pixels)
1716
uniform float iTime; // shader playback time (in seconds)
1817
uniform float iTimeDelta; // render time (in seconds)
@@ -29,17 +28,10 @@ For certain effects that may use more then four input channels, you should speci
2928

3029
It's recommended to also test the code before committing it. :)
3130

32-
### Rule 2
33-
3431
Always include detailed explanations on what the shader is doing and the math behind it. The Library of Shaders is here to help developers understand effects, not just copy and paste them.
3532

36-
37-
### Rule 3
38-
3933
You agree that your code and articles are licensed **Creative Commons Zero**, and require no credit for developers to use them.
4034

41-
### Rule 4
42-
4335
Write the code to be proper **GLSL** or **OpenGL Shading Language**, in terms of syntax.
4436

4537

0 commit comments

Comments
 (0)