ThibWeb

8 ms·

1. 31.▲
   by ThibWeb 3y ago

   Gotcha, thank you. The reasons you mentioned are excellent, definitely a pattern that’s best avoided unless there are no other alternatives.
2. 32.▲
   by ThibWeb 3y ago

   Thanks for chiming in! Do you think it’s desirable for it to stay "ugly" then if it’s for "internal use"? I can understand the admin isn’t meant to have a "consumer" UI but it still feels like there are lots of
3. 33.▲
   by ThibWeb 3y ago

   I see three quotes from past contributors in the article, that seems like valuable knowledge to me? Anecdotally as someone who contributes to the Django admin I see the interest is there. I’d say it being clunky is for other reasons (for ex
4. 34.▲
   by ThibWeb 3y ago

   Sorry I’m not sure I understand your question? I wasn’t on the internet before web 2.0, by modals I mean things like custom-styled <dialog> element[1] and the `dialog` ARIA role, which I would say are a more recent pattern than pop-up
5. 35.▲
   by ThibWeb 3y ago

   Any particular styling extension you’d recommend? Have to confess I’ve only ever used the vanilla admin myself.
6. 36.▲
   by ThibWeb 3y ago

   Text contrast is actually one of the most common issues with the Django admin. Just on the screenshot in the article, the white text against the light blue breadcrumb and nav headers background is too low contrast as per WCAG 2.0 calculatio
7. 37.▲
   by ThibWeb 3y ago

   I’d say because you can lose context more easily when having to move to a separate browser tab / window to complete a task? And I suspect the multi-window paradigm is also harder to navigate for keyboard / screen reader users (as
8. 38.▲
   by ThibWeb 3y ago

   Yep, the different button styles for no clear reasons is one. This is even more apparent on other views. On that screenshot, you can also spot questionable alignment between e.g. checkboxes and the title text in the table. Contrast issues w
9. 39.▲
   by ThibWeb 3y ago

   It is certainly simple but I’d disagree it’s functional _enough_, because of the numerous basic accessibility issues with the fundamental UI components. On extending the admin – perhaps there’s something to be said about the admin coming wi
10. 40.▲
    by ThibWeb 3y ago

    "Ugly" might not be the best one-word description but there are a lot of basic accessibility issues with the Django admin. The general user experience could also really benefit from using more modern design patterns (for example m
11. 41.▲
    Why Is the Django Admin "Ugly"?(coderedcorp.com)

    142 points by ThibWeb 3y ago|158 comments
12. 42.▲
    Core Web Vitals Technology Report(datastudio.google.com)

    1 points by ThibWeb 4y ago|0 comments
13. 43.▲
    by ThibWeb 4y ago

    I’d be really interested in this as well (disc. – I work on Wagtail). This feels so similar to our vision for the CMS aside for the fact the project has been running for a while and is in Python land.
14. 44.▲
    by ThibWeb 5y ago

    Wagtail core developer here – here are our sprint notes [1] that demonstrate what this funding means for us in practice. The TL;DR; is being able to address long-term technical debt in the UI, improving accessibility throughout, having prop
15. 45.▲
    by ThibWeb 6y ago

    I share the same sentiment, but it would be even better if what’s shared was more factual / less dogmatic – or in this case if sourcehut itself was a better example. At a high level it’s somewhat correct that sticking to HTML-only feat