Hi, please review it and let me know if there are any changes to make.

Hi, I’ve addressed the previous feedback and already updated the merge request.
Please let me know if anything further needs to be adjusted.
Thanks.

Thanks for the clarification I’ve updated the merge request Overview description to align with the commit message

Hi, I’ve checked the GitLab Commits section of MR-60.
It shows a single commit, and opening that commit displays the structured commit message including the separate Bug: T416500 footer.
I’ve attached a screenshot below showing this view.

Hi, I’ve updated the commit message to follow the Gerrit guidelines and added the separate Bug: T416500 footer. Thanks

Hi
The changes for this task are in this merge request - MR-60

Thanks, I’ll wait for the review.

Hi
I’ve pushed the updates to the same merge request - MR-61
The 404 page now includes the existing header, sidebar and footer.
Screenshots in previous comment reflect the latest changes.

Done.
I’ve added the existing header, sidebar, and footer to the 404 page and fixed the layout so it matches other pages.
Screenshots below (desktop and mobile, light and dark modes).
Thanks
Desktop :

Hi,their is a slight change in UI I have discarded one button because root route or home route contain the main tool and no different routes
so only have one button now redirectly to root route
Current UI :

Hi
I’ve opened a merge request for this task:
This is the Merge Request MR-61
Please let me know if any changes are needed.

I have attached some screenshots for this rendering issue

Yes I used some AI assistance mainly to help improve the wording and structure of the comment so that the findings could be presented clearly in Markdown.
All testing, experiments, and technical observations are from my own manual debugging.

Thanks for the pointer — to add more context as requested:

Hi @Reputation22
I noticed there is a related merge request proposing cookie-based polling during login, but it does not appear to have been merged.
I tested the current production instance and the original issue is still reproducible. After completing the Wikimedia OAuth flow and redirecting back to VideoCutTool, the UI remains in the unauthenticated state (Login button visible, no “Welcome <username>” in the header).
The authenticated view only appears after performing a manual page refresh, which matches the behavior described in this task.
I’ve attached screenshots showing:
the UI state before login and immediately after completing OAuth (without refresh), and

Hi,
I’ve drafted a possible UI direction for the common 404 page in VideoCutTool and wanted to check if this approach looks reasonable for the project.
At the moment, the idea is to keep the implementation fully React-based and lightweight, without introducing additional images or assets, and focus on a clear, purpose-driven 404 experience. That said, I wanted to ask whether this minimal approach is preferred, or if adding some simple visuals would be better for user experience.
Please let me know if this direction makes sense, or if you’d suggest any changes to the layout, wording, or overall approach. I’m happy to iterate based on feedback.
Thanks.

Thanks for pointing this out, I’ll follow these guidelines going forward.

Thanks for the note.
I’ll clean up the patch to remove the unrelated whitespace and formatting changes and keep the diff focused strictly on the socket listener fix. I’m working on this and will update the merge request shortly.

Hi @Aklapper ,
I’ve reviewed this issue and have a clear understanding of how the 404 handling for invalid edit URLs can be implemented.
I would like to work on this task. Kindly assign it to me.
Thank you.

I’ve opened a GitLab merge request that addresses this issue by moving the socket.on('update') listener into a useEffect hook with proper cleanup to avoid duplicate listener registrations and repeated state updates.

I plan to work on the VideoCutTool project on GitLab. It is a tool for editing videos on Wikimedia Commons, and I am interested in contributing to it through code contributions.
I have experience with React JS and Node JS, and I would like to get access to the GitLab repository so that I can explore the codebase, set up the project locally, and start contributing.

@Aklapper
Thanks for the clarification. I understand now that this task is scoped specifically for @pwangai and is not intended for general contributions.
I had misunderstood the purpose of the task earlier. I’ll follow the New Developers guidance for next steps.
Appreciate the explanation.

@zeljkofilipin
Thanks for the pointer. I’ll go through the New Developers page.
I’m interested in starting with code contributions and would appreciate guidance on which repository or component would be a good place to begin.
It would also be helpful to know the primary tech stack used in that area (frontend/backend) so I can get set up correctly.

Hi! I am Kunal Verma👋
I’m new to contributing to Wikimedia open source and I’m really excited to get started.
I understand this task is about creating a continuity page, but I’m not fully clear on the expected structure and required details yet.
Could someone please point me to the relevant documentation or a good example to follow? I want to make sure I do this correctly.
Thanks