What other key Reference materials should be listed in an Appendix for the Wiki

[emyoulation]

What other materials should be in an indexed Appendix? It would list the preferred References for Gramps

User references:

• Gramps User Wiki Manual
• Visual Guide to the Gramps Interface
• Gramps Glossary
• Genealogy Glossary
• User Tutorials‏‎ Category
• Video Tutorials
• Bug Report & Feature Request system guide (MantisBT guide)

Developer References

• Developer Portal
• Developer Tutorials‏‎ category
• Brief introduction to Git (GitHub guide)
• Build from source
• Gramps Data Model
• API reference guide (Sphinx)
• Developers Reference‏‎ category
• Coding for translation using weblate - Gramps

Translators References

• Translating Gramps using Weblate guide

[codefarmer]

@emyoulation That’s a good list. Suggestions:

• In the User section, before the “bug report” how about “Where to go for help” which lists the forum, IRC and other ways to connect with other Gramps users. This may help steer users to the community before filing bug reports on functionality they might still be unfamiliar with.
• “Programmer References” suggest calling it “Developer References” ✓ to include artists, triagers, translators, writers and others who help develop Gramps.
• Developer Portal ✓ is one of my go-to pages. Consider making that the first link in the developer section.

[emyoulation]

@codefarmer

In the User section, before the “bug report” how about “Where to go for help” which lists the forum, IRC and other ways to connect with other Gramps users. This may help steer users to the community before filing bug reports on functionality they might still be unfamiliar with.

We have 2 “Contact” pages: the Contact page in Wordpress (that has fewer contributors with editing rights) and the Contact page in MediaWiki in 12 languages.

The wiki page is a bit more positive. (It assumes people are there to get help from the community, while the WordPress assumption is that they want to report Bugs.) Maybe this could be the “Where to go for help”?

Adding a contact.Gramps-Project.org subdomain (like the discourse.gramps-project.org and bugs.gramps-project.org redirecting subdomains) might be worthwhile. It isn’t case sensitive and tge server could have browser-language-aware redirection rules. We wouldn’t be as tied-down to a technolgy (MediaWiki, WordPress, MantisBT, Discourse) using such genercized subdomains links in Gramps as we are with such specific URLs. Which means the discourse subdomain might be more consistent as something like “community.Gramps-Project.org” … or maybe even play off the Genealogy aspect of our community and use family.Gramps-Project.org

Note that there are extensions to embed MediaWiki content in WordPress pages too. I don’t know if the extra complexity/fragility would be worth the effort. But it might be a way to keep the WordPress content fresher & multi- cultural. It IS the first content that potential new users will see.

How to Embed MediaWiki Pages into WordPress - GreenGeeks

[codefarmer]

@emyoulation

We have 2 “Contact” pages: the Contact page in Wordpress (that has fewer contributors with editing rights) and the Contact page in MediaWiki in 12 languages.

The wiki page is a bit more positive. (It assumes people are there to get help from the community, while the WordPress assumption is that they want to report Bugs.) Maybe this could be the “Where to go for help”?

The content is very similar and to make the choice simple, wiki is a good choice because of the reasons you laid out and several of the other links are pointing to the wiki anyway.

For both Contacts pages you mentioned, it would be really helpful to first direct Gramps users to any form of self-help, i.e. wiki, forums and mailing lists by moving those section up so users search the wiki/forum first. With limited number of triagers and developers, it would be better to have them spend their time on issues that are clearly bugs or feature enhancements.