Jstg has a page on his gopher design philosophy [0]. I agree with
most of his points, in fact this gopherhole was designed in a
similar fashion - simple (or no) gophermaps, limited use of the 'i'
item type, and using descriptive selector names.  As I understand
the Veronica gopher search [1], having descriptive selectors is
particularly important, since there is no full-text document search.

I like his suggestions on a README if more description is needed,
and having links present so users can jump to the root or parent
menu easily. Floodgap's web-to-gopher proxy has this root menu link
feature and I find it very useful.

I care less about keeping menus to "one page" - the reality is that
on today's devices, one page is wildly variable. I do try to limit
line length to 68 characters, but this is more to allow comfortable
reading on most screens. I've noticed some gopherholes that don't
wrap text at all, and some that use an absurdly narrow page width. I
find both annoying. The reality with gopher is that most clients
don't wrap text for you, so it is best to keep the width at some
reasonable number. 67 or 68 seems pretty decent in my tests on both
mobile devices and various clients. I'm less concerned about ancient
clients or terminals, but a width of 67 or 68 supports them
anyway. I'd be more concerned about using type 1 text resources,
which not all clients handle properly.

[0]: gopher://sdf.org/0/users/jstg/design-philosophy.txt
[1]: gopher://gopher.floodgap.com/7/v2/vs