How (not) to Write a Rulebook
How (not) to Write a Rulebook
![the background blur](https://lemmy.world/pictrs/image/74b16c4e-d319-4d44-9d48-5407b02d4ea6.jpeg?thumbnail=256&format=webp)
![](https://lemmy.world/pictrs/image/74b16c4e-d319-4d44-9d48-5407b02d4ea6.jpeg?thumbnail=1024&format=webp)
Today's blogpost is all about my flailing to refine and streamline my design docs into a coherent rulebook. I read enough of the d**** things you'd think I would know how to compile and order one. I understand the basics and where I went wrong, and have roadmap, but compared to design development is long and grindy.
Would really love if other folks have input on what makes a rulebook good? what have people done to make their projects easy to get? Which books are your favorite examples? What are your biggest hurdles?
For me I intellectually understand what needs to be there, but actually getting the writing clean and succinct to read is a challenge. I see a lot of DiY books for of background art and such trying to emulate a AAA book but they don't have the text and order of content hammered out 1st, I didn't want to move to layouts until my text was set, but maybe that's a mistake? Curious to see what people think.