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

Add next/prev buttons to new Channel page. Save button now called 'Finish' #382

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

chrisbenincasa
Copy link
Owner

…nish'

Cleaned up the way this works a bit -- using the custom context and moving the action buttons to the top level page instead of having to duplicate them.

image

Copy link
Collaborator

@markdavella markdavella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love that you made this form feel more connected between the tabs, just added a couple thoughts and ideas.

Should we add an alert above these sections for new Channels that just says something like, "These settings can all be edited later"? When I create something new in a new platform I am always afraid I won't be able to go back and change some selection I make.

@@ -156,7 +155,7 @@ export default function ChannelPropertiesEditor({ isNew }: Props) {
)}
/>
</Box>
<ChannelEditActions />
{/* <ChannelEditActions /> */}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you meant to delete this

)
}
>
Finish
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been tormented by the UX in this section, so hard to make it feel all connected and part of the same flow. I'm wondering if "finish" should be "Save & Exit" or something like that.

</Button>
) : null;
const nextButton = !isUndefined(channelEditorState.currentTab.next) ? (
<Button onClick={() => onNav(channelEditorState.currentTab.next!)}>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we add startIcon arrows for the next/previous buttons to make it feel more connected?

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

Successfully merging this pull request may close these issues.

Update UX for New Channel flow
2 participants