Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Showcase example instances of Apache Answers

Open
#333 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
content

Research direction

Start with issue #333, compare the requested showcase with Discourse's Customers page, and review the Apache Answers Meta instance mentioned in the issue. Done means providing prospective adopters with examples of Apache Answers in use, either through a showcase or the proposed blog/forum stopgap, with the examples covering customization and broader site needs.

Written by the indexing model from the issue text.

Description

duplicate

Problem

I'm choosing between Apache Answers and a competitor, and I'm struggling to imagine how well it might serve my organization's particular needs. The only example I know of is the Apache Answers Meta.

A solution I'd like

I want to see a showcase of examples of Apache Answer used well.

To show what I mean, Discourse has a Customers page where prospective adopters can see it in action.

Examples may

  • Show off rare features
  • Show how Apache Answers can be customized and styled
  • Highlight what to do or not to do (if marked appropriately)
  • Show how the core features of Apache Answers can sit sit-by-side with other needs clients might have, such as external navigation, announcements, community guidelines, links between categories and corresponding products, and other non-question-and-answer content.

Alternatives I've considered

A blog or forum post with links to instances that the maintainers of Apache Answers would be very helpful and a good stopgap.

Dominant language
TypeScript
Stars
47
Forks
70
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/answer-website

All issues in apache/answer-website

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.