Skip to content
This repository has been archived by the owner on Jun 6, 2021. It is now read-only.
svbeon edited this page Feb 21, 2016 · 2 revisions

Things I think people generally agree on

  • Everything should be fairly simple
  • Prefer more pages with less content on each. faq/kb pages reachable by multiple routes.
  • Use the svg logos over there.
  • "I want to do X" paths to various faq/kb-style entries or (shorter where possible) lists of relevant ones
  • No giant list of FAQ entries
  • Things on the front page:
    • I am / I want to ... paths
    • News
  • Secondary pages:
    • About freenode (philosophy and (include privacy policy)policy and sponsors?)
    • Technical and Social FAQ
    • List of projects (from GMS)
    • Contribute

christel on organisation

<christel> basically i guess i want something like (but the names may change):
<christel> Front/main page - replaces current blog, serves news.
<christel> About freenode - > Philosophy/vision/mission/policy
<christel> Using freenode - > Link to Webchat/FAQ (technical vs. social, i.e. guidelines)
<christel> Projects       - > Link to GMS (to register)/Current projects (automatically updated from GMS as project is approved IF GC has opted to be listed and included an about blurb)
<christel> Contribute     - > Hosting a server / Acknowledgements

edk's FAQ layout half-idea

Several FAQ entries each with a category (for example "What is freenode?" might be in an "orientation" category). Categories are hidden from the usual interface.

FAQ indexes which pull from arbitrary sets of categories—for example there might be indexes for "wtf is freenode", "i have a project", "i'm in a group" and then possibly more topic-oriented things like social guidelines or channel management.

Clone this wiki locally