[WiP] Handbook improvements for EOS and support

Question

[WiP] Handbook improvements for EOS and support

Closed this issue 6 years ago · 1 comments

cas-- commented 6 years ago

A new groove page in apps-we-use with everything specific to using it. General stuff remains on EOS or support page.
- For Groove info@niteo.co profile:
  - upload a 50x50px logo
  - first name only? (some security) (if same name use initial of last name?). Perhaps done already but should be detailed.
  - title empty?
- more details on tagging with labels (use search feature) and signing off messages with canned replies
The support.md need rearranging so important items are higher in list. Use bullet list not numbers.
The general dealing with user text should be on the handbook support page. Leaving just the app-specific paragraphs

Not part of handbook but including here as a reminder:

In support repo https://github.com/niteoweb/support/blob/master/README.md should link to https://niteo.co/projects and use the EBN and WooCart descriptions
I don't think the word checklist is being used correctly in support docs. I shall consider alternatives, something like FAQ or common problems.

Answer 1 · 2018-05-18T07:53:32.000Z

Some more notes for documentation changes:

EBN Plugins

For EBN, a list of our plugins would be useful. A page with details of blocked etc.

Published WordPress

https://profiles.wordpress.org/niteoweb#content-plugins

Rebuild Pages

This plugin has no reference in the docs.

https://help.easyblognetworks.com/blog-health/
Rebuild Pages
Do not share but repo is here: https://github.com/niteoweb/rebuild-pages

For error message only check blog status and use canned reply blog up.

Clone pages

This was mentioned but not searched for it yet.

Setup SSL

Better wording for comparing the IP (i.e. check whois) and redeploying should
a single point but continues in the next one.

Blog support request

Tje automatic requests should be clearer for support staff.
The blog is not hyperlinked so takes more time to verify.
Responding to each one is time-consuming if they the majority are fine when
checking them. (Even within a few minutes of receiving the message)
Can this not be automated?

NXDOMAIN

Better wording required on how to inform the use that their domain is on hold/suspended https://www.digitalocean.com/community/questions/how-to-fix-status-nxdomain

Support agent should copy the Domain status from whois