<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dhruvi Butti on Medium]]></title>
        <description><![CDATA[Stories by Dhruvi Butti on Medium]]></description>
        <link>https://medium.com/@dhruvi16?source=rss-42c5d7cc78ca------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5CAzTUtm_42VP0As0GujNg.jpeg</url>
            <title>Stories by Dhruvi Butti on Medium</title>
            <link>https://medium.com/@dhruvi16?source=rss-42c5d7cc78ca------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:30:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dhruvi16/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Case study: An UX twist for your kitchen]]></title>
            <link>https://medium.com/design-bootcamp/an-ux-twist-for-your-kitchen-ba1098d411c0?source=rss-42c5d7cc78ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba1098d411c0</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Dhruvi Butti]]></dc:creator>
            <pubDate>Sun, 13 Mar 2022 18:34:39 GMT</pubDate>
            <atom:updated>2022-03-16T06:18:19.788Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Kitchen Space" src="https://cdn-images-1.medium.com/max/1024/0*0zM9A-u1TpIsEXn_" /><figcaption>Photo by <a href="https://unsplash.com/@naomish?utm_source=medium&amp;utm_medium=referral">Naomi Hébert</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Yeah! You read that right. This is a story where kitchen meets UX. Ahh my bad! Its not at all a story, this blog talks about how a user can get an upgrade in their daily kitchen experience through a small design thinking activity.</p><p>Lemme start with a quick walk through of Design Thinking -</p><h4><strong>Definition</strong></h4><blockquote>It’s a process/method to design products. It consists of five steps that I will explain below. Generally they are not followed linearly as each step result is kind of interlinked with the other ones.</blockquote><h4>Problem Statement -</h4><p>Improve kitchen experience for a user group. A little context on this — I am a part of Anudeep’s UX design course on growth school and this is a design activity that I did during the initial weeks of the course.</p><h4>Logistics -</h4><p>You are given a group of 4–5 people who you can interview to empathize with as well as test your prototypes. They all act as a target user group who needs an upgrade in their kitchen experience.</p><h4>Step 1 — Empathize 👥</h4><blockquote>As I said it is not a linear process but I used step 1 just for elaboration. Empathize as its name suggests includes empathizing with the user to find out what are their pain points. This can be done via various methods like conducting a survey or interviewing target audience or secondary research etc etc.</blockquote><p>For us, we performed this step by interviewing the user group we had. Before setting up interviews I worked on a set of conversational points/questions using which I can know the user and their pain points better. Below you can see the questions I prepared so I can have a efficient user interview.</p><figure><img alt="User interview questions" src="https://cdn-images-1.medium.com/max/936/1*uPcUJCT0QynG5VLQbXd9KQ.png" /><figcaption>User interview questions</figcaption></figure><h4>Step 2 — Define 📓</h4><blockquote>After knowing what the pain points are we sit and decide on the problem statements. We jot down crisp and relevant problem statements for which we can find solutions later. This might seem unnecessary but I realised during the exercise that it is quite an important step. Its simply that you won’t have a clear solution if you do not have a clear problem statement.</blockquote><p>After taking the interviews and jotting down small summaries, I defined certain problem statements. These were basically the pain points I found out the users had. Below are the problem statements -</p><figure><img alt="Problem statements" src="https://cdn-images-1.medium.com/max/841/1*YpBipz3XsYmh07zBm5N4Xg.png" /><figcaption>Problem statements</figcaption></figure><h4>Step 3 — Ideate 💭</h4><blockquote>I used crazy 8 trick here for brainstorming solutions for the problem statements I defined in the last step. Crazy 8 is a method where you think of 8 ideas in 8 minutes. So this helps you generate a variety of ideas and explore variety of perspectives.</blockquote><p>This was the hardest step for me as I could not think of 8 ideas in 8 mins. It took much more longer to even come up with bunch of ideas. I will not bore you with typing out all of them. Here are the top three ideas that I chose -</p><figure><img alt="Top 3 solutions" src="https://cdn-images-1.medium.com/max/888/1*OnxySY5gZRxq-9M8j3bVpw.png" /><figcaption>Top 3 solutions</figcaption></figure><h4>Step 4 — Prototype 📝</h4><blockquote>This is a technical step where you go ahead and model your solution. You can use anything for instance, sketch book, clay and for digital products we have some great tools like Figma, Adobe XD etc etc.</blockquote><p>I prototyped the first idea and created a map of sorts. You can see it here -</p><figure><img alt="Kitchen map" src="https://cdn-images-1.medium.com/max/1024/1*hlca5mZb2sY4hrd5x4Gbtg.png" /><figcaption>Kitchen map</figcaption></figure><p>There are 4 main categories in which the kitchen is largely divided into -</p><ol><li>Tools — Consists of all the tools required in the kitchen from cooking to storing to prepping.</li><li>Utensils — Consists of all the kinds of utensils to prep or eat or serve a meal.</li><li>Food articles — All the stored food and ingredients that can be found in the kitchen</li><li>Miscellaneous — All the material that you feel cannot be described in the above categories.</li></ol><p>These categories are then further subdivided into rather small groups according to their use in the kitchen. Each group or the whole category is assigned to a label for example 1:B or 1:C:a which indicates their position in the kitchen. For ex — Here I have numbered my kitchen counter as 1 and divided into 4 parts A, B, C, &amp; D and the gas stove sits in the B part of the counter. Hence that will have a label there saying this is 1:B.</p><p>This chart is highly customizable, you can beautify and add/delete items and also reorganize them as per your kitchen requirements. The idea is basically to have a blueprint/map of your kitchen so you or anyone have no hard time organizing or accessing the kitchen items.</p><h4>Step 5 — Test 🔌</h4><blockquote>This step involves testing your model with the users and validating what you have created. This step is a deciding step on whether you should go ahead and build your product. The results might take you back to any of the above steps in order to improve your end results.</blockquote><p>For testing, I simply presented my solution to the target user group and they were quite impressed by this easy solution. But they did have some constructive feedback and hence asked for the features mentioned below -</p><ul><li>The map should be digital as it’s easier to maintain and update that way.</li><li>Mapping things and arranging them in real world would take a lot of energy at first.</li><li>Add search features in a digital map.</li><li>Add notifications for movement of things in the real world</li><li>Add add/delete button on every node.</li></ul><p>I took into account a couple of changes and those were — Making the map digital and adding an add/delete button on nodes would obviously make the users life easier.</p><figure><img alt="Updated kitchen map" src="https://cdn-images-1.medium.com/max/1024/1*hlOvbCdYFITgU-rgdwzIHQ.png" /><figcaption>Updated kitchen map</figcaption></figure><p>So, this marks the end of design thinking activity and hope y’all had fun reading it.</p><p>Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba1098d411c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/an-ux-twist-for-your-kitchen-ba1098d411c0">Case study: An UX twist for your kitchen</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The specifics — Vocabulary Front.]]></title>
            <link>https://medium.com/@dhruvi16/the-specifics-vocabulary-front-de81a609877f?source=rss-42c5d7cc78ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/de81a609877f</guid>
            <category><![CDATA[specific]]></category>
            <category><![CDATA[creative-commons]]></category>
            <category><![CDATA[vocabulary]]></category>
            <category><![CDATA[design-language]]></category>
            <category><![CDATA[outreachy]]></category>
            <dc:creator><![CDATA[Dhruvi Butti]]></dc:creator>
            <pubDate>Mon, 17 Aug 2020 14:11:41 GMT</pubDate>
            <atom:updated>2020-08-27T15:46:25.813Z</atom:updated>
            <content:encoded><![CDATA[<h3>The specifics — CCOS Revamp.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mnkIwlB2rL8t9vf_8jn52w.jpeg" /></figure><p>In this blog, I will be talking about how I managed to use Vocabulary ( Creative Commons’s Design Library ) efficiently in our Open Source website.</p><h4><strong>What is Vocabulary?</strong></h4><p><a href="https://cc-vocabulary.netlify.app/?path=/story/vocabulary-introduction--page">vo·cab·u·lar·y</a></p><p>Vocabulary is a cohesive design system to unite the web-facing Creative Commons. In essence Vocabulary is a component library that uses and extends <a href="https://bulma.io/">Bulma</a> CSS library. Vocabulary makes it easier to develop Creative Commons apps while ensuring a consistently familiar experience. This project is still under development.</p><h4><strong>Why Vocabulary?</strong></h4><p>Vocabulary is used to describe the overall visual design of our digital products. At first glance, it <strong>appears</strong> to be: an amalgamation of component designs with a consistent visual aesthetic and brand, typically accompanied by usage guidelines in the form of online documentation. But there is a lot more to it.</p><p>When it comes to a large software community with a huge range of products, certain problems come along. One of those problems is maintaining the level of harmony across all the products of the network. So, there comes a need for a unified visual language that heightens the level of harmony in a digital ecosystem. And in our case, Vocabulary solves this problem.</p><p>This design system is well built and helps us bring the following aspects to the table -</p><ol><li>Recognizability</li><li>Consistency</li><li>Authenticity</li><li>Efficiency</li></ol><p>And many more.</p><h4><strong>How did I use it? — Examples</strong></h4><p>As I stated before, I have added Vocabulary by updating all the Templates in the CCOS Lektor project.</p><p>As far as components are concerned, I just had to paste the code snippets given on the Vocabulary’s website with the requires changes -</p><p><strong>Integration of Breadcrumb -</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BQD6U_xcmox4MBDFZ4NHaA.png" /><figcaption>Screenshot —<a href="https://cc-vocabulary.netlify.app/?path=/docs/navigation-breadcrumb--default-story"> Breadcrumb</a> (Vocabulary)</figcaption></figure><p><em>The code for integration —</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/738a3b5362ff3564fd01b4d6bb5a5642/href">https://medium.com/media/738a3b5362ff3564fd01b4d6bb5a5642/href</a></iframe><p>Other than the components, there are other visual elements like typography, colors, spacing, and others that are extensively used in CCOS.</p><p>This is code for the Hero section of the home page.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/677c1a82b621e6bfc0e47c6fb6df85fc/href">https://medium.com/media/677c1a82b621e6bfc0e47c6fb6df85fc/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/52e5944e8694584b593b1c2cae340b69/href">https://medium.com/media/52e5944e8694584b593b1c2cae340b69/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fTAZRZpnYL0tqksfSOtUHA.png" /><figcaption>The output.</figcaption></figure><h4>Improvements in the Lektor project -</h4><p>I tried to write the perfect code that is cleaner and readable. I would try to demonstrate my effort using the home page code where I used <a href="https://www.getlektor.com/docs/models/flow/">Lektor Flowblocks</a>. The new homepage design have four sections where each section communicated something and I realized they were all independent and building the whole page through one single template would become a bit messy and hard to handle. So I did some research and found a way where I could build sub-templates and use them all to develop a single page and Lektor’s flowblocks allowed me to do so. Here is one of the flowblock and if you want to check out the whole working you can go to — <a href="https://github.com/creativecommons/creativecommons.github.io-source">CCOS Repository</a>.</p><p><strong>Recent Blog Posts Block —</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e46d0b52b56c2e25a609c40043050083/href">https://medium.com/media/e46d0b52b56c2e25a609c40043050083/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QKUO8JTM6nSdCYBonTEACg.png" /><figcaption>Output — Recent blog posts.</figcaption></figure><p>I would also like to point out the amazing <a href="https://www.getlektor.com/docs/api/db/pad/query/">Query</a> functionality provided by Lektor where you can access the child pages of the root. Here I am accessing blog posts from our Blog page and limiting the count of posts to three.</p><h4>Difference in Experience</h4><p>The level of user experience has been significantly elevated due to the use of Vocabulary. I would like to point one of the major experience change here. The major part of the website is guidelines — we have guidelines for contributing, guidelines for how to join a community, guidelines for how to write a blog and many more. The new website has cleaner and readable guideline with a proper hierarchy and every piece of information is made accessible using secondary navigation.</p><p>Below are the images of some guidelines pages from new website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UGTUqrIqFZsx6ygC9j0bVw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BUOdcAvAjB8mj_sO3r31RA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9-YHAXfnyqV0XmVh8RFGAg.png" /><figcaption>Guidelines pages from new website</figcaption></figure><p>Below are the images of some guidelines pages from old website. You can see the difference of experience in both cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3abxVpsaD_D6x8Up6A7mmA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z9z7LTH621eQR6I2v0XTLg.png" /><figcaption>Guidelines pages from old website.</figcaption></figure><h4><strong>How you can use vocabulary and also contribute to it?</strong></h4><p>Vocabulary is very easy to use. It is intuitive, consistent and highly reusable. Vocabulary uses <a href="https://storybook.js.org/">Storybook</a> to present each visual element that makes it very convenient for a user to integrate Vocabulary in their project. The code snippets attached with every element can be copied as it is and can be used. The code snippets above indicate how the library can be used and how easily you can achieve desired web pages. For more details, you can visit <a href="https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-usage--page">usage guidelines</a>.</p><p>Vocabulary is still under development, feedback and bug reports are welcome, fixes and patches even more so. Here is the <a href="https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-contribution--page">link</a> to contribution guidelines.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de81a609877f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is up? — Revamping CCOS]]></title>
            <link>https://medium.com/devstudio/what-is-up-revamping-ccos-192777452cf1?source=rss-42c5d7cc78ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/192777452cf1</guid>
            <category><![CDATA[lektor]]></category>
            <category><![CDATA[revamp]]></category>
            <category><![CDATA[outreachy]]></category>
            <dc:creator><![CDATA[Dhruvi Butti]]></dc:creator>
            <pubDate>Mon, 13 Jul 2020 10:14:37 GMT</pubDate>
            <atom:updated>2020-07-20T10:36:54.299Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is up? — Revamping CCOS</h3><p>Well in my previous <a href="https://medium.com/devstudio/integration-of-vocabulary-with-ccos-157283623fbc">blog</a>, I demonstrated what was my Outreachy project about. Here I will talk about my progress in the past 7 weeks.</p><p><strong>The Set-Up -</strong></p><p>The <a href="https://opensource.creativecommons.org/">Creative Commons Open Source</a> website is built using <a href="https://www.getlektor.com/">Lektor</a>. I was not very familiar with Lektor, so I started by going through the documentation and the official website code. I learned how awesome it is and can also be used by non-coders. I got familiar with the <a href="https://jinja.palletsprojects.com/en/2.11.x/">jinja</a> templates and working of themes in a Lektor app. For integrating new styles from Vocabulary, I replaced <em>templates/</em> folder with a <em>theme/</em> folder.</p><p>As the revamping process is gradual, there was a need of setting up a staging environment where we could test the website. Deploying the branch that consists of the ongoing changes was pretty easy, I just followed the official <a href="https://www.netlify.com/blog/2016/05/25/lektor-on-netlify-a-step-by-step-guide/">documentation</a> provided by Netlify and deployed it.</p><p><strong>Adding New Components to Vocabulary -</strong></p><p>The <a href="https://www.figma.com/file/mttcugI1UxvCJRKE5sdpbO/Mockups">mock-ups</a> for the new CCOS website extensively use Vocabulary components, styles, and patterns, and it had components that were not available in Vocabulary. So, I worked on building them from scratch. I enjoyed this part a bit too much. And also this was a part of the project, I did not think would take up like 2 weeks but it did. I enjoyed questioning the scope, the design, the experience of the components, and getting satisfactory answers. Maintaining the practices, focusing on details were fun things to do. It felt like I own those components. You can check them out <a href="https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-introduction--page">here</a> and also use them wherever needed.</p><p><strong>Updating Templates of the Theme -</strong></p><p>I started by updating the home page template. I try to make the code cleaner and more readable. Going through the <a href="https://www.getlektor.com/">Lektor</a> documentation, I came across different ways to do so. One of them was <a href="https://www.getlektor.com/docs/content/flow/">flow blocks</a>, I like how it makes a template more modular and readable so I implemented the home page using flow blocks. This one after one, I started updating every template. For now, I have updated 10 templates and I plan to update the remaining in upcoming weeks.</p><p><strong>My Experience so far -</strong></p><p>This has been one heck of a journey for me. I have never collaborated with such a huge open-source organization and so that was something new for me. I have learned a lot of things both technical and non-technical so far. I have become more alert about the code I write, this journey has helped me improve the questions I ask to myself while writing code or thinking about the solution, I got to learn about new technologies such as <a href="https://www.getlektor.com/">Lektor</a>, <a href="https://webpack.js.org/">Webpack</a>, <a href="https://sass-lang.com/documentation/syntax">SCSS</a> and many more. I am just very glad to be a part of this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=192777452cf1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devstudio/what-is-up-revamping-ccos-192777452cf1">What is up? — Revamping CCOS</a> was originally published in <a href="https://medium.com/devstudio">DevStudio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integration of Vocabulary with CCOS.]]></title>
            <link>https://medium.com/devstudio/integration-of-vocabulary-with-ccos-157283623fbc?source=rss-42c5d7cc78ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/157283623fbc</guid>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[creative-commons]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[vocabulary]]></category>
            <dc:creator><![CDATA[Dhruvi Butti]]></dc:creator>
            <pubDate>Tue, 07 Jul 2020 19:13:45 GMT</pubDate>
            <atom:updated>2020-07-07T19:13:45.846Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog demonstrates the project I am working on during the course of my Outreachy internship. My project involves redesigning and reimplementing one of the web products of the CC network using our new cohesive design library —<a href="https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-introduction--page"> Vocabulary</a>. After completion of my internship, the <a href="https://opensource.creativecommons.org/">Creative Commons Open Source</a> website will have a completely different looking interface that will extensively use Vocabulary components.</p><p>I will start by explaining the problem -<br>There exists a large variety of web products across the Creative Commons network. These products serve different purposes for the network and so do they vary in the way of presenting the existing content. So, to conquer the inconsistency across the different products we have our coherent design system called Vocabulary.</p><p>If we come to the current CC Open Source website, it is quite off-track considering our new design system Vocabulary. The styles and components of the website are not well aligned with the components of the Vocabulary. And thus it lacks harmony and consistency concerning the brand.</p><p>The purpose of a design system gets dissolved if it is not well incorporated with the products and we do have this problem with the CC Open Source website. Hence, there was a need for a redesign of CCOS as per the new Design Library. This project aims to rectify the problems and inconsistencies of the CCOS website and build a completely new website (as per Vocabulary).</p><p>The solution -<br>I started with trying out different mock-ups for the new website in Figma. You can see what I tried to make <a href="https://www.figma.com/file/ka3zs1iYnqJvyLnvAV3cW7/Home-proposals">here</a>. And then with the help of our UX designer Francisco, we created all the mock-ups and finalized how the website will look in a couple of weeks, here the <a href="https://www.figma.com/file/mttcugI1UxvCJRKE5sdpbO/Mockups?node-id=759%3A516">link</a> for that.</p><p>I started my internship with going through the website’s tech stack, the website is made using Lektor, with which I was not very familiar. I read the official docs went through projects, tried making demo projects, and took help from mentors wherever I got stuck.</p><p>To keep the project clean I added a theme that only has templates for the project and alters no content (as per aim). While updating templates, some components were not available in the Vocabulary yet, so I worked on adding those components to the library. And then used them in my new templates. You can see the ongoing work <a href="https://cc-open-source-dev.netlify.app/">here</a>.</p><p>I have thoroughly enjoyed contributing to this project as I got to learn so much. And I am excited for what’s next to come in the coming weeks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=157283623fbc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devstudio/integration-of-vocabulary-with-ccos-157283623fbc">Integration of Vocabulary with CCOS.</a> was originally published in <a href="https://medium.com/devstudio">DevStudio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design ALT + ernatives.]]></title>
            <link>https://medium.com/devstudio/design-alt-ernatives-e42d421b772a?source=rss-42c5d7cc78ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/e42d421b772a</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Dhruvi Butti]]></dc:creator>
            <pubDate>Sun, 21 Jun 2020 22:21:46 GMT</pubDate>
            <atom:updated>2020-06-21T22:21:46.944Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I will be talking about the next step of the UX design cycle and that is <strong>Design Alternative</strong>.</p><p>This article is inspired by a Coursera course, <a href="https://www.coursera.org/learn/user-experience-design/">Introduction to User Experience</a>.</p><p>At this point in the design cycle, we have enough knowledge of the problem space as we have completed the first step — Resource Gathering. By problem space, I mean we have enough knowledge about the user, the task, the current way of accomplishment, and other relevant data. Now, the goal of the next step is to use the data and come up with a better design alternative which is both useful and usable. By useful, I mean an interface that accomplishes the task, and by usable, I mean an interface that is efficient, effective, and satisfying.</p><p>The goal of processing the data to achieve a better interface or system does not have an isolated environment. The system affects an individual, a group of people, and even a society. A designer needs to keep in mind how his/her designs benefit them all.</p><p>I am picking up a simple example from my Outreachy journey so far as to illustrate design alternatives. I am currently working on the implementation of the newly designed <a href="https://opensource.creativecommons.org/">CCOS</a> (You can find mock-ups <a href="https://www.figma.com/file/mttcugI1UxvCJRKE5sdpbO/Mockups?node-id=759%3A516">here</a>). Consider the blog page redesign, as explicit data, we have the reason why people use a blog page and that is “gaining knowledge” and as designers, we implicitly conclude that a user uses blogs to “gain concentrated knowledge in a small amount of time”. So as the first step designer extracts the implicit needs of the user which were not explicitly mentioned while resource gathering. These implicit needs help us to develop a better interface. From phase 1, we also have functional and non-functional requirements of the interface like the functional requirements for a blog page is to list out all the blog posts and the non-functional requirements are how well these posts are laid out so the user gets to the interesting posts as quickly as possible.</p><p>With the help of this phase, we were able to determine the shortcomings of the current blog page. We thus made it more readable by using a boxy layout than a list, increased title fonts to make the blogs more catchy, added excerpts to inform the user before-hand about the content of the blog.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e42d421b772a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devstudio/design-alt-ernatives-e42d421b772a">Design ALT + ernatives.</a> was originally published in <a href="https://medium.com/devstudio">DevStudio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Resource gathering.]]></title>
            <link>https://medium.com/devstudio/resource-gathering-abf9845e3423?source=rss-42c5d7cc78ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/abf9845e3423</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Dhruvi Butti]]></dc:creator>
            <pubDate>Tue, 02 Jun 2020 15:29:05 GMT</pubDate>
            <atom:updated>2020-06-08T13:22:22.956Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*gFkUfyiLXRVTSDHh" /><figcaption>Photo by <a href="https://unsplash.com/@dandimmock?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dan Dimmock</a> on <a href="https://unsplash.com/s/photos/resources?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I will be describing the UX design cycle with a series of articles and this article is about describing the first step of the design cycle which is <em>Resource Gathering</em>.</p><p>As an outreachy intern, I am handling the integration of <a href="https://creativecommons.org/">Creative Commons </a>design library — <a href="https://cc-vocabulary.netlify.app/">Vocabulary</a> with one of our web products — <a href="https://opensource.creativecommons.org/">CC OS</a>. I have been working the design library for 3–4 months now and I have enjoyed the experience the library caters and I am trying to achieve the same experience in the Open source website. To understand UX in-depth, I have been reading different resources and document this knowledge through this series of blogs. This in-depth information will help me achieve the desired experience through the library.</p><p>The core concept of user experience design is that users use interfaces to accomplish a task. User experience design starts with the user, by user I mean the individual that is using some technology to accomplish some goal.</p><p>The interface consists of an input and output through which the user interacts with the system. For instance, clicking a photo requires the user to press the button(input) and an image is the desired output. Creating an affordable and usable interface is the main goal of this process. Design is a data-driven process and resource gathering is all about gathering this data.</p><p>The resource gathering process is about figuring out how the task is accomplished by the user currently. There are 4 ways to gather data and below I will describe them all in detail. There are two types of data — Quantitative(Numeric) and Qualitative(Thematic) and designers prefer to use both types of data as per requirement.</p><ol><li>Naturalistic observation -<br>The goal of naturalistic observation is to watch the user in action in their environment. Rather than asking the user what, when, and where she accomplishes a given task, the designer goes out to where the task takes place and observes the user. Most naturalistic observations take place in the field rather than the lab because we want to get a sense of the environment where the task takes place. During the naturalistic observation session, the data collected can be either qualitative or quantitative. Qualitative data may be a set of notes written by the designer as he observes the user. Quantitative data may be collected during a naturalistic observation session as well.</li><li>Surveys -<br>A survey is quite simply a set of questions. The goal of surveys is to get the user’s opinions. Most often, we get them to provide a self-report about their behavior, perceptions, attitudes, and feelings. We can also get their opinion about someone else. Surveys can take place in the field or the lab. Surveys require little direct interaction, the survey may be physical where someone hands you a sheet of paper, but now it’s more common to have them be completely digital. Either you step up to a kiosk, or one opens up automatically when you browse a website.</li><li>Focus Groups -<br>The goal of conducting a focus group is to engage users in direct conversations. Focus groups take place in a controlled environment, usually a room where users can feel free to share and discuss information in a private setting. Focus groups allow for a high degree of interaction, more so than a survey, but less so than an interview. A focus group allows the design team to meet with a group of five to ten users. This group should be representative of the user group that the designers want to address. The design team includes a trained moderator who organizes the topics of conversation among the users. A note-taker who keeps track of the major conversation points between the users and the moderator. And if possible it should also include a media person, who either audiotapes or videotapes the session.</li><li>Interview -<br>The goal of an interview is to gather in-depth information from a user. An interview can take place either in the field or in the lab. The one requirement is that there is enough privacy that the user can freely answer the questions being asked. The interview offers the designer an opportunity to have a conversation with the user. This is valuable because the interviewer can then follow any interesting lead the user can have. During the interview session, the data collected will mostly be qualitative.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abf9845e3423" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devstudio/resource-gathering-abf9845e3423">Resource gathering.</a> was originally published in <a href="https://medium.com/devstudio">DevStudio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Takeaways from my FOSS journey!]]></title>
            <link>https://medium.com/devstudio/takeaways-from-my-foss-journey-62c34a132d1d?source=rss-42c5d7cc78ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/62c34a132d1d</guid>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[journey]]></category>
            <category><![CDATA[takeaways]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Dhruvi Butti]]></dc:creator>
            <pubDate>Fri, 22 May 2020 14:16:05 GMT</pubDate>
            <atom:updated>2020-05-22T14:16:05.546Z</atom:updated>
            <content:encoded><![CDATA[<h3>Take aways from my FOSS journey!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nqMfXfUSR3h9Xvif.jpg" /><figcaption><a href="https://www.flickr.com/photos/60255995@N04/14774214687">“Sky at night”</a> by <a href="https://www.flickr.com/photos/60255995@N04">Rychu92</a> is licensed under <a href="https://creativecommons.org/licenses/by-sa/2.0/?ref=ccsearch&amp;atype=rich">CC BY-SA 2.0</a></figcaption></figure><p>First let me introduce myself because of course I am not a very famous blogger or writer.</p><p>I am Dhruvi. I am a third-year undergrad student. I am a designer/developer and also a FOSS enthusiast. I started my opensource journey a year ago (that is around Feb ’19) and now here I am starting my Outreachy internship with this blog (not literally of course). I am consistent, curious, and creative, and below I will tell you how these three C’s have helped me through my journey.</p><p>Below are the four things that I think might be the ‘takeaways’ from my experience -</p><h4>NOW is the time -</h4><p>There is no better time than now! Let’s accept the fact that most of the students wait for “the time” to start with opensource as most of us want to get into programs like GSoC, Outreachy, and many more. But I figured it is very necessary to know that whether you are interested in opensource or is it only the big internships attracting you. So, to get these answers, you need to explore, and to explore I suggest you start today. I am very fond of asking myself the question ‘Why?’ and to answer those questions I explore, I invest time. So start finding answers to your whys? today.</p><h4>Start SLOW -</h4><p>For me the start was a little overwhelming and that made me push it away. And to avoid that I tried starting small and slow. By small and slow, I mean try the easy things first, like getting aware of the logistics. Personally, general practices or set of rules calm me down when I try to get into some uncomfortable zones. And yes opensource was not a very comfortable zone for me in the beginning (I mean what is *wink). To keep myself motivated, I started with familiar things like contributing to familiar projects or familiar good first issues (the easy ones). Completing a task or two gave me a lot of confidence and made me stick around.</p><h4>Choose WISELY -</h4><p>After playing around for some time and getting familiar with the logistics, I went for a project hunt. I listed my areas of interest and areas which seemed exciting to me. Using those filters I found some amazing projects which were actively being worked on. I got my answers to why would I want to work on these projects? by working on them. I believe if you are interested the motivation will be natural. With some projects, I felt connected and I did not feel the need of pushing myself for contributing to them. My only advice for making a wise choice is that “Don’t push yourself too hard”!</p><h4>Speak through your WORK -</h4><p>When I was sure, I wanted to work on a particular project I started getting familiar with the community (the specifics). I got familiar with the ideas and agendas the community had behind the projects. And fortunately, I got to work with the most amazing and inspiring people who helped me when I was stuck and I plan to keep working with them. I kept doing a few things which I guess might be worth mentioning -</p><ol><li>Try to write the most appropriate and relevant code.</li><li>Try to break the solution into small understandable parts.</li><li>Try to take initiatives. Small initiatives like opening issues will also work (Yes! opening relevant and meaningful issues is an initiative.).</li><li>Know when to ask for help from the community (I am still working on this).</li></ol><p>I know this was not an article full of resources and tips to get into Outreachy or GSoC but I just wanted to communicate that students should see that opensource is a broader concept. I wanted to share a personal take and help the beginners with my own experience. Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62c34a132d1d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devstudio/takeaways-from-my-foss-journey-62c34a132d1d">Takeaways from my FOSS journey!</a> was originally published in <a href="https://medium.com/devstudio">DevStudio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Lektor?]]></title>
            <link>https://medium.com/devstudio/why-lektor-e95f54a71cb3?source=rss-42c5d7cc78ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/e95f54a71cb3</guid>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[node]]></category>
            <category><![CDATA[lektor]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[static-websites]]></category>
            <dc:creator><![CDATA[Dhruvi Butti]]></dc:creator>
            <pubDate>Wed, 13 May 2020 09:01:52 GMT</pubDate>
            <atom:updated>2020-05-13T14:04:48.493Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*nrlUVaUrtA6Up2jkXoezuA.png" /><figcaption>why? why? why?</figcaption></figure><p>I wrote this article while prepping for my Outreachy internship. I was trying to find out why Lektor is being used for the project and found out really convincing reasons for the same.</p><p>Let’s start with basic types of website -</p><ol><li>Static website: Here the webpages are pre-loaded to the server and when the request is made, these pages are served to the client as it is. These webpages can use HTML, CSS, and Javascript. By static, it does not mean that these webpages are devoid of user interactivity. These pages can be highly reactive (because of course JS) but yes they are not generated on the server and are static in that manner.</li></ol><p>2. Dynamic website: Here the webpages are generated by the server. It is connected to a database and all the data is fetched from there. It uses server-side scripting and also client-side scripting (if necessary). It is called dynamic because the webpages are processed by the server.</p><p>So why go static? — Because the vast, vast majority of websites will be read many more times than they will be updated. This is crucial because dynamic content does not come for free. It needs server resources and because program code is running there it needs to be kept up to date to ensure there are no security problems that are left unpatched. Also when a website gets a sudden spike of traffic a static website will stay up for longer on the same server than a dynamic one that needs to execute code.</p><p>There are certain drawbacks of static websites we are going to focus on here and how Lektor helps us to combat those.</p><p>Drawbacks -</p><p>1. Multi-page websites are really hard to manage — Updating the content can be a cumbersome task here.</p><p>2. Lack of dynamic content.</p><p>3. Unavailability of the admin side of the website — This makes hard for non-technical people to edit the website.</p><p>Lektor helps to combat all the shortcomings listed above. It is built using Node.js and Python and is very easy to understand and use.</p><ol><li>The first drawback has a very common solution that is templates. Lektor has a file structure that consists of — content, models, and templates. This structure helps us to manage multi-page websites without any cumbersome copy-pasting.</li><li>This drawback can be overcome by using external services or in house micro-services. These services can easily be integrated into your Lektor project. This will save time and give efficient results.</li><li>This is the most amazing thing that Lektor does. Combating this shortcoming makes Lektor stand out. Lektor takes from content management systems like WordPress and provides a flexible browser-based admin interface from which you can edit your website’s contents. Unlike traditional CMS solutions, however, it runs entirely on your computer. This means you can give a Lektor website to people that have no understanding of programming and they can still modify the content and update the website.</li></ol><p>Due to such capabilities, I find this framework amazing and I am excited about using it. Though there are many points untouched in this blog I would try to write a more in-depth blog when I learn about it more during my internship.</p><p>Credits — This blog is inspired by <a href="https://2016.ploneconf.org/talks/static-websites-with-lektor.html">https://2016.ploneconf.org/talks/static-websites-with-lektor.html</a> and also for more details you can check out <a href="https://www.getlektor.com/">https://www.getlektor.com/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e95f54a71cb3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devstudio/why-lektor-e95f54a71cb3">Why Lektor?</a> was originally published in <a href="https://medium.com/devstudio">DevStudio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>