# Maintaining a "Best Practices", "Working Examples", or "FAQs" section of the site

**URL:** https://discourse.roots.io/t/maintaining-a-best-practices-working-examples-or-faqs-section-of-the-site/8549
**Category:** general
**Created:** 2017-01-13T19:25:04Z
**Posts:** 4

## Post 1 by @MWDelaney — 2017-01-13T19:25:04Z

Spinning off from [this comment](https://github.com/roots/sage/pull/1809#issuecomment-272520931), does it make sense to maintain a page in the Sage documentation dedicated to best practice examples for things like adding FontAwesome (and other packages)?

I’m often working from examples laid out by the Roots team, like `_grid.scss` and the Font Awesome example that was included in earlier versions of Sage 9. [This Blade example](https://discourse.roots.io/t/best-practice-resources-for-blade/8341/11) is another great example. We often see general questions on this forum about adding packages like FontAwesome “the Roots way”.

I don’t know where the line would be between “useful examples” and “re-documenting npm”, but there must be a good way to maintain answers to these FAQs, right?

---

## Post 2 by @anon56740962 — 2017-01-13T19:34:08Z

I’ve actually gotten to peek at the new Sage 9 book and it contains quite a bit more information/examples and addresses a lot of non-sage related topics that are seen on Discourse frequently. There is also a resources section akin to an FAQ linking to outside documentation as well as the most popular questions on this forum.

---

## Post 3 by @darjanpanic — 2017-01-13T23:52:18Z

Was thinking a similar thing today, some nice “snippets” or gists would be nice for some things :slight_smile: for example ACF flexible fields + Blade best practices would be one of them.

---

## Post 4 by @JulienMelissas — 2017-01-15T00:08:50Z

There’s always the #example tag! I wish people used it more here.