Opened 3 years ago

Last modified 20 months ago

#22842 accepted task

Create a knowledge base that's more in-depth than FAQs

Reported by: catalyst Owned by: hiro
Priority: Medium Milestone: WebsiteV3
Component: Webpages/Website Version:
Severity: Normal Keywords: ux-team, FAQ
Cc: dmr, pili Actual Points:
Parent ID: #24133 Points:
Reviewer: Sponsor:


It would be useful for visitors to our web pages to have access to content that:

  • goes into more depth than a FAQ entry
  • is more formal than a blog post
  • is less comprehensive than a reference manual section
  • is more stable than a wiki page

These pages would form sort of a knowledge base or resource section.

Child Tickets

#27567closedWebsite FAQ: Implement Collapsible FAQ itemsWebpages/Website
#27582closedadd page for Tor controllersWebpages/Website

Change History (14)

comment:1 Changed 3 years ago by catalyst

In the interim, making a list (possibly using a designated blog tag?) of useful blog posts to which we often refer people would be helpful.

comment:2 Changed 3 years ago by cypherpunks

These pages would form sort of a knowledge base or resource section.

Wiki pages would be the best for such a thing so why did you exclude them? I happened to find a similar trac ticket with the suggestion of having a just like Mozilla's

Version 0, edited 3 years ago by cypherpunks (next)

comment:3 Changed 3 years ago by hiro

Owner: set to hiro
Status: newaccepted

I was actually discussing this already. It has been pointed out many times that the FAQ section is too long and it belongs to a proper knowledge base more like

We can either use a wiki or see if we can create a KI of our own. I am open to possibilities.

Last edited 3 years ago by hiro (previous) (diff)

comment:4 Changed 3 years ago by hiro

Keywords: ux-team added
Milestone: WebsiteV3

This issue was discussed separately and will be addressed in the new version of the website.

comment:5 Changed 3 years ago by linda

Parent ID: #21222
Type: projecttask

I added the redesign ticket as this one's parent ticket.

comment:6 Changed 3 years ago by linda

Parent ID: #21222#23266

comment:7 Changed 2 years ago by cypherpunks

Other example designs and content by and for large open-source communities:

comment:9 Changed 23 months ago by traumschule

I'd choose the wiki approach, similar to BashFAQ and protect FAQ/* pages to be editable only by selected curators (maybe per topic). This way we could easily reuse existing wikis and clean harmfully outdated stuff. Count me in if that becomes an official project.

comment:10 Changed 23 months ago by traumschule

Keywords: FAQ added

comment:11 Changed 23 months ago by dmr

Cc: dmr added

comment:12 Changed 21 months ago by traumschule

#28065 is related

comment:13 Changed 20 months ago by traumschule

Cc: pili added
Parent ID: #23266#24133

Making this a child of the new community page to be looked at more.

#21222 and #23266 however are still related.

From yesterdays community meeting:

there's all kind of stuff on the old website that should be cleaned up, updated, and put on the support portal for example a whole long explanation of Tor vs VPNs
we need someone to go in and take an inventory of what is on the website that is missing from the support portal
in general we are trying to move away from using the wiki for everything
the main idea is to have community.tpo as a hub for people who want to volunteer

Pili organizes a meeting on friday about the community portal to coordinate the timeline. I was not sure if it's ok to add your document link here?

comment:14 Changed 20 months ago by emmapeel

I think we have a lot of content in different platforms and formats, and we have problems to keep them all updated/indexed/searchable/localized.

I feel this content should go on our trac wiki while is being edited, and once it has reached certain stability, be moved to,, or

Note: See TracTickets for help on using tickets.