Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃殌 [Feature] Native FAQ/help pages #2723

Open
10 tasks
sushidave opened this issue Jan 10, 2020 · 3 comments
Open
10 tasks

馃殌 [Feature] Native FAQ/help pages #2723

sushidave opened this issue Jan 10, 2020 · 3 comments
Labels
Projects

Comments

@sushidave
Copy link

sushidave commented Jan 10, 2020

馃殌 Feature

FAQ/help pages as part of the application with crowd-sourced translations using Lokalise.

User Problem

With the current solution all FAQs are hosted on a separate WordPress multisite installation (currently in English and German only). However, this solution is not scalable as more languages would require more coordination amongst authors.

Implementation

  • Define URL structure for help pages
  • Create an HTML template for each help/FAQ page and populate with content (text strings, localised images, etc.)
  • Create a page index
  • Create a search field and function
  • Create a search results page
  • Connect with Lokalise
  • Redirect old URLs to new URLs
  • Testing
  • Replace link address in the footer
  • On the presentation website, create some FAQs pages with non-application related content

Design & Layout

Similar to the current Code of Conduct page but with a search field on top.

Help pages should be displayed in a new tab/window or in a lightbox, see #2514 .

Validation

Additional context

Questions:

  • Should we rename the "FAQ" pages to "help" pages?
  • The current FAQ pages are categorised. How simple is this to implement with the new solution?
  • Some FAQs have anchor links. How can they be managed with the new solution?
@sushidave sushidave added this to New in Roadmap via automation Jan 10, 2020
@DennisHack DennisHack moved this from New to Nice To Have In The Future in Roadmap Jan 13, 2020
@datenbrei
Copy link
Contributor

This would mean to ad some kind of CMS functionality to the code base. I would like this, but in the future (already put in the Roadmap like that)

@stale
Copy link

stale bot commented Mar 14, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 14, 2020
@sushidave sushidave removed the stale label Mar 14, 2020
@stale stale bot added the stale label May 13, 2020
@Human-Connection Human-Connection deleted a comment from stale bot May 13, 2020
@stale stale bot removed the stale label May 13, 2020
@Mogge
Copy link
Member

Mogge commented May 13, 2020

Not stale.
see #3543

@stale stale bot added the stale label Jul 12, 2020
@Human-Connection Human-Connection deleted a comment from stale bot Jul 13, 2020
@stale stale bot removed the stale label Jul 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Roadmap
  
Nice To Have In The Future
Development

No branches or pull requests

3 participants