https://docs.all-hands.dev/ logo
Join Slack
Powered by
Thoughts on adding an agent canvas section similar...
# proj-documentation
q
Thoughts on adding an agent canvas section similar to SDK, Cloud, etc? And remove legacy CLI Also everything here is documentation, ideas on a more descriptive name for the "documentation" tab?
c
An agent-canvas tab sounds great to me! Maybe "Main" for the main section? Provisionally at least
šŸ‘ 1
The CLI is still available and supposed to receive critical / major fixes, was my understanding. Did we change that?
šŸ¤” It's an interesting question though...
q
Hmm yeah CLI is still available cc @wooden-umbrella-84098 to weigh in
e
Documentation tab has some generically useful information that is available for all the interfaces, such as what's found under: ā€¢ Essential Guidelines ā€¢ Product Guides We also are looking to drive folks into Agent Canvas as the starting point, rather than provide a menu of options under "Quick Start".
q
Here is the change I'm proposing, rename documentation tab to "home" containing information essential for all interfaces And have a dedicated agent canvas tab that is cross referenced in the home pages
ā¤ļø 1
It also seems like our tabs are for specific interfaces, so maybe the use cases tab lives under the home tab? under the essential guidelines section perhaps
c
The other alternative is that due to the backend, maybe we could ā€œmeltā€ Cloud into Agent-Canvas, though I like this and think itā€™s clear enough this wayā€¦ šŸ¤” Wellā€¦ Where is, in this layout, Joeā€™s user journey, itā€™s under Agent-Canvas, right?
q
Yep under canvas
c
Well, our tabs are our specific interfaces because I found that to be a small step towards clarifying what the user gets when they use one or the other. But thatā€™s becoming outdated now, because the goal of canvas is to unify that experience itself
What exactly is remaining under Cloud, that isnā€™t in Agent-Canvas?
q
I think its mostly configuration details and orgs management in cloud section
c
Or isnā€™t Open Source? I thought that with the integrations, practically all that isnā€™t enterprisey is Open Source.
Right, org management is enterprisey
It's not part of the personal AI software engineer, aka individual user experience
Rohit, do you have a branch I could browse a little bit, please?
q
c
Re: this wording, I am not sure we should keep it, even if only for Cloud. šŸ¤”
nod 1
So the goal of agent-canvas is to offer a single, unified experience for the user. Joeā€™s ā€œuser journeyā€ should be the start of what someone coming to OpenHands and trying to see whatā€™s that like, would see / understand / reflexively perceive as the normal OpenHands experience ā€¦
nod 1
Which I think means weā€™re trying to get rid of the multiple interfaces concept, or at least de-emphasize that aspect a lot
Same for this, similar issue, ā€œa few ways toā€ - followed by several options
nod 1
Please tell me if Iā€™m not making sense. Iā€™m trying to say that maybe instead of this wording, and even instead of the pages itā€™s on, we could: ā€¢ Home ā—¦ has the few user journey pages ā—¦ has the other two categories, Product Guides and something ā€¢ Agent Canvas ā—¦ detailed sections ā€¢ CLI ā—¦ tab staysā€¦ but maybe not linked from the start pages; itā€™s a tab, itā€™s visible ā—¦ or tab doesnā€™t stay, but then I donā€™t know where the info goes ā€¢ Cloud and Enterprise ā—¦ admittedly my preference would be to move under an 
enterprise.
subdomain ā—¦ even if they stay as tabs, the primary Cloud experience is supposed to become via agent-canvas I think ā—¦ which means not via Quick Start
q
This makes sense to me! Stepping away for a bit, ill open branch off the current working one incorporating this
ā¤ļø 1
c
Also, to note, we will delete Local GUI and its doc. Since agent-canvas gives the same anyway, and since the codebase becomes cloud backend. Probably not until we move the codebase out of OH/OH.
nod 1
e
Team I don't want to delete the Local GUI docs. We still have many users of Local GUI. We should create a more responsible timeline and communication around how we support Local GUI users. I am trying to work with @wooden-umbrella-84098 on what that looks like. For now we keep Local GUI docs.
nod 1
šŸ‘ 1
Rohit I haven't caught up on all of your changes. The goal was originally to create some backend / how to self host docs so we can get this out tomorrow. And then iterate / refine. Hope we are still in good shape there šŸ˜Š
q
Yep I'll have it ready by tmrw To make it less confusing for users that land on the docs, I'm seeing where else we can make immediate improvements such that agent canvas is front and center, and that all of the canvas capabilities are easy to parse quickly
šŸ™ 1
e
Thanks - appreciate the help. I may have feedback later but overall as long as we are getting the canvas docs out for tomorrow that's great šŸ’Ŗ
šŸ™ 1
c
Sorry Joe, I didnā€™t mean it quite like letā€™s delete it now šŸ™
np 1
ā¤ļø 1
Have we considered the question of migration?
e
I def like the idea of a migrationā€¦ we should brainstorm this!
c
šŸ¤” actually I think it might beā€¦ almost no difference. Iā€™ll kick start a little investigation
w
Agreed on keeping CLI and Local GUI docs, but pushing them down a bit so they're harder to find unless you're looking for them
nod 1
3 Views
Open in Slack
PreviousNext
Powered by