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

Explanatory text on SlothAI pages #61

Open
ljsinclair opened this issue Nov 13, 2023 · 0 comments
Open

Explanatory text on SlothAI pages #61

ljsinclair opened this issue Nov 13, 2023 · 0 comments

Comments

@ljsinclair
Copy link

ljsinclair commented Nov 13, 2023

Issue

Some potentially confusing explanatory content on SlothAI pages:

  • Settings > "Salutations " - Issue here is that it's a long, old word used where a simpler one would suffice. And while stylistically interesting, it won't work for people from non-english speaking backgrounds. Recommend changing to "Hello" or "Welcome"
  • Tasks > "There are no active tasks. Start ingestion to see tasks here." > There is no "start ingestion" button in the UI. Recommend saying "There are no active tasks. Start a pipeline to see a task."
  • Templates > The "Edit" column at the end only has DELETE on first open. However, the name "Edit" has an actual meaning, so it's not the best column title. Call this something else (e.g., Actions, Template actions, etc)
  • Templates > Non-obvious clickable elements in the grid. You can fix by stating above the grid "Click an element to see more information", or make it a mouse-over.
  • Templates > Click name of template to edit > inconsistent UX because this isn't the case in the nodes page. Recommend disabling edit on name and enabling edit button in final column (Actions/Template actions, etc as suggested above)
  • Templates > Edit template -- error message on save "Extras cannot be saved while in use by a node" > This should be made clearer up-front, either on the page, or preferably when trying to edit a template with a node. e.g., Disable edit, pop message to say "delete from node to edit".
  • Edit template > the template name is non-obvious as the field has no title
  • Create Pipeline > Error message has typos "The request body must be valid JSON data and contain a 'name' and 'nodess' key
  • Create Pipeline > no indication WHERE to alter the request body. Perhaps it's talking about the template? In which case, this should be stated clearly so the user knows where to make the fix
  • Create Pipeline > Error msg - None of the sample templates contain a "nodes" key, so no way to determine what this is and its syntax. I'd call this a showstopper because without it, it seems the pipeline cannot be created.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant