-
Notifications
You must be signed in to change notification settings - Fork 4
Release notes to sprint 60 #483
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
Conversation
A PR preview is available: Preview URL |
PR SummaryThis pull request introduces several enhancements and bug fixes to the ValidMind platform, focusing on improving user experience, functionality, and documentation. Key Enhancements
Bug Fixes
Documentation Updates
Test Suggestions
|
PR SummaryThis pull request introduces several enhancements and bug fixes to the ValidMind platform, focusing on improving user experience, functionality, and documentation. Key Enhancements
Bug Fixes
Documentation Updates
Test Suggestions
|
A PR preview is available: Preview URL |
A PR preview is available: Preview URL |
A PR preview is available: Preview URL |
A PR preview is available: Preview URL |
@validbeck, great feedback, thank you. Will address where you haven't already. Some comments:
I don't think this should be true globally. We should open links in new tabs ONLY if the links are external and this is already configured in _quarto.yml via (For reference, at my previous gig we had a rule that internal docs links could never spawn another tab, as we had >300k pages and it was just messy otherwise. You can always open links in a new tab if this is your preference.)
I'm on the fence about these but with a preference not to add too many links — release notes should tell you how to get started with something after you read them and that should be the notebooks, not some reference page. Again, less is more. |
Forgot to mention, I like the new rounded corners!
This is how the buttons were when I grabbed them to do the first round of links — I will adjust in my PR now that I know this wasn't intentional.
I understand what you're arguing, but in this case I vote for them. As a developer, I would expect to see the reference for the function or test you're talking about. |
I think that was likely a side effect of which button you grabbed to create others which just goes to show that there is an issue with the old HTML button approach. Thank you for fixing!
Will add for now but we should discuss the meaning of the tip of the iceberg that is release notes ... Reference content on its own likely is not enough to do something, so why not just link to something you can actually use out of the box? General thoughts on links in release notes, for further discussion:
All of which goes to say: use links sparingly, including in release notes. |
A PR preview is available: Preview URL |
@validbeck I rounded the corners a bit more via df602de which also happens to solve the issue we've been having with corner artefacts from screenshots on macOS.
|
A PR preview is available: Preview URL |
A PR preview is available: Preview URL |
Removed from the style guide, where you had added
I replaced all the docs links with the actual topic title and I think that is a generally good rule to follow, thank you. I do NOT agree with adding lead-in text for a button that describes what the button does ... That's just a simpler button replaced with text + button. As a general rule, we should be mindful about avoiding unnecessary verbiage — less is more! Also, we have some notebooks that have very long titles that themselves need to be edited and that would make for some pretty painful buttons: ![]() Here's how the buttons now look — doc links use the exact title and notebook links remain as before: ![]()
Agreed, removed.
They're the exact same size as in the docs ... If people want a bigger view, they can just watch the videos on YouTube.
I scanned the text and searched for paragraphs of >200 words. I find release notes often look fragmented anyway, so I made no changes here but if there are specific sections where you think this would help, go ahead.
Yup, that fixed it! Not sure why it was missing when I created the release notes initially but the file is there now.
I would normally agree but in this case there is a new "Ongoing Monitoring" option in the navigation on the left that you would not see if you cropped the screenshot. (FWIW, the docs for ongoing monitoring use only a very cropped version that has been reduced to the graph.)
Since the screenshot is not being cropped, I'm going to leave this as is. I think it's fine to have a full-width screenshot here as ongoing monitoring is basically our halo feature in these release notes.
Links added.
Agreed, looks better in two columns, with a bit of padding between them. Coincidentally, I noticed that you've been adding this in some places:
These spacer columns should not be necessary with Tachyons CSS, you can use
Link added.
Ugh, done. I sense another CSS class ... manually adding video styling is getting old fast!
As in there's not enough margin? I did add
I don't know what this comment means? It's not a screenshot, it's the live training page embedded in the release notes. I did look at the example, but it's just a small callout. I'd prefer to give more emphasis to our training page here.
Fixed. |
A PR preview is available: Preview URL |
A PR preview is available: Preview URL |
1 similar comment
A PR preview is available: Preview URL |
A PR preview is available: Preview URL |
A PR preview is available: Preview URL |
* Edits up until Releases * Edits for 2024-aug-13 releases * Adjusted figcaption to center text * Edits for 2024-jul-22 releases * Edits for 2024-jun-10 releases * Edits to overview guides * Releases tweaks up to June 10 2024 * Edits to march 27 2024 wip * Final tweaks to march 27 2024 * Edited feb 14 2024 * Edited jan 26 2024 * Edited jan 18 2024 * May 22 2024 releases WIP * Edited may 22 2024 * Added _how-to-upgrade.qmd single-source * Added _how-to-upgrade.qmd to newer releases missing it * Edited nov 09 2023 * Edited oct 25 2023 * WIP Sep 27 2023 * Edited Sep 27 2023 * Tweaks to variable in buttons & links * Edited aug 15 2023 * Edited jul 24 2023 * Edited jun 22 2023 * Edited may 30 2023 * Visual tweaks * More cleanup * Some more tweaks * Final? edits * Feedback from Nik * Maybe the python docs need to be updated on remote? * Nope, just a docs-demo preview issue * Release notes to sprint 60 (#483) * Generate initial release notes * Fix LUA error * WIP edits * Initial edit pass & add images * Add new button to styles.css * Clean up styles.css * WIP more edits * WIP more edits * WIP more edits * Update button style * WIP edits * Second edit pass complete * Add button info to style guide * Minor edits * Fix broken link * Run make get-source * Final tweaks * Remove release notes notebook * Improved hover state for buttons * Adjusted style guide & README * Tweak to the convention example * Oops, I can't spell * Remove _blank guidance * Round screenshot corners more * Add fig-alt text * Address review comments from Beck * Add upgrade info and crop screencap * Ambiguous antecedents are a bad habit * Visual tweaks * Summary & final touches --------- Co-authored-by: Beck <164545837+validbeck@users.noreply.github.com> --------- Co-authored-by: Beck <164545837+validbeck@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Internal Notes for Reviewers
This PR includes release notes up to Sprint 60: LIVE PREVIEW — October 22, 2024
Frontend
Developer framework
Documentation
Other improvements
New button class for Markdown links
I got tired of our hard-coded HTML buttons and added a new class for buttons to simplify the process. You can now add
{.button}
to any Markdown link to turn it into a button:<form method="get" action="../../guide/monitoring/ongoing-monitoring.html"><button type="submit" style="color: white; background-color: #de257e; border-radius: 8px; border: none; font-size: 16px; padding: 6.25px 12.5px; margin-left: 16px; margin-bottom: 20px;">Learn about monitoring</button></form>
[Learn about monitoring](../../guide/monitoring/ongoing-monitoring.qmd){.button}
Rounded edges for screenshots
Quite subtle, but our class="screenshot" was very rectilinear. I added the same rounding for corners as for the button:
External Release Notes