Replies: 21 comments 17 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Hi @rishits321, welcome. Please use the #gsoc channel on Slack for introductions, and only post here if you have specific questions or comments about this project. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Hi @pawan941394, welcome. Please use the #gsoc channel on Slack for introductions, and only post here if you have specific questions or comments about this project. I have reviewed your application , I think it’s a bit early for applications considering how little details we’ve shared about this project so far – there are no new pages to create, and we’re not expecting contributors to do a redesign. Just implement new designs onto existing pages. This is already plenty of work as it is! For now if you want to make a solid proposal for this project I would suggest asking questions based on what you’ve found out so far. |
Beta Was this translation helpful? Give feedback.
-
|
For people interested in this project, I would recommend looking at:
Questions are very welcome on all of the above – this project would be invaluable for us to see through, but I realise the scope is still a bit more nebulous than some of the other ideas. |
Beta Was this translation helpful? Give feedback.
-
|
Quick follow-up based on yesterday’s meeting – the "Wagtail UI overview" spreadsheet is there as a planning tool. It summarises what Wagtail’s admin interface is made up of: view-by-view, and component-by-component. I expect this will help to understand the scale of this project, and plan accordingly. |
Beta Was this translation helpful? Give feedback.
-
|
Here is a very practical example to illustrate what this project is about :) The second most important part of the Wagtail admin is the "explorer" views – how we navigate around a site’s pages as we manage the site’s contents. Here is a screenshot of our (WIP) redesign for this part of Wagtail: Edit: see examples here: #8158 (reply in thread) Here is what this UI looks like at the moment: https://docs.wagtail.org/en/stable/editor_manual/finding_your_way_around/the_explorer_page.html This is a good example because:
|
Beta Was this translation helpful? Give feedback.
-
|
Notes from Anuja’s questions in today’s meeting:
|
Beta Was this translation helpful? Give feedback.
-
|
Updated main description with FAQ to answer this at the top. |
Beta Was this translation helpful? Give feedback.
-
|
@thibaudcolas is it possible to get links to all current Figma files (or even screen grabs), I know some are still being roughly done internally at Torchbox but some of the potential candidates are asking, plus would be good for me to get my head around if possible. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, It will be very helpful for making good proposal and where to start :). |
Beta Was this translation helpful? Give feedback.
-
|
Updated the parent description with some images that have been floating around |
Beta Was this translation helpful? Give feedback.
-
|
Here are higher-res screenshots of three pages we have early designs of. Note this is very much experiments at this stage, that haven’t been reviewed internally and aren’t up-to-date with design changes being rolled out elsewhere. Page history
Search results
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, everyone I have question regarding this project, is this project about implementing all these features that came up in "page editor 2022" or implementing that UX design to other page like snippets, reports , setting etc. |
Beta Was this translation helpful? Give feedback.
-
|
This project is about implementation of the design and potentially shared components/ templates from the new page editor to other areas of Wagtail. As mentioned - reports, snippets etc. |
Beta Was this translation helpful? Give feedback.
-
|
Updated main description with FAQ to answer this at the top. |
Beta Was this translation helpful? Give feedback.
-
|
I don't see checkboxes on the left side of page names in the mock images shared above(page hierarchy). Should they be there? If not then how will bulk actions work. |
Beta Was this translation helpful? Give feedback.
-
|
Great question, we will either go for showing them on hover or have them always visible, I think that will be determined as we start to work through how to split up the designs into work to be implemented. |
Beta Was this translation helpful? Give feedback.
-
|
Hover should be nice. Like initially when we hover on page name than the checkbox appears for it only but once we check it then all of them become visible. |
Beta Was this translation helpful? Give feedback.
-
|
yeah, we need to consider mobile devices here but that is the general gist. |
Beta Was this translation helpful? Give feedback.
-
|
Good question indeed. What you’re suggesting makes sense to me. This is exactly the type of work we’ll need to do early on in this project – check the intended designs cover all desired functionality, and if not, understand whether any gaps are intentional (if so, look into the consequences) or not (then we need to do more designing). |
Beta Was this translation helpful? Give feedback.
-
|
Where will typescript and react come in handy during this project? While writing tests? |
Beta Was this translation helpful? Give feedback.
-
|
Some components, not many, are written in React and most of those are using TypeScript, so if we need to adjust the styles of those components (or potentially behaviour) it will help to know React but this is not critical. Unit tests however are written in JavaScript, for non-React components we also try to write solid unit tests for these. We use Jest for unit tests, we also have Integration tests https://docs.wagtail.org/en/stable/contributing/developing.html#integration-tests |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
@ajitesh13 thanks for your interest. Please use the slack channel #gosc For introductions and I recommend you read Wagtail's wiki page and Google Summer of Code's page for details. Proposals can be submitted from this week until the 20th of April This discussion is for specific questions about the project and as such I will close this discussion item. |
Beta Was this translation helpful? Give feedback.
-
|
FYI I have removed screenshots of the "page explorer" mockups above because we don’t want people to get held up on that specific design. This was a very early draft of a highly complex UI, other screenshots above are also early draft, so there is no point in discussing the specific functionality of any of them at this stage. I’ve only shared those as examples of our design vision for parts of Wagtail that aren’t the page editor. |
Beta Was this translation helpful? Give feedback.
-
|
Good question came up in Slack about testing, here is what I wrote. Hey, in regards to testing, we have
For more resources
|
Beta Was this translation helpful? Give feedback.
-
|
Added #8325 to the linked issues/discussion mainly as a reference of potentially related improvements to the dashboard. |
Beta Was this translation helpful? Give feedback.
-
|
Update - I have reviewed all the apply page editor UX proposals today, we will likely to another round of reviews soon. In general
|
Beta Was this translation helpful? Give feedback.
-
|
BETA version of the Wagtail design system (for the community) |
Beta Was this translation helpful? Give feedback.
-
|
For anyone watching this discussion, there is now a project board - still early days though. |
Beta Was this translation helpful? Give feedback.
-
|
Proposing to improvise the frontend editing more than backend editing something better than |
Beta Was this translation helpful? Give feedback.
-
|
@davidjeba thanks for the ideas but this discussion is more about aligning the new user interface styling / UX to other parts of Wagtail. I saw you commented on the page editor UI item and do not want to bounce you around but I recommend you try to frame up your thoughts in what you would like to see Wagtail implement. Then start a new discussion about this and see what feedback you get, do not be disheartened if you do not get much and also remember that anyone can build a package (yourself included) that achieves your goal. I think our current StreamField approach is quite powerful and maybe could be extended to do more drag/drop type things in the future but I am not aware of that being on the roadmap and it would be a huge undertaking. In the new discussion, maybe have a think about how to frame up what you are proposing.
I think that a complete change to the paradigm that Wagtail's UI uses is probably going to be a hard thing to get done (as most developers in Wagtail are volunteers or do big features via sponsorship). However, it is still worth discussing and seeing who else may be interested in contributing or what is already out there in the community. Thanks for being involved in the community |
Beta Was this translation helpful? Give feedback.
-
|
Update - two main issues will be the next big ones to tackle, still refining but posting here for anyone watching to add thoughts.
These two are intertwined so depending on designs received we may do parts in parallel, but most likely will try to look at the bulk of the breadcrumbs first. |
Beta Was this translation helpful? Give feedback.
-
|
Update - getting close to the Release Candidate 4.0 and it is incredible so see the amazing work as a whole that @PaarthAgarwal has done. See https://github.com/wagtail/wagtail/pull/8943/files for a bit of a preview (also, this is not even all of it, just the things that group well under the UX Unification banner).
|
Beta Was this translation helpful? Give feedback.
-
|
Prepared a list of screenshots of the pages and components that I, along with my mentors, worked on during this project to compare Wagtail 3.x with the new release candidate 4.x. |
Beta Was this translation helpful? Give feedback.
-
Incredible work here @PaarthAgarwal - here are some 1:1 comparisons. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Edit: this project has been renamed to UX Unification, and will be going ahead outside of GSoC 2022 but alongside other GSoC projects.
Apply new page editor UX to all of Wagtail
Discussion about Apply new page editor UX to all of Wagtail a Google Summer of Code project.
Reference designs
To get a sense of UX/design changes, here is a list of resources.
Useful links
mainbranch, update the frontend build (npm run build) and run Wagtail locally, you will see a bunch of differences in the sidebar (main menu) and parts of the Page EditorUI mock images
Page history:
Search results:
FAQs
Related issues
A non-complete list of potentially related existing issues (bugs/enhancements).
Some of these may already be in the scope of the page editor work, however, it might be a good reference for those wishing to contribute or for proposals.
Beta Was this translation helpful? Give feedback.
All reactions