A footer is an area for more off-beat references. They are more offside insofar as our readers expect to get access to what they came for — directly after a page is loaded, directly on top of it. At the bottom — where they first have to scroll — they are looking for minor aspects. That’s the logic of subordination. For the sake of reader-friendliness, the footer is a good place for a secondary subordinated menu should:
- Select a few important pages from the main menu, or create a few new overview pages.
- Create a second menu under ‘Appearance/Menu’.
- Include these pages in it.
- Mark the menu as a footer menu.
The position of a footer menu determines its task. As a subordinate element, it will hardly offer important novelties. A reader already would have to scroll ‘tremendously’ to reach it at all.
So the task of a footer menu can only be to lead back to the core — in a simplified way. It is immanently optional. The reader doesn’t need it. But once she’s down here, we can make it easy for her to find her way back. Simplified readability minimizes churn.
The bootScore home page demonstrates just that by using the Footer-Menu bootScore offers: Its main menu divides the content into 5 groups. For each group, there is exactly one entry in the footer menu. And these entries lead to the corresponding overview page.
Slim, simple, and functional.
And how does this …
… support our migration to bootScore? Well, if a web designer must abandon her current WordPress theme, she needs a replacement. A free ‘off-the-shelf’ theme, she probably wants to personalize. First a bit cosmetically, then in terms of the gray value of her pages, multilingualism and internal reference techniques and linking. Finally, she perhaps enables special footers, a secondary menu or a copyright notice before checking the SEO features of the selected theme. This is a way that this post supports too.