libraryh3lp logo

LibraryH3lp is software used by libraries, educators, and non-profits for better customer service.

Wednesday, May 15, 2013

FAQs on FAQs: Fabulous Footers

Welcome back to FAQs on FAQs, a series designed to help you get the most out of your LibraryH3lp-powered FAQ. Last time, we showed how to reuse existing headers from your library's website within your FAQ. So it is only fair that we cover custom footers in this installment!

As with customizing headers, setting up a custom footer requires a little bit of template editing.

1) Add content. Place the desired content within the footer.html template. Or if you wish the footer to span the entire width of your page, comment out the footer block within the base.html template using HTML comments (as you did with your header in Step 1 of the previous installment) and place the desired content after the main "container" div.

2) Adjust styling. As with custom headers, your strategy for including the styling for your header elements will vary since there are several ways to handle CSS. Please refer to Step 2 of the previous installment for styling tips and tricks or e-mail support if you need any help sorting things out.

Advanced customization: Sticky Footers. If you want to be extra fancy, you can opt to make your footer sticky. A sticky footer always remains at the bottom of a page and can be attractive on your individual question pages where content may be short and your footer appears higher on the page. If you'd like a sticky footer for your FAQ, check out the "how to" in our online docs.

Want to get your own LibraryH3lp-powered FAQ site up and running? Need to import content from an existing knowledge base into your FAQ? E-mail us!

Missed a previous installment of FAQs on FAQs? Here are some quick links to help you catch up: real-time chat and e-mail contact optionsmobile-specific view for patrons browsing on smartphonesadding content to your knowledge basecustomizing answer previewsstyle your FAQ with themes, bring your own theme part 1 and part 2, reusing existing headers.

No comments: