Hostea
/
website
3
2
Fork 2
Code Issues 5 Pull Requests Projects Releases Wiki Activity

updates to the clinic page #13

Merged
realaravinth merged 1 commits from dachary/website:wip-clinic into master 2022-05-04 18:03:15 +00:00
Conversation 1 Commits 1 Files Changed 3
dachary commented 2022-05-04 07:27:49 +00:00
Owner
  • Removed the contact banner that leads to /contact
  • Changed the link to each doctor to be the support tracker that
    contains their track record instead of a resume
  • Added testimony link to the first Hostea public consult
* Removed the contact banner that leads to /contact * Changed the link to each doctor to be the support tracker that contains their track record instead of a resume * Added testimony link to the first Hostea public consult
dachary added 1 commit 2022-05-04 07:27:49 +00:00
ci/woodpecker/pr/woodpecker Pipeline failed Details
3eda37b4fe
updates to the clinic page 
* Removed the contact banner that leads to /contact
* Changed the link to each doctor to be the support tracker that
contains their track record instead of a resume
* Added testimony link to the first Hostea public consult
dachary requested review from realaravinth 2022-05-04 07:28:01 +00:00
realaravinth requested changes 2022-05-04 12:25:08 +00:00
content/gitea-clinic/index.md
@ -19,3 +19,2 @@
Sounds good, I want to get an appointment!
{{ call_to_action_banner(prompt="Sounds good, I want to get an appointment!", link="/contanct", action="Contact Us") }}
## Sounds good, I want to get an appointment!
realaravinth commented 2022-05-04 12:16:53 +00:00
Owner

The action banner pointing to the contacts page is a temporary measure. Ideally, there should be a customer workflow that will guide them from this page to do the following things:

  1. Sign up
  2. Select a Doctor
  3. Sign a contract with Doctor of their choice
  4. Interact with the Doctor in a ticketing system to track the engagement
  5. If resolved, rate and exit

Thoughts?

The action banner pointing to the contacts page is a temporary measure. Ideally, there should be a customer workflow that will guide them from this page to do the following things: 1. Sign up 2. Select a Doctor 3. Sign a contract with Doctor of their choice 4. Interact with the Doctor in a ticketing system to track the engagement 5. If resolved, rate and exit Thoughts?
dachary commented 2022-05-04 17:39:52 +00:00
Poster
Owner

This is a sensible workflow when the service is confirmed to be something worth running. During the User Research phase it will be enough if I can explain to people that they just create an issue on the tracker.

Realistically, since I'll get in touch with them individually, that's a good option. I don't think anyone will arrive on this page without talking to someone involved in hostea first.

This is a sensible workflow when the service is confirmed to be something worth running. During the User Research phase it will be enough if I can explain to people that they just create an issue on the tracker. Realistically, since I'll get in touch with them individually, that's a good option. I don't think anyone will arrive on this page without talking to someone involved in hostea first.
realaravinth marked this conversation as resolved
content/gitea-clinic/index.md
@ -22,3 +21,2 @@
The doctor name links to their resume. Stars are awarded when someone is
happy about a public consultation (not for private consulations).
Each star is awarded when someone is happy about a public consultation. Doctors cannot get a star for a private consulation.
realaravinth commented 2022-05-04 12:19:05 +00:00
Owner

Ah, I see what you mean. Can this be a separate metric, like "successfully resolved"?

Ah, I see what [you mean](https://gitea.hostea.org/Hostea/website/issues/12#issuecomment-325). Can this be a separate metric, like "successfully resolved"?
dachary commented 2022-05-04 17:40:44 +00:00
Poster
Owner

Is is worth creating two metrics for the User Research phase?

Is is worth creating two metrics for the User Research phase?
realaravinth marked this conversation as resolved
data/clinic-doctors.toml
@ -4,3 +4,3 @@
nick = "dachary"
name ="Loïc Dachary"
website = "https://dachary.org"
website = "https://gitea.hostea.org/dachary/hostea/issues"
realaravinth commented 2022-05-04 12:22:57 +00:00
Owner

I wanted to do a profile page for every Doctor Hostea/dashboard, which can be made public via hostea.org instead of dash.hostea.org too. The Hostea SSO will also allow for seamless Gitea integration with the dashboard for interacting with the Doctor to track current engagement, as mentioned in a previous comment.

I wanted to do a profile page for every Doctor Hostea/dashboard, which can be made public via hostea.org instead of dash.hostea.org too. The Hostea SSO will also allow for seamless Gitea integration with the dashboard for interacting with the Doctor to track current engagement, as mentioned in a [previous comment](https://gitea.hostea.org/Hostea/website/pulls/13/files#issuecomment-327).
dachary commented 2022-05-04 17:42:20 +00:00
Poster
Owner

This would look a lot better, indeed. Pointing directly to the issues during the User Research phase requires no work and goes directly to when things happen.

This would look a lot better, indeed. Pointing directly to the issues during the User Research phase requires no work and goes directly to when things happen.
realaravinth marked this conversation as resolved
data/clinic-doctors.toml
@ -10,2 +9,3 @@
name = "Chris H."
rating = 5
remarks = "Nice"
remarks = "https://discourse.gitea.io/t/blank-page-after-login/5051/14"
realaravinth commented 2022-05-04 12:24:55 +00:00
Owner

I think we could have a source attribute for external reviews and verbatim quote relevant sections in remarks attribute. That way, the Doctor profile page can have a traditional reviews section with textual comments. Thoughts?

I think we could have a `source` attribute for external reviews and verbatim quote relevant sections in `remarks` attribute. That way, the Doctor profile page can have a traditional reviews section with textual comments. Thoughts?
dachary commented 2022-05-04 17:43:28 +00:00
Poster
Owner

I think we can just forget about this during the User Research phase. But again, it is a sensible way to go about it once the service launches.

I think we can just forget about this during the User Research phase. But again, it is a sensible way to go about it once the service launches.
realaravinth marked this conversation as resolved
realaravinth commented 2022-05-04 18:02:41 +00:00
Owner

I understand where you are coming form. I've made a note to continue this discussion if UX research indicates positive interest.

I understand where you are coming form. I've made a note to continue this discussion if UX research indicates positive interest.
realaravinth merged commit 9c9e68617f into master 2022-05-04 18:03:15 +00:00
dachary deleted branch wip-clinic 2022-05-04 18:40:45 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
realaravinth
Labels
Clear labels   
Blog
   
Bug
   
Enhancement
   
Feature
No Label
Blog
Bug
Enhancement
Feature
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Hostea/website#13
There is no content yet.
Delete Branch "dachary/website:wip-clinic"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?