New Editor layout Improvements ☂️
See original GitHub issueDescribe the Issue
This is an umbrella issue to discuss the improvement to the editor layout: Here is the mockup for your reference. https://www.figma.com/file/BINkSLYG2VzT9GGEajhoiH/Untitled?node-id=0%3A1
General:
- Make the reset step contextual (show it along with the help button at the button of the lower jaw after a few attempts) #46272
- Add
Sign up to save progress
button above all elements in the lower jaw for un-auth #46401 - Add the modal progress bar to the button of the lower jaw. #46811
- Add a share button below the progress bar at the end of each project. (Custom twitter cards)
- Confetti at the end of each project.
- Add a quote to the lower jaw when tests pass. #46429
- Disable button and show loading bar on challenge submission
- Debounce the challenge submission from the epic not the component
Mobile:
- Remove editor side by side display #46276
- Remove double scroll in the editor tab
- Reduce the area to the left of the line count to save space. #46309
- Remove
Ctrl + Enter
on CTA #46239
Project:
- Minimize tests when they are not run.
Needs further discussion:
- Is having multiple stacking options feasible?
- Making tests challenge completion state more visible when editable region is not visible.
- For mobile, is the lower jaw redundant or the lower buttons row.
- What is the best way to nest tabs and simplify the navigation for Mobile.
Issues
- Toggling the editor tab clears the lower jaw state.
- The focus should be on the editable region of the editor when starting a challenge.
Issue Analytics
- State:
- Created a year ago
- Comments:20 (19 by maintainers)
Top Results From Across the Web
Updated editor layout support in 6.1 after refactor
WordPress 6.1 brings considerable more flexibility to the layout controls and features to the block editor. A new layout type, “constrained” ...
Read more >What is WordPress full site editing?
The site editing features are a collection of new WordPress features that focus on styling and editing blocks and using blocks for all...
Read more >Changelog | ArcGIS Hub
Stay up-to-date with new features, changes, and fixes for ArcGIS Hub. ... To add a browse button, locate the Search card in the...
Read more >What's New: 3D, Charts, and Auto Layout - Vev
What's New: 3D, Charts, and Auto Layout · Just in time for Q1, we are excited to share a ton of new features...
Read more >Release notes (2022) - Looker Studio Help - Google Support
Request new features or upvote existing feature requests here. December 20, ... We've added the following improvements to the Looker Studio report editor:....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think this might be more of a UI/UX issue than an accessibility issue. I suppose you could make an argument that only using a check mark icon to signal success might be confusing/inaccessible to some people. But since our users will learn what it means relatively quickly (since they are doing this over and over again) I don’t think this is a showstopper. I think it might be more of a question of whether you want to congratulate them or if you are satisfied with just the check mark.
Hi @ahmadabdolsaheb ,
I am interested in going for this one first : Add the modal progress bar to the button of the lower jaw. I will start on that asap