<?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 Bismita Guha on Medium]]></title>
        <description><![CDATA[Stories by Bismita Guha on Medium]]></description>
        <link>https://medium.com/@bguha?source=rss-2afb039aa001------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*Fa56uE7Q6d6Qoa-HQRHXeA.jpeg</url>
            <title>Stories by Bismita Guha on Medium</title>
            <link>https://medium.com/@bguha?source=rss-2afb039aa001------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:08:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bguha/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[Winding up GSoC’20]]></title>
            <link>https://medium.com/anitab-org-open-source/winding-up-gsoc20-89203bbf85e4?source=rss-2afb039aa001------2</link>
            <guid isPermaLink="false">https://medium.com/p/89203bbf85e4</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[contribution]]></category>
            <category><![CDATA[anitab-open-source]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Bismita Guha]]></dc:creator>
            <pubDate>Mon, 24 Aug 2020 22:27:40 GMT</pubDate>
            <atom:updated>2020-08-24T22:31:12.183Z</atom:updated>
            <content:encoded><![CDATA[<h4>GSoC’20 — The good thing about 2020</h4><p>So the Coding Phase finally comes to an end, and a few more days to wind up everything. GSoC has given me a great learning experience and an opportunity to be a part of a community and work to build something which will be used by many. In this blog, I will summarize my experience. I was selected as a student in <a href="https://github.com/anitab-org">AnitaB.org Open Source</a>.</p><p><a href="https://summerofcode.withgoogle.com/projects/#6743530602496000">Google Summer of Code</a></p><p>My project <strong>Open Source Programs</strong> changed its track during the Community Bonding period from an application with a fixed purpose to being a very dynamic, processing and automating, application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g5RBYeGe0VLB6t_ZsvO_wQ.png" /></figure><blockquote><strong>Planning</strong></blockquote><p>The <strong>Community Bonding</strong> period is spent mostly on planning the project and creating a roadmap of everything you will be working on. Also, you have fun sessions and get to know the community better like Coding standards followed or practices preferred. The better you can plan out your work here, the lesser challenges you face.</p><blockquote><strong>Coding Phase</strong></blockquote><p>This basically involves you writing code, working on mentors’ reviews, developing the features and lots of learning. Not just writing code, you need to document everything for further reference. It’s not just your work on the project, but there will be many more people who will be contributing to it later on.</p><blockquote><strong>Challenges I faced</strong></blockquote><p>While planning and discussions things look like a smooth run, but you never know what problems may come in between. Sometimes, debugging simple things also become complex.</p><p><strong>Uploading to AWS bucket</strong> — My project involved uploading files from the frontend to the AWS bucket, but there is no specific documentation on how to do it using ReactJS. So this part took a lot of time as I faced errors while doing it, and really needed a lot of research to figure out a suitable way.</p><p>You may have a look at this blog I’ve written to try its implementation:</p><p><a href="https://medium.com/anitab-org-open-source/uploading-files-to-aws-using-reactjs-9f3f85c0135d">Uploading files to AWS using ReactJS</a></p><p><strong>Sendgrid Email feature</strong> — My project needed integration for sending emails, and I chose to go ahead with Sendgrid API for this purpose. The documentation was not that great so that I could easily implement things. Simple things like variables to be used and how flexible we can get with testing were missing. Have a look at this blog for the approach:</p><p><a href="https://medium.com/anitab-org-open-source/gsoc20-coding-phase-week-3-9d084ea55bdc">Email confirmation process using Django and Sendgrid</a></p><p><strong>Maintaining Code quality and Documentation </strong>— While referring to the documentation of various services I need in my project, I realized the importance of good documentation. Your project doesn’t get hits if it isn’t documented properly. Since my GSoC project, was a from-scratch project, good documentation was necessary as it would have future contributors and more feature additions. Also writing code that can be easily understood and modified based on future requirements was a necessity in this project. I had to concentrate on all these factors while making a contribution, which made me aware of the coding standards and techniques being followed globally.</p><blockquote><strong>Blogs</strong></blockquote><p>During my Coding Phase, I penned down my experiences in Medium blogs weekly. Do give them a read —</p><ul><li><a href="https://medium.com/anitab-org-open-source/gsoc20-coding-phase-week-1-4f0df051fdf1">API testing using Postman and Newman</a></li><li><a href="https://medium.com/anitab-org-open-source/gsoc20-coding-phase-week-2-6d13932e372f">JWT Authentication using Django REST Framework</a></li><li><a href="https://medium.com/anitab-org-open-source/why-prefer-server-side-rendering-157b4ad41e45">Why prefer Server-Side Rendering?</a></li><li><a href="https://medium.com/anitab-org-open-source/more-into-redux-e0b1f8e26867">More into Redux…</a></li></ul><blockquote><strong>Inviting Contributions</strong></blockquote><p>There are tons of new features and developments which can be done in Open Source Programs project. These contributions will help you learn a lot and expand your knowledge. Not just already discussed ideas, we do need wonderful ideas which everyone can come up with. If you are looking to contribute here are some important links —</p><p><a href="https://anitab-org.zulipchat.com/#narrow/stream/237907-open-source-progs">Zulip Chat</a> | <a href="https://github.com/anitab-org">GitHub</a></p><ul><li><a href="https://github.com/anitab-org/open-source-programs-web/wiki">anitab-org/open-source-programs-web</a></li><li><a href="https://github.com/anitab-org/open-source-programs-backend/wiki">anitab-org/open-source-programs-backend</a></li></ul><p><em>Happy Open-Sourcing!!!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89203bbf85e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/anitab-org-open-source/winding-up-gsoc20-89203bbf85e4">Winding up GSoC’20</a> was originally published in <a href="https://medium.com/anitab-org-open-source">AnitaB.org Open Source</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why contribute to Open Source?]]></title>
            <link>https://medium.com/anitab-org-open-source/why-contribute-to-open-source-af5bc966e295?source=rss-2afb039aa001------2</link>
            <guid isPermaLink="false">https://medium.com/p/af5bc966e295</guid>
            <category><![CDATA[anitab-open-source]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[information]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Bismita Guha]]></dc:creator>
            <pubDate>Mon, 17 Aug 2020 21:24:13 GMT</pubDate>
            <atom:updated>2020-08-17T22:00:44.298Z</atom:updated>
            <content:encoded><![CDATA[<h4>I am almost towards the GSoC Coding period now, and I feel eligible enough to describe a few reasons on why you should contribute to Open-Source.</h4><p><strong>Open Source Software</strong> (OSS) is software with source code that anyone can inspect, modify, and enhance. Open source projects are a great way of developing quality products by working together with other developers. <strong>You create code that benefits the community.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mo8jBqqAyEvLP5HNpffxLg.png" /></figure><blockquote><strong>Learning</strong></blockquote><p>You get to learn and develop a lot of software skills. You gain a clear idea of contributing to previously written code and following patterns and guidelines being followed by the community. Also, each project has separate different levels of required tests and documentation. So you get to learn right from the setup of the project till finding where the error is and successfully implementing the changes. Also your knowledge of using a version control system increases.</p><p>As you keep contributing you realize that you gain a deeper understanding of concepts involved in the project. Usually, <strong>your first contribution is not up to the mark</strong> of the project, or maybe you had to implement things differently. So your submission will undergo reviews and discussions which will help you develop, get a better grasp of the accepted practices in development and writing code which the next developer can clearly understand.</p><blockquote><strong>Building a portfolio</strong></blockquote><p>Once you start open-sourcing it’s like an addiction and you start becoming members of various communities. This opens the doors to various opportunities because your <strong>Github profile</strong> stands out and many communities conduct conferences which you get invited to. These conferences are learning hubs and a great place to network. Along with this, you get a community for being involved constantly, to develop, brainstorm and contribute.</p><blockquote><strong>Make your own ideas available</strong></blockquote><p>You have an idea which can be useful to many people, and you need a platform to develop and showcase it? You can obviously bring it up to your community and start working on the project.</p><p>OSS helps us create better technology, nicer tools and user-friendly work environments. Be it Linux or Git, every great project was once at a very initial stage and now there are so many contributors that have helped make it awesome and wonderful. We cannot deny that almost everyone reading this blog is using these.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F26tn33aiTi1jkl6H6%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F26tn33aiTi1jkl6H6%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExY3d1NnNxNGJpdWoyYW02cHJyMnEwNGtuMm12Y253dGxvNzNwbmc4ZCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2F26tn33aiTi1jkl6H6%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/53c433cc54b5b6de2b774b317a463275/href">https://medium.com/media/53c433cc54b5b6de2b774b317a463275/href</a></iframe><p>My GSoC was with <a href="https://github.com/anitab-org">AnitaB.org Open Source</a> and I worked on a project from scratch. It was just a proposed idea by the community, and so many discussions and brainstorming have now made it at a stage which maybe no one thought at the beginning. It is a great feeling to be contributing to the benefit of many and learning so much, in a short time.</p><p><em>Willing to meet you at the other end of your laptop! Happy Developing…</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af5bc966e295" width="1" height="1" alt=""><hr><p><a href="https://medium.com/anitab-org-open-source/why-contribute-to-open-source-af5bc966e295">Why contribute to Open Source?</a> was originally published in <a href="https://medium.com/anitab-org-open-source">AnitaB.org Open Source</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Uploading files to AWS using ReactJS]]></title>
            <link>https://medium.com/anitab-org-open-source/uploading-files-to-aws-using-reactjs-9f3f85c0135d?source=rss-2afb039aa001------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f3f85c0135d</guid>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[aws-s3]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <dc:creator><![CDATA[Bismita Guha]]></dc:creator>
            <pubDate>Thu, 13 Aug 2020 16:42:53 GMT</pubDate>
            <atom:updated>2020-08-15T22:09:18.637Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is a simple way for uploading files to an AWS S3 bucket using ReactJS</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ASCANX-9KL4yUBMiMbo6Sg.png" /></figure><p>Storing files in AWS buckets is safer than saving them on the server. So there are just a few simple steps which can help you do this. Once you create the bucket, go to the <strong>Permissions</strong> tab and enter the CORS configuration:</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;CORSConfiguration xmlns=&quot;http://s3.amazonaws.com/doc/2006-03-01/&quot;&gt;&lt;CORSRule&gt;&lt;AllowedOrigin&gt;*&lt;/AllowedOrigin&gt;<br>&lt;AllowedMethod&gt;POST&lt;/AllowedMethod&gt;&lt;AllowedMethod&gt;GET&lt;/AllowedMethod&gt;<br>&lt;AllowedMethod&gt;PUT&lt;/AllowedMethod&gt;&lt;AllowedMethod&gt;DELETE&lt;/AllowedMethod&gt;&lt;AllowedMethod&gt;HEAD&lt;/AllowedMethod&gt;&lt;AllowedHeader&gt;*&lt;/AllowedHeader&gt;&lt;/CORSRule&gt;&lt;/CORSConfiguration&gt;</pre><p>Get the AWS keys and enter them in your .env file. Now just entering the keys won’t work, because by default ReactJS uses the NODE_ENV , so to ensure it uses the variable from your .env file begin both the names with REACT_APP_ . Only then will they be read.</p><p><a href="https://create-react-app.dev/docs/adding-custom-environment-variables/">Adding Custom Environment Variables | Create React App</a></p><p>Next, you need to import those variables in your required files. Install <a href="https://www.npmjs.com/package/dotenv">dotenv</a> package for the same. Just one more function away.</p><p>Write a similar kind of function to make the PUT request to the AWS bucket.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2e8f7b61774ac43d21a972895f19a25c/href">https://medium.com/media/2e8f7b61774ac43d21a972895f19a25c/href</a></iframe><p>This function can onClick or onChange of any button or field, and can be configured more. Read the official documentation here:</p><p><a href="https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/s3-example-photo-album.html">Uploading Photos to Amazon S3 from a Browser</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f3f85c0135d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/anitab-org-open-source/uploading-files-to-aws-using-reactjs-9f3f85c0135d">Uploading files to AWS using ReactJS</a> was originally published in <a href="https://medium.com/anitab-org-open-source">AnitaB.org Open Source</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why prefer Server-Side Rendering?]]></title>
            <link>https://medium.com/anitab-org-open-source/why-prefer-server-side-rendering-157b4ad41e45?source=rss-2afb039aa001------2</link>
            <guid isPermaLink="false">https://medium.com/p/157b4ad41e45</guid>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[client-side-rendering]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[server-side-rendering]]></category>
            <category><![CDATA[nextjs]]></category>
            <dc:creator><![CDATA[Bismita Guha]]></dc:creator>
            <pubDate>Mon, 03 Aug 2020 20:12:36 GMT</pubDate>
            <atom:updated>2020-08-14T19:24:58.178Z</atom:updated>
            <content:encoded><![CDATA[<h4>So I came across these interesting concepts and facts during my GSoC project, although it’s not a part of my project specifically, but worth sharing…</h4><p>Whenever you build an application, you start taking into consideration optimization techniques to handle multiple requests and responses within a short time span. Here is when we need to start thinking of choosing between <strong>Server-Side Rendering </strong>(SSR) and <strong>Client-Side Rendering </strong>(CSR).</p><p><strong>SSR</strong> is a popular technique for rendering a client-side <em>single page application</em> (SPA) on the server and then sending a fully rendered page to the client.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nteTCH5EJGTAY0LL8HhHHA.png" /><figcaption>Source: Google Images</figcaption></figure><p>Just as the name suggests it is very clear that obviously SSR gives better performance than CSR. SSR is when HTML is built on the server than on the browser. It is preferred mainly due to 2 reasons:</p><ul><li>Better performance</li><li>Search Engine Optimization (SEO)</li></ul><p>CSR happens when an empty HTML file is first served to the browser and then HTML is built on the browser and the painting is started. We can summarize the steps for each of them as follows after the request for the page is made by the browser:</p><p><strong>Server-Side Rendering</strong></p><ul><li>The server sends ready to render HTML page to the browser</li><li>The browser renders the HTML page, which is now <strong>viewable to users</strong></li><li>Then the browser downloads JS</li><li>Now React is loaded and the browser executes it</li><li>The page is now <strong>interactable</strong></li></ul><p><strong>Client-Side Rendering</strong></p><ul><li>The server sends the response to the browser</li><li>The blank HTML page is loaded</li><li>Then the browser downloads JS</li><li>React is loaded and the browser executes it</li><li>The page is not <strong>viewable to users </strong>and <strong>interactable</strong></li></ul><blockquote><strong>The Increase in Performance</strong></blockquote><p>The loading part which can be seen as a blank page flicker in CSR does not happen when using SSR. Now let’s look at a few cases in CSR:</p><ul><li>If the user clicks on a button or performs some action before the page becomes interactable, the action won’t get executed until the React gets properly loaded.</li><li>There is the obvious distinction in that the output of CRA (static files) can be served up through any web server (say a <a href="https://www.akamai.com/uk/en/cdn/what-is-a-cdn.jsp#:~:text=CDN%20Definition,the%20server%20and%20the%20user.">CDN</a>) while the output of <em>Next.js</em> (being server-rendered) is served up by a <em>Node.js</em> server (going to be substantially slower than a CDN).</li></ul><blockquote><strong>React SSR Framework</strong></blockquote><p>For rendering React on the Server-Side you might want to use <strong>Next.js.</strong></p><p><a href="https://nextjs.org/">Next.js by Vercel - The React Framework</a></p><p>There are obviously a few cons of Next.js, so as a developer one should always be open to new ideas and learning. You can turn your CRA into the server-side rendering by <a href="https://create-react-app.dev/docs/pre-rendering-into-static-html-files/"><strong>Pre-Rendering with CRA</strong></a>. Have a look at this blog:</p><p><a href="https://www.digitalocean.com/community/tutorials/react-server-side-rendering">How to Enable Server-Side Rendering for a React App | DigitalOcean</a></p><p>From <a href="https://www.netflix.com/">Netflix</a> to <a href="https://github.com/">GitHub</a> many applications are using Next.js. Even non-image content in CRA gets displayed at a delayed rate from Next.js. To get into more performance details and testing, have a look at this <a href="https://github.com/goldenshun/nextjs-cra">Github Repo</a>. As the main page of Next.js mentions, it is a React Framework for:</p><ul><li>Production</li><li><a href="https://web.dev/progressive-web-apps/">Progressive Web Apps</a> (PWAs)</li><li>Pre-Rendered Apps</li><li>SEO friendly sites</li><li>The Desktop</li><li>The Mobile Web</li><li>Static Websites</li><li>Lightweight Apps</li></ul><p><em>…and many more</em></p><p>While writing the code the JSX Components are almost similar in both, but how the API is fetched differs in both cases. There is a major time gap if we look at the content-loading of both cases and for large-scale applications, this affects the performance to a huge extent. The First Meaningful Paint usually has a difference of 6–7 seconds, because downloading all the required bundles for an application takes up ample time and you can see where the lag is caused.</p><p>One of the cons of Next.js is that image files aren’t cached. The first load of Next.js doesn’t involve downloading the bundles, so your user has already started viewing the static page content before Javascript got even downloaded by your browser.</p><blockquote><strong>Resources</strong></blockquote><ul><li><a href="https://medium.com/walmartglobaltech/the-benefits-of-server-side-rendering-over-client-side-rendering-5d07ff2cefe8">Walmart Labs Blog</a> — <em>A must read!!!</em></li><li><a href="https://blog.logrocket.com/next-js-vs-create-react-app/">Logrocket Blog</a> — <em>Details on really interesting stats</em></li><li><a href="https://codeburst.io/next-js-ssr-vs-create-react-app-csr-7452f71599f6">Codeburst Blog</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=157b4ad41e45" width="1" height="1" alt=""><hr><p><a href="https://medium.com/anitab-org-open-source/why-prefer-server-side-rendering-157b4ad41e45">Why prefer Server-Side Rendering?</a> was originally published in <a href="https://medium.com/anitab-org-open-source">AnitaB.org Open Source</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experimenting with Django]]></title>
            <link>https://medium.com/anitab-org-open-source/experimenting-with-django-f5bc4d563996?source=rss-2afb039aa001------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5bc4d563996</guid>
            <category><![CDATA[django]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[backend-development]]></category>
            <dc:creator><![CDATA[Bismita Guha]]></dc:creator>
            <pubDate>Tue, 28 Jul 2020 14:17:13 GMT</pubDate>
            <atom:updated>2020-07-28T14:17:13.215Z</atom:updated>
            <content:encoded><![CDATA[<p>Here, I am describing just a few interesting changes that can be done to reduce the code being written in views.</p><blockquote><strong>Generalising code</strong></blockquote><p>In my GSoC project, I had to implement <strong>create</strong> and <strong>list</strong> functions with multiple models and serializer. So I wrote easy functions, rather than complicating the code to include loops with conditional statements.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/85022f035356b63e8cca491f5a822c6d/href">https://medium.com/media/85022f035356b63e8cca491f5a822c6d/href</a></iframe><p>This is a file from my code, where I have returned a dictionary that has the model and serializer based on the data type passed in the function.</p><blockquote><strong>Related Name</strong></blockquote><p>Django related name might seem like not a necessary feature but it actually proves to be really helpful to access the models through reverse relations. You can find the details in this documentation:</p><p><a href="https://docs.djangoproject.com/en/dev/topics/db/queries/#following-relationships-backward">Making queries | Django documentation | Django</a></p><p>Now instead of making SQL queries to multiple tables which are related we can directly access them, in one line. For example look at this relation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/1*6rxJnvgq2n_yImfshrGF7g.png" /><figcaption>Many to Many Relation</figcaption></figure><p>Suppose we need to filter objects in the Answer model, based on some feature of the Form Feedback, i.e, <strong>user_id</strong> and <strong>form_id.</strong> The basic process would be first filtering the Form Feedback model, and retrieve the answers list and then make a query to the Answers model.</p><p>A simpler method, considering the related name of the answers (M2M) in the Form Feedback model is <strong>form_answers,</strong> will be:</p><pre>queryset = Answer.objects.filter(form_answers__form_id=form_id, form_answers__user_id=user.id)</pre><p>Not only one model, but this can be extended to multiple related models. So it’s just a <strong>double underscore</strong> which makes your job easier, and you can easily relate the queries.</p><p><em>Enjoy writing Django!!!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5bc4d563996" width="1" height="1" alt=""><hr><p><a href="https://medium.com/anitab-org-open-source/experimenting-with-django-f5bc4d563996">Experimenting with Django</a> was originally published in <a href="https://medium.com/anitab-org-open-source">AnitaB.org Open Source</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[More into Redux…]]></title>
            <link>https://medium.com/anitab-org-open-source/more-into-redux-e0b1f8e26867?source=rss-2afb039aa001------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0b1f8e26867</guid>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[redux]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Bismita Guha]]></dc:creator>
            <pubDate>Mon, 20 Jul 2020 20:28:11 GMT</pubDate>
            <atom:updated>2020-07-21T19:33:07.792Z</atom:updated>
            <content:encoded><![CDATA[<p>Redux is a standalone library that can be used with any UI layer or framework like, React, Angular, Vue and so on. If you are using Redux with any kind of UI framework, you will normally use a <strong>UI binding</strong> library to tie Redux together with your UI framework, rather than directly interacting with the store from your UI code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4ElLBnIT7PItm5TGawUBRQ.png" /></figure><blockquote>As for architecture, anecdotal evidence is that Redux works well for varying project and team sizes. Redux is currently used by hundreds of companies and thousands of developers, with several hundred thousand monthly installations from NPM.</blockquote><p>With Redux, the state of your application is kept in a store, and each component can access any state that it needs from this store.</p><p><a href="https://redux.js.org/">Redux - A JS library for predictable and maintainable global state management | Redux</a></p><blockquote><strong>Why need Redux or any State management tool</strong></blockquote><p>Redux was originally designed for use with React. Obviously now it can be used with multiple UI layers. As the React or Angular applications keep growing bigger, state management becomes tough without a separate tool; and handling them amidst various components gets difficult.</p><p>For example, it gets difficult when the children components are sharing states, it gets difficult to maintain and less predictable.</p><blockquote><strong>How Redux Works</strong></blockquote><p>There is a central store that holds the entire state of the application. Each component can access the stored state without having to send down props from one component to another. There are three building parts: actions, store, and reducers.</p><p><strong>Actions</strong></p><p>Actions are payloads of information that send data from your application to your store. They are the <em>only</em> source of information for the store. You send them to the store using store.dispatch(). Actions must have a type property that indicates the type of action being performed. Types should typically be defined as string constants.</p><p>Example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2fcb433a02b2c47aeeaab47c9719a2f4/href">https://medium.com/media/2fcb433a02b2c47aeeaab47c9719a2f4/href</a></iframe><p><strong>Reducers</strong></p><p>Reducers specify how the application’s state changes in response to <a href="https://redux.js.org/basics/actions">actions</a> sent to the store. A reducer is a pure function that takes in the initialState and the action.type and returns the next state. Reducers are just functions — you can organize them and subdivide them any way you want, and you are encouraged to break them down into smaller, reusable functions.</p><p>Example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cf6aa04bfa6b25d2af15ae804b2a2548/href">https://medium.com/media/cf6aa04bfa6b25d2af15ae804b2a2548/href</a></iframe><p>They do not change the data in the object passed to them or perform any side effects, API calls, or call non-pure functions in the application. Given the same object, they should always produce the same result.</p><p>Reducers can be defined in different files and then combined in index.js or any other proper approach which you feel. To return new state objects, instead of mutating the previous state, we can start with a single reducer, and as the app grows, split it off into smaller reducers that manage specific parts of the state tree.</p><p><strong>Store</strong></p><p>Store is the object that brings actions and reducers together. There is a single store in a Redux application. We used combineReducers() to combine several reducers into one. We will now import it, and pass it to <a href="https://redux.js.org/api/createstore">c</a>reateStore() .</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a485ddace141c96792574313022a2bcc/href">https://medium.com/media/a485ddace141c96792574313022a2bcc/href</a></iframe><p>The data flow in a Redux architecture is <strong>unidirectional</strong>.</p><p>The data lifecycle in any Redux app follows these 4 steps:</p><ul><li>You call <a href="https://redux.js.org/api/store#dispatchaction">store.dispatch(action)</a>.</li><li>The Redux store calls the reducer function you gave it.</li><li>The root reducer may combine the output of multiple reducers into a single state tree.</li><li>The Redux store saves the complete state tree returned by the root reducer.</li></ul><blockquote><strong>Something more…</strong></blockquote><p>For connecting our UI with APIs we need <strong>Asynchronous Actions. </strong>The standard way to do it in Redux is to use the <a href="https://github.com/gaearon/redux-thunk">Redux Thunk Middleware</a>. When an action creator returns a function, that function will get executed by the Redux Thunk middleware. To include the Redux Thunk middleware in the dispatch mechanism, we use the applyMiddleware() store enhancer from Redux. <strong>Middleware</strong> is some code you can put between the framework receiving a request, and the framework generating a response. Redux middleware creates a bridge between dispatching an action and the moment it reaches the reducer. People use Redux middleware for logging, crash reporting, talking to an asynchronous API, routing, and more. To connect with the React App you need to use connect and mapStateToProps , which needs to be defined as a function.</p><p><a href="https://react-redux.js.org/using-react-redux/connect-mapstate">Connect: Extracting Data with mapStateToProps | React Redux</a></p><p>In Redux:</p><ul><li><em>The global state of the application is stored in a single store in an object tree</em></li><li><em>The state can be changed only when an action is performed (or called), else it is read-only</em></li><li><em>The changes are handled by pure functions or reducers only</em></li></ul><blockquote><strong>References</strong></blockquote><p>These are very helpful in understanding state management and Redux workflow —</p><ul><li><a href="https://redux.js.org/">Redux Docs</a></li><li><a href="https://react-redux.js.org/">React Redux</a></li><li><a href="https://blog.logrocket.com/why-use-redux-reasons-with-clear-examples-d21bffd5835/">Redux Blog</a></li><li><a href="https://medium.com/swlh/the-case-for-flux-379b7d1982c6">The Case for Flux</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0b1f8e26867" width="1" height="1" alt=""><hr><p><a href="https://medium.com/anitab-org-open-source/more-into-redux-e0b1f8e26867">More into Redux…</a> was originally published in <a href="https://medium.com/anitab-org-open-source">AnitaB.org Open Source</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redux state management for different request methods]]></title>
            <link>https://medium.com/anitab-org-open-source/redux-state-management-for-different-request-methods-fc1f29a82d3a?source=rss-2afb039aa001------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc1f29a82d3a</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[redux]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Bismita Guha]]></dc:creator>
            <pubDate>Mon, 13 Jul 2020 15:00:21 GMT</pubDate>
            <atom:updated>2020-07-13T20:07:29.096Z</atom:updated>
            <content:encoded><![CDATA[<h4>Here I have described ways to manage state using redux for <strong>GET</strong>, <strong>POST</strong>, <strong>PATCH</strong> &amp; <strong>DELETE</strong></h4><p><strong>Redux</strong> is used for state management in JavaScript applications, which can be changed during the lifecycle of the application. It can be easily used with actions and reducers. So a basic problem which we might have observed in the basic stages of learning redux is that on adding an element to the backend of our application only the API for creating the object is called and the general list of objects still remains as it is. You need to make another call to the <strong>GET</strong> endpoint to retrieve the new list.</p><p>Making so many API calls doesn’t give efficient performance in your application, and also prevents a dynamic application. Here, by the simple use of reducers, we can handle the state while implementing different request methods.</p><p><a href="https://redux.js.org/">Redux - A JS library for predictable and maintainable global state management | Redux</a></p><p><em>Check out the official documentation of Redux for more insight…</em></p><blockquote><strong>Initial States</strong></blockquote><p>In every reducer, we pass the action to be performed and the initial state. So define an initial state for everything you need. For now you can use 2 states to understand the concept:</p><pre>const initialState = {<br>    list: [],<br>    postobject: []<br>}</pre><p>One for receiving the GET data, and another for creating a new object in the same list.</p><blockquote><strong>GET method</strong></blockquote><p>This is the simplest one.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/58f7c23517783b762cdaba45b2b204bd/href">https://medium.com/media/58f7c23517783b762cdaba45b2b204bd/href</a></iframe><p>You always need to define the default method like in every switch method.</p><blockquote><strong>POST method</strong></blockquote><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2162c1d64a57458043d92d7734ce904c/href">https://medium.com/media/2162c1d64a57458043d92d7734ce904c/href</a></iframe><p>comma is used to append. So action.payload gets appended to the previous state of list . Now without retrieving the new list, we have updated the frontend.</p><blockquote><strong>DELETE method</strong></blockquote><p>Now the object needs to be deleted from the list. So, we are actually sending the id of the object in the action.payload . We have to remove the object whose id is equal to action.payload .</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3597a5165abd13aa2701897c78dd426/href">https://medium.com/media/e3597a5165abd13aa2701897c78dd426/href</a></iframe><blockquote><strong>PATCH method</strong></blockquote><p>PATCH is kind of a combination of DELETE and POST methods. We have to remove the object which is getting updated and replace it with the action.payload , which contains the updated data.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/99619bc44c3f03dd9152dd9fa4d12c04/href">https://medium.com/media/99619bc44c3f03dd9152dd9fa4d12c04/href</a></iframe><p>First, we are removing the old object using it’s id , and then appending the new data to the list.</p><p>This simple implementation reduces much of the complicated code which might get involved. <em>Happy Developing!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc1f29a82d3a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/anitab-org-open-source/redux-state-management-for-different-request-methods-fc1f29a82d3a">Redux state management for different request methods</a> was originally published in <a href="https://medium.com/anitab-org-open-source">AnitaB.org Open Source</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working with multiple serializers]]></title>
            <link>https://medium.com/anitab-org-open-source/working-with-multiple-serializers-76858c07e50d?source=rss-2afb039aa001------2</link>
            <guid isPermaLink="false">https://medium.com/p/76858c07e50d</guid>
            <category><![CDATA[serializers]]></category>
            <category><![CDATA[django-rest-framework]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <dc:creator><![CDATA[Bismita Guha]]></dc:creator>
            <pubDate>Mon, 06 Jul 2020 14:22:32 GMT</pubDate>
            <atom:updated>2020-07-06T14:22:32.391Z</atom:updated>
            <content:encoded><![CDATA[<h4>This blog describes various ways to work with multiple serializers and multiple objects in the same view, using Django and Django REST Framework</h4><p>My major work in Week 5 of the GSoC Coding Phase involved working with multiple serializers in the same view. Many times, we need a queryset which includes objects from differents models, or a combination of different serializers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*9V_mG4LeY8XO71U4Tmg5_g.png" /><figcaption>An example from my project</figcaption></figure><blockquote><strong>List Serializers</strong></blockquote><p>Usually, we use POST requests to create a single object, and very rarely do we create a list of them. So if it’s a single model where we are creating a list of objects, bulk_create() would be useful in this case.</p><p><a href="https://docs.djangoproject.com/en/3.0/ref/models/querysets/#bulk-create">QuerySet API reference | Django documentation | Django</a></p><p>To get a REST API, we will need to serialize the JSON Response. Here’s when list serializers will come into use.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9ddb0bbe49794a134ca238741aaf79a0/href">https://medium.com/media/9ddb0bbe49794a134ca238741aaf79a0/href</a></iframe><p>Another option would be to do the following in the views.py :</p><pre>objs = Book.objects.bulk_create(results)<br>serializer = BookSerializer(objs, many=True)</pre><p>results will be a list of the objects to be created.</p><p><strong><em>TIP:</em></strong><em> You cannot use </em><em>bulk_create() on inherited models. It creates a discrepancy in the </em><em>id so it is not allowed.</em></p><blockquote><strong>Separating different lists</strong></blockquote><p>We can create a combination of querysets from different models in a single API.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f6be01854c0abfa2fde634b3cb5d97dc/href">https://medium.com/media/f6be01854c0abfa2fde634b3cb5d97dc/href</a></iframe><p>books and authors would be 2 separate lists containing respective data. We can extend this method to any number of serializer we want.</p><blockquote><strong>Combining different serializers into a single list</strong></blockquote><p>Now we do not want separate lists for different queryset, but an overall queryset for this purpose. Do something similar to this in your views.py:</p><pre>results = []</pre><pre>books = Books.objects.all()<br>authors = Author.objects.all()<br>results.append(BookSerializer(books, many=True).data)<br>results.append(AuthorSerializer(authors, many=True).data)</pre><pre>return Response(results, status=status.HTTP_200_OK)</pre><p>You define an empty list and go on appending objects to the list. Finally, you can return the list in your Response . You can use it within loops, or with conditional statements.</p><blockquote><strong>References</strong></blockquote><p>Have a look at the documentation for <strong>multiple create</strong> and <strong>multiple update</strong> for more details.</p><p><a href="https://www.django-rest-framework.org/api-guide/serializers/#customizing-multiple-create">Serializers</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76858c07e50d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/anitab-org-open-source/working-with-multiple-serializers-76858c07e50d">Working with multiple serializers</a> was originally published in <a href="https://medium.com/anitab-org-open-source">AnitaB.org Open Source</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Form validations in ReactJS]]></title>
            <link>https://medium.com/anitab-org-open-source/form-validations-in-reactjs-4838ce32bd83?source=rss-2afb039aa001------2</link>
            <guid isPermaLink="false">https://medium.com/p/4838ce32bd83</guid>
            <category><![CDATA[anitab-open-source]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Bismita Guha]]></dc:creator>
            <pubDate>Mon, 29 Jun 2020 14:41:55 GMT</pubDate>
            <atom:updated>2020-06-29T18:08:28.080Z</atom:updated>
            <content:encoded><![CDATA[<p>Completely relying on the backend for the entry of proper data into databases, is not the right practice. We should disallow the submission of data that does not fulfill the criteria for each entry. This reduces API calls to the backend server. This is called <strong>Client-side Validation</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*LA2dQpXGrixUFldIFzHc2g.png" /><figcaption>Sample from my GSoC project</figcaption></figure><p>Not only this but even after submission to the backend, some errors might arise which should also be displayed to the user for further correction or assistance. This is called <strong>Server-side Validation</strong>.</p><blockquote><strong>Possible Types of Validation</strong></blockquote><ul><li>Disallow empty submissions</li><li>Regex matching for fields <em>(like password, email etc.)</em></li><li>Length of Data submitted</li></ul><p>There can be other possible types of form validation too. I have just mentioned a few.</p><blockquote><strong>Implementation</strong></blockquote><p>Instead of a check on every field in a specific function, simpler methods to disallow empty data submission would be disabling the <strong>Submit</strong> button.</p><p>In your button component do the following:</p><pre>&lt;Button<br>    disabled={ !this.state.name || !this.state.email }<br>/&gt;</pre><p>Add all the required fields similarly. Also, ensure adding the required attribute to the field component also.</p><p>For specific fields like <strong>Password</strong> and <strong>Email</strong>, we need to ensure Regular Expressions (RegEx) for proper entry of data.</p><p>A sample regex for password will be:</p><pre>^(?=.*[a-z])(?=.*[A-Z])(?=.*\d)(?=.*[@$!%*?&amp;])[A-Za-z\d@$!%*?&amp;]{8,}$</pre><p>The first part (?=.*[a-z]) ensures a small letter, similarly second part ensures a capital letter, next a digit, next a special character, next any alphanumeric character, and the last one limits the minimum length of data to be 8. If we want a maximum limit then modify the expression to {8,32} , which means a minimum of 8 characters and a maximum of 32 characters allowed.</p><p>You can learn more about RegEx from here:</p><p><a href="https://regexone.com/">RegexOne - Learn Regular Expressions - Lesson 1: An Introduction, and the ABCs</a></p><p><em>…and there can be other ways to do the same.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4838ce32bd83" width="1" height="1" alt=""><hr><p><a href="https://medium.com/anitab-org-open-source/form-validations-in-reactjs-4838ce32bd83">Form validations in ReactJS</a> was originally published in <a href="https://medium.com/anitab-org-open-source">AnitaB.org Open Source</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Email confirmation process using Django and Sendgrid]]></title>
            <link>https://medium.com/anitab-org-open-source/gsoc20-coding-phase-week-3-9d084ea55bdc?source=rss-2afb039aa001------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d084ea55bdc</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[django-rest-framework]]></category>
            <category><![CDATA[sendgrid]]></category>
            <dc:creator><![CDATA[Bismita Guha]]></dc:creator>
            <pubDate>Mon, 22 Jun 2020 15:58:11 GMT</pubDate>
            <atom:updated>2020-06-27T14:38:49.213Z</atom:updated>
            <content:encoded><![CDATA[<h4>GSoC’20 | Coding Phase | Week 3</h4><p><strong>Email confirmation</strong> is a necessary part of proper authentication. It’s like a complete process for confirming user details. I have implemented this in my GSoC project which was my major work in the 3rd week of my Coding Phase.</p><p>I have used the <a href="https://sendgrid.com/">Sendgrid</a> email service for easy implementation with <a href="https://www.django-rest-framework.org/">Django REST Framework</a>. <strong>Sendgrid </strong>is a cloud-based email service that provides reliable transactional email delivery, scalability, and real-time analytics along with easy integration. The first step would be sending the email and the second step would be generating encoded tokens for email activation for specific users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VvPP0vawxiQimAFw1X-sZA.png" /></figure><h3><strong>Sending emails</strong></h3><p>A few changes to the settings.py and the views will easily send emails. First, we need to generate an API key for the app from <a href="https://app.sendgrid.com/settings/api_keys">this URL</a>. We need to add this API key to the .env file and then import this in settings.py for further use.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bafd61ebebcd9b9a9dcd287ec86a7594/href">https://medium.com/media/bafd61ebebcd9b9a9dcd287ec86a7594/href</a></iframe><p>We need to install python-dotenv for loading the environment variable. Next, make the following changes to settings.py:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d702df0e93d106f323f3be48822ee9a4/href">https://medium.com/media/d702df0e93d106f323f3be48822ee9a4/href</a></iframe><p>Next, we need to add a few lines to the views on the execution of which we want to send the email. Go to the specific function on the execution of which you want to send the email.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/97231a779a7f9fc07b7f5be4d78b7acd/href">https://medium.com/media/97231a779a7f9fc07b7f5be4d78b7acd/href</a></iframe><p>For testing, we can manipulate the settings.py to receive the output to the terminal instead of sending the email.</p><pre>SENDGRID_SANDBOX_MODE_IN_DEBUG = False<br>SENDGRID_ECHO_TO_STDOUT = True</pre><p><em>Next, we need to generate the token for email activation.</em></p><h3><strong>Token Generation</strong></h3><p>We need to generate a unique token for every user registering, to frame the URL for email activation. Write a token.py file for generating a unique token. You can obviously use other methods.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3b3e257b45c59e06635dee8d16ad2efe/href">https://medium.com/media/3b3e257b45c59e06635dee8d16ad2efe/href</a></iframe><p>In the URL generation part, these tokens need to be added:</p><pre>token1 = urlsafe_base64_encode(force_bytes(user.pk))<br>token2 = account_activation_token.make_token(user)</pre><pre># URL with token<br>http://your_domain_here/token1/token2</pre><p>You need to send this URL in the email being sent, with any other customized message you are willing to add. This token needs to be appended to the URL for activation. In the activate function we need to activate the user and return a response according to the validation of the URL, so that when the user clicks the URL in the email they received, they are redirected to a page that confirms their action and allows further login in the application.</p><p>views.py</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/eaf10630aef112d77e2efd962b6f8a59/href">https://medium.com/media/eaf10630aef112d77e2efd962b6f8a59/href</a></iframe><p>So, finally, this process isn’t as complicated as it looks. You can customize your email and also the email confirmation page, as per your design and creativity.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F14moZ7QNrGwAF2%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fwell-done-14moZ7QNrGwAF2&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2F14moZ7QNrGwAF2%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="320" frameborder="0" scrolling="no"><a href="https://medium.com/media/853f6d778ae7629f9d05e1c222c7e952/href">https://medium.com/media/853f6d778ae7629f9d05e1c222c7e952/href</a></iframe><p><em>Well done, you successfully integrated email confirmation in your application.</em></p><h3><strong>References</strong></h3><ul><li><a href="https://simpleit.rocks/python/django/adding-email-to-django-the-easiest-way/">Sendgrid Tutorial</a></li><li><a href="https://docs.microsoft.com/en-us/azure/sendgrid-dotnet-how-to-send-email">Microsoft Docs</a></li><li><a href="https://sendgrid.com/docs/for-developers/">Sendgrid Docs</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d084ea55bdc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/anitab-org-open-source/gsoc20-coding-phase-week-3-9d084ea55bdc">Email confirmation process using Django and Sendgrid</a> was originally published in <a href="https://medium.com/anitab-org-open-source">AnitaB.org Open Source</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>