<?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[DevStudio - Medium]]></title>
        <description><![CDATA[Dev Studio is a developer circle by IIIT Surat - Medium]]></description>
        <link>https://medium.com/devstudio?source=rss----b1bdc5315e1d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>DevStudio - Medium</title>
            <link>https://medium.com/devstudio?source=rss----b1bdc5315e1d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:14:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/devstudio" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Best folder structure for flutter app with riverpod]]></title>
            <link>https://medium.com/devstudio/best-folder-structure-for-flutter-app-with-riverpod-ba72ceb780b3?source=rss----b1bdc5315e1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/ba72ceb780b3</guid>
            <category><![CDATA[flutter-architecture]]></category>
            <category><![CDATA[riverpod]]></category>
            <category><![CDATA[flutter-riverpod]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[rkishan516]]></category>
            <dc:creator><![CDATA[KISHAN RATHORE]]></dc:creator>
            <pubDate>Sun, 07 Jul 2024 08:59:59 GMT</pubDate>
            <atom:updated>2024-07-07T08:59:59.022Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re building a big and complex app, it’s important to consider the folder structure. Without it, your unorganized code can hinder your progress over time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*H1rNLlDnWtI7yf2WqtHbcw.gif" /></figure><p>Each state management library in Flutter has many folder structure patterns, including Riverpod. However, the pattern We are sharing with you is easy to understand, test, debug, and scale. It also allows for easy code clean-up and refactoring, as well as simple migration from any other structure. Let’s take a closer look and see how simple it actually is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*a0ttqJt3hu_wdKU35B3U6A.gif" /></figure><p>First, divide the app into features. Say your app has four features; your structure will look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9DMq4kz69HjCI75RLJdfYA.png" /><figcaption>App level structure</figcaption></figure><p>The app-level structure includes three layers:</p><ol><li>Presentation Layer</li><li>Logic Layer</li><li>Data Layer</li></ol><p>But for better organization, modify the structure for each feature:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*CqbzxloJrN6Hjan3xnM4Uw.png" /><figcaption>Feature level sturcture</figcaption></figure><ol><li><strong>Presentations :- </strong>This folder contains the widget code that’s rendered on the screen.</li><li><strong>States :- </strong>This folder contains all the states that widget apdat to render something different.</li><li><strong>Notifiers :- </strong>This folder contains the business logic to manage the widget state.</li><li><strong>Services :- </strong>This folder contains the business logic to manage the application state.</li><li><strong>Models :- </strong>This folder contains the data model to share data coming from the repository to notifiers or services.</li><li><strong>Repositories :- </strong>This folder contains the handling for data coming in and out from your database or server.</li><li><strong>Data Providers :- </strong>This folder contains all your data sources, such as fake data, server calls, or database calls.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*wc22UXuiFzRRT-iX2VtJYw.gif" /></figure><p>That’s it! You can add as many features as you want and remove them easily if they’re not required. Test each layer individually, debug only the folder with the problem, and solve it quickly like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*gm3_WY9iYBgAlWE03742vw.gif" /></figure><p>You can also explore example <a href="https://github.com/rkishan516/SpacerTranslator">here</a>. We hope to see you in our coming articles.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba72ceb780b3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devstudio/best-folder-structure-for-flutter-app-with-riverpod-ba72ceb780b3">Best folder structure for flutter app with riverpod</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[What is up? — Revamping CCOS]]></title>
            <link>https://medium.com/devstudio/what-is-up-revamping-ccos-192777452cf1?source=rss----b1bdc5315e1d---4</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:53 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----b1bdc5315e1d---4</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:14:02 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----b1bdc5315e1d---4</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:22:13 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----b1bdc5315e1d---4</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:33 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----b1bdc5315e1d---4</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:24 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----b1bdc5315e1d---4</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>Sat, 16 May 2020 15:15:37 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>
        <item>
            <title><![CDATA[Roaring Flutter in Every Platform]]></title>
            <link>https://medium.com/devstudio/roaring-flutter-in-every-platform-b341190b8ae0?source=rss----b1bdc5315e1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/b341190b8ae0</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[webdev-labs]]></category>
            <dc:creator><![CDATA[KISHAN RATHORE]]></dc:creator>
            <pubDate>Fri, 08 May 2020 07:50:56 GMT</pubDate>
            <atom:updated>2019-07-31T03:09:03.023Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kgvN_jTqRpMvkXKz.jpg" /></figure><p>We are living among different technologies of mobile, web and desktop app development. The market of mobile, desktop and responsive web is growing at a rapid pace and highly dynamic and cross-platform application have become cakewalk to build for developers.</p><p>In this article, we are going to look at sensational flutter which is roaring high in every sphere of society.</p><h3>What is Flutter?</h3><p>Flutter is Google’s cross-platform SDK or portable UI toolkit/framework for building beautiful, natively compiled applications for <a href="https://flutter.dev/docs">mobile</a>, <a href="https://flutter.dev/web">web</a>, and <a href="https://flutter.dev/desktop">desktop</a> from a single codebase.</p><p>It makes app development faster, efficient and gives native-like experience without compromising the speed of the development.</p><h4>Why Flutter?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*toqoqFo163iAGqYb.jpg" /></figure><h4>1. Single Codebase, Single Language</h4><p>Flutter makes beautiful UI in a very easy manner and unlike some platform, here we have single codebase and single language for developing the app for mobile, web and desktop. It’s possible because this tool has special widgets and unique designs that makes it capable to develop the same app to cater to different platforms.</p><h4>2. Awesome Documentation</h4><p>Flutter has neat and very simple documentation which is well-organized which doesn’t need developers to put extra effort into learning it. That’s why it’s becoming a popular choice among developer.</p><h4>3. Fast Development</h4><p>Flutter’s hot reload has changed the way of app development. Just change the code and look the result in realtime. Moreover, it’s a way to establish coordination between developers and designers but if designers have given their UI then also developers can easily create them without designers.</p><h4>4. Widget’s and Animation</h4><p>A single sentence in flutter makes it very easy i.e. “Everything in flutter is widget”. Creation of UI in flutter is easy because it has a lot of widget’s inbuilt in material library and Cupertino library. As far as animation is concerned flutter gives us a facility to render 60 frames per second and flare ( A powerful design and animation tool) makes easy to animate in apps.</p><h4>5. Flutter Community</h4><p>Flutter community is working hard day by day to build libraries, plugins and help the newcomers to flutter. As flutter has support from Google it also attracts a developer to move to flutter.</p><h3>Flutter with Different Operating Systems</h3><p>Google initially started flutter for fuchsia OS development which is in build phase now. Then in 2016, they extended it to build android and iOS app which became an attraction to developer and businesses.</p><p>After watching this success, Google and Flutter team thought to extend it for web and they launched its preview in December 2018 (Flutter Live Event).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uk_e1Tc_mDoYHQWo.png" /></figure><p>And now Google has come with its idea to extend flutter for desktop and embedded system. Still, the team is working to extend Flutter to support desktop as a target environment, allowing developers to create macOS, windows, and linux applications with Flutter.</p><h3>Conclusion</h3><p>Flutter is a futuristic cross-platform development tool that is specifically built to make high-end mobile, web and desktop apps tailored to suit specific business needs. Many of companies like Dream11, Tencent, Alibaba, Google Ads, AppTree, Google Greentea, Hamilton Musical already shifted to flutter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b341190b8ae0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devstudio/roaring-flutter-in-every-platform-b341190b8ae0">Roaring Flutter in Every Platform</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[Flutter Book - Intro]]></title>
            <link>https://medium.com/devstudio/flutter-book-intro-64c25678980b?source=rss----b1bdc5315e1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/64c25678980b</guid>
            <category><![CDATA[learn]]></category>
            <category><![CDATA[rkishan516]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[flutter-widget]]></category>
            <category><![CDATA[flutterio]]></category>
            <dc:creator><![CDATA[KISHAN RATHORE]]></dc:creator>
            <pubDate>Fri, 08 May 2020 07:50:12 GMT</pubDate>
            <atom:updated>2019-09-12T04:13:38.321Z</atom:updated>
            <content:encoded><![CDATA[<h3>Flutter Book</h3><p><strong>Flutter </strong>the awesome SDK by Google to developing Android and iOS App as well as now available for web also. So, if you are the one who wants to learn this futuristic technology, then here I have given the best way to learn that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O8O73T8zKOHHw7iw.jpg" /></figure><p>I think Reading ( complex cognitive process of decoding symbols to derive meaning ) is just opposite of definition easiest way of learning the things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/0*77C9JSGzJl8Oq3QE" /></figure><p>So, before starting with Flutter you should have knowledge of these:-</p><ol><li><strong>Dart Language</strong></li><li>“<strong>Everything</strong> in <strong>Flutter</strong> is a <strong>Widget</strong>”</li></ol><p>So, in this series of articles the sequence will be something like this:-</p><p>A) Layout</p><ol><li>Stateful and Stateless widget</li><li>Container Widget with Rows and Column</li><li>Text Widget</li><li>Buttons (RaisedButton, FlatButton, IconButton) Widget</li><li>Icon Widget</li><li>Image Widget</li><li>Center Widget</li><li>Text Field Widget</li><li>Checkbox and Radios Widget</li><li>Slider, Switches and Indicators Widget</li><li>Stack Widget</li><li>Date Picker</li><li>Sized Box</li><li>Decorated Box Widget</li><li>Card Widget</li><li>Rich Text Widget</li><li>List view and Grid view</li><li>Table Widget</li><li>Expansion Panel Widget</li><li>Stepper Widget</li><li>Tab Bar View</li><li>Tooltip and Chip Widget</li><li>Form and Form Field</li><li>Popup Menu Button</li><li>Rotated Box Widget</li><li>Transform Widget</li><li>Opacity Widget</li><li>Padding Widget</li><li>Expanded and Flex Widget</li></ol><p>B) Scaffold</p><ol><li>AppBar</li><li>Drawer and Floating Action Button</li><li>Footer Buttons and Bottom Navigation Bar</li></ol><p>C) Notification</p><ol><li>Simple Dialog</li><li>Alert Dialog</li><li>Snack Bar</li><li>Bottom Sheet</li></ol><p>D) Navigation</p><ol><li>PushNamed &amp; PushNamedUntilAndRemove</li><li>Push and Pop</li></ol><p>E) State Management</p><ol><li>Redux</li><li>BLoC Pattern</li><li>Global State</li><li>Passing Variable</li><li>Scoop Model</li><li>Provider</li></ol><p>F) Animation</p><ol><li>Tween Animation</li><li>Hero Animation</li><li>Animation builder with listener</li><li>Animated Widget</li></ol><p>G) Charts</p><ol><li>Introduction to Charts</li></ol><p>H) Phone Integration</p><ol><li>URL Launcher</li><li>Permissions</li><li>Contacts</li><li>Camera</li></ol><p>I) Firebase With Flutter</p><ol><li>Firebase authentication ( Anonymous and Google authentication )</li><li>Firebase Storage ( Real-Time Database )</li></ol><p>So, this will be the sequence in with that you can learn day by day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TuS0L6Ld6DEliLTT.jpg" /></figure><p>Hope to see you in coming articles.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64c25678980b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devstudio/flutter-book-intro-64c25678980b">Flutter Book - Intro</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[How to Install WiFi Driver of RTL8723BE in Ubuntu 18.04]]></title>
            <link>https://medium.com/devstudio/how-to-install-wifi-driver-of-rtl8723be-in-ubuntu-18-04-1c031e2baf5?source=rss----b1bdc5315e1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/1c031e2baf5</guid>
            <category><![CDATA[ubuntu]]></category>
            <dc:creator><![CDATA[KISHAN RATHORE]]></dc:creator>
            <pubDate>Fri, 08 May 2020 07:45:24 GMT</pubDate>
            <atom:updated>2018-06-11T12:20:43.492Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, I got the update of Ubuntu 18.04 and I update my Ubuntu to 18.04 LTS. After this update, I found that some of the drivers are no more available on my Ubuntu Desktop. But the most important WiFi Driver also wasn’t there. So, I Google that how to recover or install the WiFi Driver. I found many codes and many links. But at the end of the day, I found this method that I have mentioned below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vw758BjCJO5p-lZB7rxGVg.png" /></figure><p>First of all enter in Terminal by pressing Ctrl+Alt+T.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AgQP6k6z5neD8nNBFsD4HQ.png" /></figure><p>In terminal enter “git<strong> </strong>clone https<a href="https://github.com/lwfinger/rtlwifi_new.git">://github.com/lwfinger/rtlwifi_new.git</a><strong>”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OfG3wLbW1Cxzcv0918IVXg.png" /></figure><p>Now enter “cd rtlwifi_new”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fYHHeP3ZvOtfZ2j2UM9gKw.png" /></figure><p>And now press “git checkout origin/extended -b extended”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hNhSPzM1eitq6G5d0OZT6Q.png" /></figure><p>Now I understood that what’s going on under the hood and for install this I press “sudo make install” in a terminal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TJ9XyFc0QdzolU2eFu-O4A.png" /></figure><p>After this enter “sudo modprobe -r rtl8723de”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J_IG6DzU5pPa3hhZpwCoHw.png" /></figure><p>Again enter “sudo modprobe rtl8723de”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2_V8trYYl_jdhm8YHrxsnA.png" /></figure><p><strong>Congratulations!</strong></p><p>Now WiFi is ready to use and connect to router by click on WiFi icon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c031e2baf5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devstudio/how-to-install-wifi-driver-of-rtl8723be-in-ubuntu-18-04-1c031e2baf5">How to Install WiFi Driver of RTL8723BE in Ubuntu 18.04</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>