Simplified Workflow Centric UI (Attempt 3) #18445
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
791406f
to
839588f
Compare
839588f
to
8a6d8c9
Compare
|
I think this is a great step in the right direction for finding workflows. I'd like to propose a minimalist workflow landing page as a further simplification on the ramp from I suspect the work to implement something like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A large group of us outlined the idea in details years ago in http://bit.ly/simplified-workflow-ui. The idea was brought up and highlighted by @bwlang again during this year's GCC panel. The document walks through a bunch of choices and options and outlines why histories and uploads are not required. This PR is my latest landing attempt for a simplified workflow-centric interface to Galaxy. The page show the workflows available to the users and allow access to invocations. Since the original idea we've added a customizable activity bar, per-subdomain client side configuration options, and vastly improved the workflow invocation view so this idea should be stronger than ever and less disruptive to implement.
Previous attempts at #9030 and #9109 are probably not interesting but xref-ing. This attempt builds on top of @guerler's latest Masthead work in #17927.
The screenshot of the new landing is:
The two relevant config options are:
client_mode: 'workflow_runner'(orworkflow_centric)simplified_workflow_landing_initial_filter_text: 'tag:iwc'These options can both be set on a per subdomain basis so we could create
iwc.usegalaxy.orgwith all the published IWC workflows available and easily runnable. The filter text is configurable so other sites could filter by username in addition to tags for instance. This idea isn't just to highlight IWC workflows - we've seen projects with comparable ideas built on top of Galaxy like this (e.g. Galaksio, Refinery, etc..) for years and well before we had an IWC.A note on
workflow_runnervsworkflow_centricProjects like Galaksio were explicitly created to only allow specific workflows to be run. The is mode I'm aiming to implement with
workflow_runner. This mode disables a bunch of workflow management features (importing, seeing your workflows, editing workflows) that we should have a modality for but probably isn't what we want for a more typical Galaxy - where editing and sharing workflows are important activities we want to encourage. For this I've implemented a second client mode calledworkflow_centric.How to test the changes?
(Select all options that apply)
License