# Inline user guides **URL:** \ **Category:** Development\ **Created:** [February 27, 2021, 6:55pm UTC](https://farmos.discourse.group/t/inline-user-guides/680 "2021-02-27T18:55:28Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\ **Post date:** [February 27, 2021, 7:40pm UTC](https://farmos.discourse.group/t/inline-user-guides/680/3 "2021-02-27T19:40:02Z")
@paul mentioned another interesting idea in the [farmOS Redesign](https://farmos.discourse.group/t/farmos-org-redesign/505) topic: > Drupal 9 has a core concept of [Help Topics](https://www.drupal.org/docs/develop/documenting-your-project/help-topic-standards). It’s an experimental module right now - but will soon be stable! These are fairly targeted towards general Drupal administration, but I think it would be possible to create dedicated sections for farmOS topics and “hide” what isn’t needed for normal users. They should be theme-able as well. > > A nice feature is that they can be translated with the existing Drupal localization service. But perhaps a downside of this is the topics need to be written in twig files. Markdown would probably be best… but maybe a script could auto-generate the twig files from markdown?? The translation potential is very appealing! And perhaps the [Twig filter](https://twig.symfony.com/doc/2.x/filters/markdown_to_html.html) I linked to above could help? I’m curious to understand how the files need to be structured. It sounds like you put “help topics” in each module that is responsible for them. But our current user guide content might not fit that model exactly. So that would be something to think about… --- _[View the full topic](https://farmos.discourse.group/t/inline-user-guides/680)._