I like highlighting the archivesunleashed@gmail.com email on both the FAQ page (it's already on the "about" page), and maybe also in the footer or at the bottom of the collection analysis page. Even if it's just an e-mail icon or something unobtrusive like that.

As you note (and as @ruebot noted too), it does suggest that having some sort of contact@archivesunleashed.org etc. e-mail address would be nice.

In addition to the FAQ, we could also set this up, and send folks to the #auk channel or an #auk-support channel. Example of what it looks like.

That looks great, and I like the idea of sending folks directly to either #auk or #auk-support. Latter has the benefit of being dedicated, although in the former more technical users could see ongoing GitHub + technical conversations (which could, in turn, alienate less technical users).

Cool. I'll dig into it today time permitting. Thursday, if I don't (on campus tomorrow).

For sure! I think that would be very helpful

I don't know if this would be helpful, or if it would be possible to implement, but just throwing out the idea of having a systems status page to show if there are any disruptions.

I use to use on in the past and was helpful to diagnose data ingest problems. Example from past project.

Again, this may not be applicable to our project, but just thought I'd see if @ruebot @ianmilligan1 had any thoughts on this.

Oh, like a status page: https://status.github.com or https://status.slack.com/? I could dig into that.

Yes, those are much better examples :)

http://slack.archivesunleashed.org/

Just catching up on notifications - a status page would be nice, esp. as we rely on WASAPI for so much.

To resolve this, should we add a note here to invite them to join the #auk-support channel on our Slack? I think we've take care of the other core issues in this ticket: .org email, and implementing the faq.

Implementing a status site is going to require a lot more work after I dug into it before the holidays. We should create a separate ticket for that, and identify what exactly we want to report on, and how we will verify that it is up; green.

Yep, and I think perhaps adding like to "About," "Documentation" as well as FAQ would help cover our bases. The goal is that people see the link before resorting to e-mails or giving up.

If you want I can take the lead on incorporating the links and then stage a PR for yours and @SamFritz review?

Sounds good! Thanks for staging the PR @ianmilligan1.

I agree that we've addressed issues listed in this ticket.

And agree with @ruebot re: status page. Happy to discuss the status page further (and move out of this ticket).