Skip to content
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

Enhancing Blueprint Accessibility (First Iteration) #3729

Closed
2 tasks
Tracked by #3728
MarianRaphael opened this issue Apr 16, 2024 · 5 comments · Fixed by #3752
Closed
2 tasks
Tracked by #3728

Enhancing Blueprint Accessibility (First Iteration) #3729

MarianRaphael opened this issue Apr 16, 2024 · 5 comments · Fixed by #3752
Assignees
Labels
area:frontend For any issues that require work in the frontend/UI headline Something to highlight in the release size:M - 3 Sizing estimation point task A piece of work that isn't necessarily tied to a specific Epic or Story.
Milestone

Comments

@MarianRaphael
Copy link
Contributor

MarianRaphael commented Apr 16, 2024

Epic

#3728

Description

As a: New FlowFuse User

I want to: Easily locate where the Blueprints are within FlowFuse

So that: I can quickly create new Node RED instances using Blueprint templates.

Which customers would this be availble to

Other (See comments)

  • Teams and Enterprise for Self Hosted version (ee)
  • All FF Cloud Users

Acceptance Criteria

  • Clicking on a specific Blueprint within the Blueprint Library should redirect the user to the instance creation page.
    The selected Blueprint should be pre-loaded or pre-selected in the instance creation workflow, streamlining the process of using a Blueprint for a new instance.
  • Design: Design: Enhanced Blueprint Accessibility in Library Tab #3598 (comment)

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

@MarianRaphael MarianRaphael added story A user-oriented description of a feature size:M - 3 Sizing estimation point labels Apr 16, 2024
@MarianRaphael MarianRaphael changed the title Implment better onboarding for Blueprint Accessibility (First Iteration) Enhancing Blueprint Accessibility (First Iteration) Apr 16, 2024
@joepavitt joepavitt added the area:frontend For any issues that require work in the frontend/UI label Apr 16, 2024
@cstns
Copy link
Contributor

cstns commented Apr 19, 2024

This area would love some TLC
image

@cstns
Copy link
Contributor

cstns commented Apr 19, 2024

Would also rename the "Library" menu item and "Team Library" page title to "Shared Library" (open for discussion).

The library nomenclature doesn't quite fit now after splitting the page into multiple tabs.

Any thoughts @joepavitt @MarianRaphael ?

@joepavitt
Copy link
Contributor

joepavitt commented Apr 19, 2024

@knolleary the term "Team Library" is what's used in the Node-RED codebase, right? So we'll be smart in keeping with "Team Library" as the tab to show shared js and json files here? Assuming that's not easily changed?

Whatever the side navigation text is, should be consistent with the bold text on this page. The tabs can then be named respectively.

@knolleary
Copy link
Member

'Team Library' is what it is labelled in the import/export dialog within Node-RED, but that comes from the settings file generated by the launcher so could be modified: https://github.com/FlowFuse/nr-launcher/blob/279538dd6fb406028d7c7566856626a8a446ce3b/lib/runtimeSettings.js#L186

image

However, I think Team Library is the right label for within Node-RED.

I'd suggest we just update the top header of the page - call it Library to be consistent with the sidebar, with the Team Library and Blueprints as subtabs as per the screenshot. The description would need updating to match

image

@joepavitt
Copy link
Contributor

I'd suggest we just update the top header of the page - call it Library to be consistent with the sidebar, with the Team Library and Blueprints as subtabs as per the screenshot. The description would need updating to match

Agreed

@joepavitt joepavitt added task A piece of work that isn't necessarily tied to a specific Epic or Story. and removed story A user-oriented description of a feature labels May 3, 2024
@joepavitt joepavitt added this to the 2.4 milestone May 8, 2024
@joepavitt joepavitt added the headline Something to highlight in the release label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:frontend For any issues that require work in the frontend/UI headline Something to highlight in the release size:M - 3 Sizing estimation point task A piece of work that isn't necessarily tied to a specific Epic or Story.
Projects
Status: Closed / Done
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants