The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Our existing login experience is brand and ambassador specific. It hasn’t been touched in years and is a bit behind the rest of the product.
We need the ability to allow brands and customers to have a different login experience when coming from different access points.
I looked through a few semi-competitors' experiences to gauge what their learnings have been. While looking for the overall flow and experience I collected samples of UI elements to give our login pages a bit of a refresh.
Keeping in mind the new pathways we want to support, I began mapping it out and looking for potential gaps in the flow.
I worked with our Customer Success team to ensure we weren’t missing anything and then began to work through the various pages.
Using Figma I began breaking out the pages into sections and keeping the wires simple.
After brief reviews with the Product team, dev team, and CS I began putting together higher fidelity mocks.
We also needed tools for the Brand side to upload the desired logos and images.
Accounting for error states, email notifications and branding fit. I prepared the story for final review and to be split out amongst the devs to begin work.
During review our COO and lead CS walked a few users through the various experiences to ensure we were on the right track.
After a few minor tweaks we sent to the dev team to build and launch.
After the release we began slowly inviting our brand users to experience the new login experience. They were shown both branded and unbranded experiences.
Some feedback we received along with some internal projects led us to revisit and tweak some of the design and spin off a few new stories to support the branded experience a bitbetter.
Because the team asked for this as a potential feature I mocked up what it would look like if we allowed the brand users to adjust colors and it wasn’t pretty.
I already knew the aspect ratios and images needed work with the Image Cropper story already slated for development but the feedback helped validate the need as well as provide additional notes to add to the story.
I took some of the learnings and and re-thought a bit of the responsive aspect as well as the colors, aspect ratio, and text placement.
While logging into our platform using google I took note of the simplicity
I began reworking our designs. Luckily because I use components, the job was quite simple to change and the result not only fixed a few of the problems we were aware of, but it also solved some complexities for dev and consistency issues throughout the rest of the app.
This was quickly launched and has been live for approximately 5 weeks. We are continually moving over users from our old experience to the new. This is both Brand and Customer users.
We have received a lot of positive feedback on the new design, flow as well as the branded experience. Because of the feedback we are seeing less users going back to the old platform and have plans to deprecate it within the next 3 weeks.
As for the other pathways into the login experience, we have yet to launch our new product that will utilize product sharing as well as links meant for organic users.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Joshua Home
New York Times
Nulla vitae elit libero, a pharetra augue.
New York Times
Our existing login experience is brand and ambassador specific. It hasn’t been touched in years and is a bit behind the rest of the product.
We need the ability to allow brands and customers to have a different login experience when coming from different access points.
I looked through a few semi-competitors' experiences to gauge what their learnings have been. While looking for the overall flow and experience I collected samples of UI elements to give our login pages a bit of a refresh.
Keeping in mind the new pathways we want to support, I began mapping it out and looking for potential gaps in the flow.
I worked with our Customer Success team to ensure we weren’t missing anything and then began to work through the various pages.
Using Figma I began breaking out the pages into sections and keeping the wires simple.
After brief reviews with the Product team, dev team, and CS I began putting together higher fidelity mocks.
We also needed tools for the Brand side to upload the desired logos and images.
Accounting for error states, email notifications and branding fit. I prepared the story for final review and to be split out amongst the devs to begin work.
During review our COO and lead CS walked a few users through the various experiences to ensure we were on the right track.
After a few minor tweaks we sent to the dev team to build and launch.
After the release we began slowly inviting our brand users to experience the new login experience. They were shown both branded and unbranded experiences.
Some feedback we received along with some internal projects led us to revisit and tweak some of the design and spin off a few new stories to support the branded experience a bitbetter.
Because the team asked for this as a potential feature I mocked up what it would look like if we allowed the brand users to adjust colors and it wasn’t pretty.
I already knew the aspect ratios and images needed work with the Image Cropper story already slated for development but the feedback helped validate the need as well as provide additional notes to add to the story.
I took some of the learnings and and re-thought a bit of the responsive aspect as well as the colors, aspect ratio, and text placement.
While logging into our platform using google I took note of the simplicity
I began reworking our designs. Luckily because I use components, the job was quite simple to change and the result not only fixed a few of the problems we were aware of, but it also solved some complexities for dev and consistency issues throughout the rest of the app.
This was quickly launched and has been live for approximately 5 weeks. We are continually moving over users from our old experience to the new. This is both Brand and Customer users.
We have received a lot of positive feedback on the new design, flow as well as the branded experience. Because of the feedback we are seeing less users going back to the old platform and have plans to deprecate it within the next 3 weeks.
As for the other pathways into the login experience, we have yet to launch our new product that will utilize product sharing as well as links meant for organic users.