I'm not sure which part of "patterns" or the book description suggests it's only about ideas, but in general, patterns can be about process or anything else. Where there are useful solutions to recurring problems, there are patterns worth mining and recording.

I might suggest the project just call these "startup patterns" as "design patterns" tends to make people think of technical coding or software architecture patterns. "startup patterns" is deliberately open-ended.