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.
mormon.org is a site dedicated to helping people get answers to their questions and learn more about the church and its beliefs. Different areas had different challenges that needed help to grow and become a better more performant system.
I worked on key features to provide system structure and usability early on in the process. I worked on the UX Strategy, Interaction Design & Front-End Prototyping of various features.
After discussions with the client, team, missionaries and members, we learned some valuable insights into the hopes and desires for the product. We also learned that there were many pain points that existed in the system and in the systems that surrounded mormon.org.
As mormon.org had plans to grow, my team and I needed key people from other departments to participate in different design activities. These activities broke down walls and created a culture of shared ownership around future product vision.
I started looking into social networks and personal services to understand their onboarding process and how they would collect information to cater the content their users would see. I created alternate accounts to sites I used and walked through the process to gain a greater understanding. I looked for:
I mapped out the flow that would allow for multiple admins at different tiers. This would allow for roles and permissions to be established and begin to solve our approval flow problem. This structure was just the start to addressing our international and localized communities.
I took the ideas and research and began playing with numerous ideas and thoughts to solve the problems we were facing.
Being able to work on multiple problems allowed me to see where there were crossover and reusability.
From the whiteboard ideas, I began implementing the ideas into a more refined state. Wireframing a few and in some instances added them to Marvel for e as a clickable prototype.
This project continued on after I left employment for another opportunity. As far as I am aware the product never launched as direction shifted throughout the organization.
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.
mormon.org is a site dedicated to helping people get answers to their questions and learn more about the church and its beliefs. Different areas had different challenges that needed help to grow and become a better more performant system.
I worked on key features to provide system structure and usability early on in the process. I worked on the UX Strategy, Interaction Design & Front-End Prototyping of various features.
After discussions with the client, team, missionaries and members, we learned some valuable insights into the hopes and desires for the product. We also learned that there were many pain points that existed in the system and in the systems that surrounded mormon.org.
As mormon.org had plans to grow, my team and I needed key people from other departments to participate in different design activities. These activities broke down walls and created a culture of shared ownership around future product vision.
I started looking into social networks and personal services to understand their onboarding process and how they would collect information to cater the content their users would see. I created alternate accounts to sites I used and walked through the process to gain a greater understanding. I looked for:
I mapped out the flow that would allow for multiple admins at different tiers. This would allow for roles and permissions to be established and begin to solve our approval flow problem. This structure was just the start to addressing our international and localized communities.
I took the ideas and research and began playing with numerous ideas and thoughts to solve the problems we were facing.
Being able to work on multiple problems allowed me to see where there were crossover and reusability.
From the whiteboard ideas, I began implementing the ideas into a more refined state. Wireframing a few and in some instances added them to Marvel for e as a clickable prototype.
This project continued on after I left employment for another opportunity. As far as I am aware the product never launched as direction shifted throughout the organization.