-
Notifications
You must be signed in to change notification settings - Fork 28
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add nebari user personas #460
Conversation
✅ Deploy Preview for nebari-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I got some help from Smera on this. She has suggested I use the css tag |
@pavithraes or @viniciusdc this is ready for review. |
Hi @kcpevey, can you refresh me on why we need this again? Also, would it be possible to consolidate all personas into a single md file? It gets weird in the sidebar menu, with many names without any context... for a second, I thought I had some colleagues I had never talked to. XD |
User personas helps to understand user stories on nebari usecases. These were created by the team a couple years ago and saved in our private notion docs. I was merely publishing them, which is why they are split out into individual pages - I just copied the currently existing notion pages. That said, I can understand it does seem like a lot. I can collapse it down to one if you'd prefer? |
Gotcha, thanks @kcpevey
That would be great |
@viniciusdc I've collapsed all personas down to a single file. This is ready for review again :) |
Looking gorgeous, thanks @kcpevey |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!!
We have personas that we created a while back but they were never published externally. This is just a copy of those personas (previously in notion) out to the public docs. I did not change any wording.
Reference Issues or PRs
Resolves #455
What does this implement/fix?
Put a
x
in the boxes that applyTesting
Documentation
This IS documentation
Access-centered content checklist
Text styling
H1
or#
in markdown).Non-text content
Any other comments?