Skip to content

Conversation

@smeragoel
Copy link
Member

@smeragoel smeragoel commented Apr 28, 2025

Updating personas based on output of design clinic Jan - Mar 2025

Reference Issues or PRs

What does this implement/fix?

Put a x in the boxes that apply

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds a feature)
  • Breaking change (fix or feature that would cause existing features not to work as expected)
  • Documentation Update
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Build related changes
  • Other (please describe):

Testing

  • Did you test the pull request locally?
  • Did you add new tests?

Documentation

Access-centered content checklist

Text styling

  • The content is written with plain language (where relevant).
  • If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
  • All links describe where they link to (for example, check the Nebari website).
  • This content adheres to the Nebari style guides.

Non-text content

  • All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
  • If there are emojis, there are not more than three in a row.
  • Don't use flashing GIFs or videos.
  • If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

Updating personas based on output of design clinic Jan - Mar 2025
@netlify
Copy link

netlify bot commented Apr 28, 2025

Deploy Preview for nebari-docs ready!

Name Link
🔨 Latest commit 50fcee7
🔍 Latest deploy log https://app.netlify.com/sites/nebari-docs/deploys/681a011cf69ffb0008e0bba7
😎 Deploy Preview https://deploy-preview-572--nebari-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Member Author

@smeragoel smeragoel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cleaning up markdown, and introduction text.

Cleaning up text and markdown spacing
@smeragoel smeragoel moved this from Todo 📬 to In Progress 🏗 in 📖 - Documentation Apr 29, 2025
Adding dividers between the personas and removing extra emojis
@smeragoel
Copy link
Member Author

This is ready for review!

One change I’d like to flag (which I don't know how to do) is moving the Personas page from the References section to a new Design section. I assume that's best handled in a separate so I am happy with this being reviewed in the current page structure then I can open another issue for moving it to a dedicated design page.

@smeragoel smeragoel marked this pull request as ready for review April 29, 2025 14:34
@pavithraes pavithraes self-requested a review April 29, 2025 14:52
@viniciusdc
Copy link
Contributor

viniciusdc commented Apr 29, 2025

The linter needs to be run locally to address the fixes, for some reason the --attempt-fixes is not working on CI. @smeragoel can you try runnning yarn run format

@pavithraes
Copy link
Member

pavithraes commented Apr 29, 2025

@viniciusdc: I'll push up a commit to fix the linting issues. :)

@smeragoel: +1 to moving the page in a separate PR.

Signed-off-by: Pavithra Eswaramoorthy <[email protected]>
Signed-off-by: Pavithra Eswaramoorthy <[email protected]>
@pavithraes pavithraes merged commit 51d2bd6 into nebari-dev:main May 6, 2025
6 checks passed
@github-project-automation github-project-automation bot moved this from In Progress 🏗 to Done 💪🏾 in 📖 - Documentation May 6, 2025
@pavithraes
Copy link
Member

Thanks for this PR, @smeragoel! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done 💪🏾

Development

Successfully merging this pull request may close these issues.

3 participants