Perhaps this presents an opportunity for maintainers of Quicklisp (perhaps in collaboration with Quickdocs) to introduce a style guide for making their lives easier.
I edited the Google Common Lisp Style Guide (well, at least the version that was published a few years back; I know it has evolved internally since, but no updates were published.) I also published an ASDF "best practices" document.
There are many acceptable yet mutually incompatible ways of using Common Lisp packages. You must pick one and stick to it within any given system. Maybe you can describe them (or at least, one) in a blog post and/or some other document that you write.
Then again, there are also proposed alternatives to packages. Or you may embrace modernity and embrace Racket modules, or their reimplementation by Gerbil Scheme.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org It is paradoxical, yet true, to say, that the more we know, the more ignorant we become in the absolute sense, for it is only through enlightenment that we become conscious of our limitations. Precisely one of the most gratifying results of intellectual evolution is the continuous opening up of new and greater prospects. — Nikola Tesla