Conversation

Notices

1. Embed this notice
   Niléane (nileane@nileane.fr)'s status on Wednesday, 27-Dec-2023 07:25:50 JST Niléane

   • Tangerine UI for Mastodon

   @TangerineUI v2.0.0 will have a translate button that's an actual button 😌

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Wednesday, 27-Dec-2023 07:26:49 JST Tim Chambers

     in reply to

     • Tangerine UI for Mastodon

     @nileane @TangerineUI

     Have you thought of submitting some of your UX work as PR's for the main Mastodon codebase?

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Wednesday, 27-Dec-2023 09:13:26 JST Tim Chambers

     in reply to

     • Scott Starkey

     @ScottStarkey @nileane Second that!

   • Embed this notice
     Scott Starkey (scottstarkey@hoosier.social)'s status on Wednesday, 27-Dec-2023 09:13:32 JST Scott Starkey

     in reply to

     • Tim Chambers

     @nileane @tchambers

     I'd love to see what a real UI witch could do.

     Mastodon needs all the UI work it can get. Your work would be greatly appreciated.

   • Embed this notice
     Niléane (nileane@nileane.fr)'s status on Wednesday, 27-Dec-2023 09:13:35 JST Niléane

     in reply to

     • Tim Chambers

     @tchambers I might be a CSS witch, but not much more 😅 — so every time I think about submitting a PR I get demotivated by the fact that I would have to re-implement my ideas in whatever Mastodon’s using for the frontend.

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Wednesday, 27-Dec-2023 09:22:24 JST Tim Chambers

     in reply to

     • Scott Starkey

     @nileane @ScottStarkey I'd suspect it would be hit or miss as to which got in, but that they would welcome all suggestions! And you might not need to work on a PR beyond being a feature request until after it got to a certain level of momentum...then coding could happen knowing it was on a glide path to making a difference.

   • Embed this notice
     Niléane (nileane@nileane.fr)'s status on Wednesday, 27-Dec-2023 09:22:25 JST Niléane

     in reply to

     • Tim Chambers
     • Scott Starkey

     @tchambers @ScottStarkey I would definitely love it if some of my ideas were to get implemented in Mastodon’s default theme. But I’m also not sure they’d be welcomed by the team — and I wouldn’t feel motivated to work on PRs that will never get merged.

     Tim Chambers repeated this.
   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Wednesday, 27-Dec-2023 10:09:33 JST Tim Chambers

     in reply to

     • Elk
     • Roni Laukkarinen
     • Chee Aun 🤔
     • sam henri gold
     • Scott Starkey

     @samhenrigold @nileane @ScottStarkey

     On this exact topic, I'd say the same thing for @rolle and @cheeaun and @elk UX folks and early PR feature requests to the Mastodon core...

   • Embed this notice
     sam henri gold (samhenrigold@hachyderm.io)'s status on Wednesday, 27-Dec-2023 10:09:34 JST sam henri gold

     in reply to

     • Tim Chambers
     • Scott Starkey

     @nileane @tchambers @ScottStarkey We’re working on documentation in the new year to explain our design process and get more alignment on how design should work in an OSS environment. But in the meantime, PRs that aren’t radical undertakings and can be backed up with some amount of objectivity would probably be received well.

     *disclaimer, i’m just a contract designer working on the 1st party mastodon app, i don’t speak for the core dev team or the web team.

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Wednesday, 27-Dec-2023 17:23:42 JST Renaud Chaput

     in reply to

     • Tim Chambers
     • Scott Starkey

     @nileane I would definitely push for UI improvements to be merged, as well as any CSS improvements. I would like to switch to individual components CSS files (and not one huge components.scss), more CSS variables…
     We can discuss a process for this, for example issues with mockups or ideas that get flagged and validated by the team before getting implemented?
     @tchambers @ScottStarkey

     Tim Chambers repeated this.
   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Wednesday, 27-Dec-2023 20:29:28 JST Renaud Chaput

     in reply to

     • Eugen Rochko
     • Tim Chambers
     • Roni Laukkarinen
     • sam henri gold
     • Scott Starkey

     @nileane I forgot to reply on this issue, I thought I did! Will do it right now.

     I am taking some time off with family this week, but let's try to discuss this in January. I am not the one making big decisions when it comes to product design, but I am sure we can try some experiments on how to work on it with a team of trusted people, with some coordination / guidance from @samhenrigold (who heads the design for the official apps) and @Gargron

     @tchambers @ScottStarkey @rolle

   • Embed this notice
     Niléane (nileane@nileane.fr)'s status on Wednesday, 27-Dec-2023 20:29:31 JST Niléane

     in reply to

     • Tim Chambers
     • Renaud Chaput
     • Roni Laukkarinen
     • Scott Starkey

     @renchap @tchambers @ScottStarkey Moving away from SCSS variables and toward more native CSS solutions sounds like a good direction to take.

     Yep, it would be great if there were a streamlined process to formally pass UI ideas to the team.

     Speaking of issues/mockups/ideas, have you been looking at @rolle's suggestions in this issue? https://github.com/mastodon/mastodon/issues/27102#issuecomment-1869651552

     I think this alone would go a long way, and @rolle and I both seem to agree that the main nav should be on the left, not on the right.

     Tim Chambers repeated this.
   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Wednesday, 27-Dec-2023 20:32:28 JST Renaud Chaput

     in reply to

     • Tim Chambers
     • Roni Laukkarinen
     • Scott Starkey

     @rolle Yes, we definitely need this, and I want to push for it. I will need to discuss it with the team, but I am pretty sure we can experiment with new ways of working on such areas with non-core team contributors.

     @nileane @tchambers @ScottStarkey

   • Embed this notice
     Roni Laukkarinen (rolle@mementomori.social)'s status on Wednesday, 27-Dec-2023 20:32:30 JST Roni Laukkarinen

     in reply to

     • Tim Chambers
     • Renaud Chaput
     • Scott Starkey

     @nileane @renchap @tchambers @ScottStarkey Thanks for being open to changes Renaud. I think I have also suggested a structure for SCSS but I don’t recall where. Perhaps should open another issue for that for the discussion. SCSS components should be written as per their equivalent HTML elements and SCSS views structure should be in par with their jsx files, with a proper modular directory and file structure. As stated, in other words: Mastodon desperately needs its own (S)CSS framework. This is something we probably could help over time if we’d know what is the process.

     Is it going to be as simple as this:

     1. Issue (first perhaps of the structure)
     2. Discussion
     (In here splitted to more issues or branches)
     3. PR(s)?

     Not sure how this goes without being a part of the team.

     Tim Chambers repeated this.
   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Thursday, 28-Dec-2023 00:10:45 JST Tim Chambers

     in reply to

     • Renaud Chaput
     • Roni Laukkarinen
     • Scott Starkey

     @renchap @rolle @nileane @ScottStarkey

     Love every bit of where this conversation is going ✊