Simple Project Planning UI in the platform
N
Night sky Reptile
One of the most difficult things in Rewst is picking back up on a complex set of workflows after a weekend. It would be awesome from a planning perspective to have a simple UI that, let's call it projects,
where you can add a list of workflows (with links), workflows you intend to refrerence, templates you intend to reference, and a quick notes section for where you left off.
I get that there's some overlap with just making the workflows, but this would serve the purpose of an outline, and make it easier for teams to build different parts of a workflow. The idea wouldn't be to create the same links and transitions that workflows have, but to quickly and automatically provide links to the workflows you intend to use, their most recent results, and a freeform notes, possibly with estimated time to complete.
Log In
C
Continued Lungfish
We use named noops in an actual workflow to draw out concepts, then gradually replace the noops with real actions. The best part is that the flow will still work as long as you build out portions of it completely (otherwise, disable or don't add a trigger). Pair this with a Loop/Notion workspace, and off to the races.
I definitely like this idea, but it might just be a bit less of a priority for them due to the accessibility of tools like what I described above.
N
Night sky Reptile
Continued Lungfish: Definitely, that's how we're doing it as well. My main two issues with this are that it's really tempting to do too much at once, and it's a bit cumbersome to add and look up details like what templates, env vars, completion handlers, and subworkflows you plan on using. Also, there's something of a temporal nature to a lot of these noops, and I've found they tend to get deleted prematurely.
It might have been better to say that I want something to organize our workflows and their relationships a bit better, and I'm leaning towards a simple projects/relationships UI to set that up.
I've seen the request for folders in the workflows page, and while I love that, I also don't think it solves the problem most people would expect it to. I've seen how quickly our internal documentation gets cluttered, stale, and later avoided, no matter what kind of organizational system we attempt :)