Release of the new Paste visual language and new navigation #3728
-
|
Hey Paste team! I am looking for directions from Paste on 2 areas:
Does Paste have any plan to announce this visual language change at Comms BU level and set a deadline for teams to migrate? With the direct push from Paste, it would help us nudging our cross functional partners adopting this change and make it happen. Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
Disclaimer: This is a very experimental bot using OpenAI's GPT-4. The answers may not be correct, a human will review the answer and update it if necessary. Sorry, I don't know how to help with that. I did do a search though, and I managed to find these other Discussions that might be similar or related to your question. Give them a read to see if they answer your question. If they do, head back here and update this discussion and mark it as answered, pointing others to the related discussion:
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Frank So, the answers to these questions are largely the same as they were when you asked about them back in January with some updates. The Navigation UI kit was released in August for everyone to use. So far we have seen Paste docs site (obviously), Twilio Docs, Twilio Help Center (logged in experience) and internally across One Admin adopt and deploy this experience. There might be more that we don't know about. It is entirely up to each application to adopt at their own pace, and each application owner is aware. I suspect you are also aware that each application owner has their own timelines and roadmaps that we do not control or influence. We suspect Twilio Console will adopt in Q1 / Q2 potentially, and Segment towards the end of the year. That is up to those owning two teams to decide, though, based on the priorities they own. As pointed out in the UX offsite though, we already have great traction and adoption in a few very key and important customer facing properties, and it'll be pretty soon to roll out elsewhere. For the new Design Language, this was released in Code back in April, not just Figma, and has been adopted already by Paste docs site (obviously), Twilio Docs, Twilio Help Center (logged in experience), unified login, sign up and internally across One Admin. The release of this was communicated to the Comms BU back in Q1 of 2023, along with many of the stakeholders across Twilio, and coupled with our very extensive migration guide for all Twilio properties to follow, including guides for Figma libraries and code. The new Design language is just a theme on top of the existing components. In Figma, adoption is only a mode switch and in Code a single variable change. Everything else is 1-to-1, down to design tokens if you are creating custom components. Of course, as mentioned in the UX offsite, if you are detaching components, changing the values of component properties to not use Paste design tokens, or creating custom designs that do not use design token styles from the Paste libraries, those assets are not using Paste and are not supported by the Design System team. You'll have a really unfun time, and unfortunately, it'll be your own fault. If you are using design tokens exclusively, and not modifying Paste components, you can effectively supply designs in any theme you want. It doesn't matter. To prove it, you can visit this link and then start appending With regard to a deadline, we don't deal with or set deadlines. It would be unreasonable and unrealistic to do so. It's entirely down to the application owners to handle their own priorities, of which they have many. Historically, we have great adoption traction though, and I'm really not concerned by it at all given it's already live in login, signup, docs, help center and more. The Paste version update in Console is already done, and going out to customers in February. We could roll out the new design language at will at that point, but I am suggesting we hold off until the nav and topbar are updated with the foundational model work. If you're using Figma correctly, this wait will be fine and won't have any negative effects. Once it is done, it will instantly cover 75% of every page view in Console over night. The other 25% will require teams to continue migrating to Console zen, at which point they will automatically get it, or manually updating the Paste dependency in their legacy Console micro applications. Even then, there will be a small percentage of pages that are either still in php or unowned, that will likely never get updated until they are retired and pulled out of service. That is a reality of a large company like this, unfortunately, and something we're totally fine with. Technical and design debt is a part of life. Hopefully that answers all your questions about the migration. Hang in there, it won't actually be much longer, and it'll be here before we know it. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Simon for this thoughtful reply! Really appreciate it. I will sync with the console team on the next steps on the adoption of the new visual language & the new navigation |
Beta Was this translation helpful? Give feedback.
Hi Frank
So, the answers to these questions are largely the same as they were when you asked about them back in January with some updates.
The Navigation UI kit was released in August for everyone to use. So far we have seen Paste docs site (obviously), Twilio Docs, Twilio Help Center (logged in experience) and internally across One Admin adopt and deploy this experience. There might be more that we don't know about.
It is entirely up to each application to adopt at their own pace, and each application owner is aware. I suspect you are also aware that each application owner has their own timelines and roadmaps that we do not control or influence. We suspect Twilio Console will adopt in Q1…