New Project Info Page Pops Up after Create New Project & Add Existing...

[thisguy-1]

User should also have a the ability to disable if s/he chooses. @tetchel @thisguy-1

[deboer-tim]

Are you talking about the project's readme here? Is the usability of seeing and closing it that bad since project creation is not that frequent?

I ask because template creators often want to show a quick summary of what's in the project the user just created to help them get started, and I've heard from another group that wants to expand on this.

[tetchel]

he is referring to the Project Overview page. The README makes sense too, iff the project has one. But they serve different purposes; the Overview page also introduces the user to a number of Codewind concepts.

[deboer-tim]

Ah. Maybe we should have a discussion or there is more detail elsewhere, but which Codewind concepts do we want to introduce them to, and couldn't we do that as part of the initial welcome? I'm a little anxious about showing two pages for different reasons and just want to make sure we have a plan for how this fit together in a clean flow.

[thisguy-1]

@deboer-tim
I'm not familiar with the difference between project readme and the project overview. I am referring to this:

Im guessing the readme is this:

There are several advantages to having the overview (the first image) pop up after they make their first project (and these are just some ideas):

• Increase learnability by having buttons to contextual functions that otherwise they'd have to discover via the palette or by right-clicking, something we have found in the study users do not automatically do (eg. Open App button)
• Better understand the statuses
• It could potentially link to information about stacks, where they could better learn about the different stacks.
• It could contain more information on the template itself.

The problem with the Readme would be that they would be tasked with finding it, assuming they would even go looking for it. They have to stumble on it. Considering the difficulty they already have with understanding the relationship between the codewind explorer and the codewind-workspace, I think for now our best bet is using the overview page.

[thisguy-1]

Based on our conversation, I will mock up a Project Overview page with collapsable information that doesn't have to be seen and a section for the readme.

[thisguy-1]

As an edit to the above, having a "readme section" is not possible, so the readme will popup next to the overview, and a link to the readme file will be in the overview.

[thisguy-1]

Work in progress, need feedback @jopit @elsony @tetchel @deboer-tim :

[thisguy-1]

Work in progress:

[tetchel]

The overview page is opened on create/add now, but i think we are still considering the new overview page for future

[thisguy-1]

Yes, for now we have kept the old version, but I have designed a new one which I hope will be implemented. If you like, we can close this one and open a new one that reflects the redesign of the overview page.

[thisguy-1]

in fact we have that already: https://github.com/eclipse/codewind/issues/161