{"CACHEDAT":"2026-04-14 05:13:10","SLUG":"outline-requirements-yYSN0egQD2","MARKDOWN":"Would you be open to Outline being a part of such a setup and be willing to provide the necessary input so that our programmer(s) can come up with code that can actually be used? I believe it could be a win-win situation since there are feature requests on Github for most of our needs anyway.\n\nWould it be feasible?\n\nCould you perhaps give me a first idea of how difficult it would be to develop the following features:\n\n* **Custom CSS**\n* * \n * \n * \n * \n\n\n* **hashtag anchor links to notices (or even paragraphs)**\n* * \n * \n\n\n* **something like a glossary / link system**\n* * where we can define terms, which are then automatically highlighted in all wiki pages and show the definition from the glossary in a pop-up with a link to the glossary entry\n * * model: \n * reduced version, but a start: \n * where we can define links to our lesson plan repository that are then also automatically added to the keywords / \"external glossary\" (maybe the link system could be created through APIs?)\n\n\n* **would be really great: mark sub-documents as hidden on public**\n* * \n * model: \n\n\n* **ideally: content snippets / reusable content**\n* * \n * \n * model: \n\n\n* API access to transcripts of coaching sessions (saved somewhere else), we could even offer an AI coach for teachers\n\n\n* header / footer (Erasmus+ logo) when printed\n * ","HTML":"

Would you be open to Outline being a part of such a setup and be willing to provide the necessary input so that our programmer(s) can come up with code that can actually be used? I believe it could be a win-win situation since there are feature requests on Github for most of our needs anyway.

\n

Would it be feasible?

\n

Could you perhaps give me a first idea of how difficult it would be to develop the following features:

\n
    \n
  • Custom CSS
    • \n
  • * <https://github.com/outline/outline/discussions/4206>
    • \n
  • <https://github.com/outline/outline/discussions/2362>
    • \n
  • <https://github.com/outline/outline/discussions/8537>
    • \n
  • <https://github.com/outline/outline/discussions/4307>
    • \n
\n
    \n
  • hashtag anchor links to notices (or even paragraphs)
    • \n
  • * <https://github.com/outline/outline/discussions/9825>
    • \n
  • <https://github.com/outline/outline/discussions/3562>
    • \n
\n
    \n
  • something like a glossary / link system
    • \n
  • * where we can define terms, which are then automatically highlighted in all wiki pages and show the definition from the glossary in a pop-up with a link to the glossary entry
    • \n
  • * model: <https://docs.document360.com/docs/glossary>
    • \n
  • reduced version, but a start: <https://www.archbee.com/docs/reusable-variables>
    • \n
  • where we can define links to our lesson plan repository that are then also automatically added to the keywords / "external glossary" (maybe the link system could be created through APIs?)
    • \n
\n
    \n
  • would be really great: mark sub-documents as hidden on public
    • \n
  • * <https://github.com/outline/outline/discussions/9889>
    • \n
  • model: <https://www.archbee.com/docs/mark-as-hidden-on-public-docs>
    • \n
\n
    \n
  • ideally: content snippets / reusable content
    • \n
  • * <https://github.com/outline/outline/discussions/7164>
    • \n
  • <https://github.com/outline/outline/discussions/2030>
    • \n
  • model: <https://www.archbee.com/docs/content-snippets>
    • \n
\n
    \n
  • API access to transcripts of coaching sessions (saved somewhere else), we could even offer an AI coach for teachers
    • \n
\n
    \n
  • header / footer (Erasmus+ logo) when printed
    • \n
  • <https://github.com/outline/outline/discussions/5327>
    • \n
","UPDATEDAT":"2025-08-17T14:32:28.024Z","ID":"6e5dc1e9-df90-4b8e-8a85-91a9462665f8","TITLE":"Outline Requirements"}