<?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 Dara Olayebi on Medium]]></title>
        <description><![CDATA[Stories by Dara Olayebi on Medium]]></description>
        <link>https://medium.com/@DaraOlayebi?source=rss-242454fe7e12------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*C1cV135E5bb-eief7D7ixA.jpeg</url>
            <title>Stories by Dara Olayebi on Medium</title>
            <link>https://medium.com/@DaraOlayebi?source=rss-242454fe7e12------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:26:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@DaraOlayebi/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[A checklist for prioritising web accessibility]]></title>
            <link>https://uxdesign.cc/a-checklist-for-prioritising-web-accessibility-2c80c51ca659?source=rss-242454fe7e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c80c51ca659</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Dara Olayebi]]></dc:creator>
            <pubDate>Mon, 12 Sep 2022 15:51:00 GMT</pubDate>
            <atom:updated>2022-09-16T12:19:08.807Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bHUycyTt76gTLDfEcu-vlw.png" /></figure><p>In the spirit of being transparent, I haven’t always prioritised accessibility. This is not to say that I’ve deliberately built applications to be inaccessible, but rather, that it was often an afterthought — something I needed to “tackle” at the very end. Because of this, I never spent enough time making sure all parts of the user interface were <strong>accessible</strong>. Over time, I have realised how important it is to make it a natural part of my development process from the jump.</p><p>In a nutshell, accessibility on the web refers to the ability for <strong>everyone </strong>to successfully perceive, operate, understand and access a website or web application. People with disabilities use assistive technologies — screen readers, screen magnifiers, Braille displays, voice control, to name a few — to access the web.</p><figure><img alt="Different categories of permanent, temporary and situational disabilities" src="https://cdn-images-1.medium.com/max/1024/1*MhzOMlT3fxU1BD9xsLdwhg.png" /><figcaption>Different categories of disabilities (source: Microsoft’s inclusive design kit)</figcaption></figure><p>Before diving in, we’ll go behind the scenes a little bit. When a browser loads a webpage, a couple of things happen. One of those things is the creation of what is called the <strong>Accessibility Tree</strong> — the browser takes the DOM tree and transforms it into a version that assistive technologies can understand. The Accessibility Tree consists of the name, role, value and state (along with other properties) of elements on a webpage. Technologies such as screen readers will refer to this tree to relay information to its users.</p><figure><img alt="Chrome’s Accessibility Tree (within Developer tools) showing the accessibility data for a button on the webpage" src="https://cdn-images-1.medium.com/max/1024/1*wOR2lW5HyY5lzGicaCgT-w.png" /><figcaption><em>Chrome’s Accessibility Tree (within Developer tools) showing the accessibility data for a button</em></figcaption></figure><p>To ensure website developers stick to accessibility rules, the <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/Understanding_WCAG">WCAG</a> (Web Content Accessibility Guidelines) were introduced many years ago. This article highlights some of these guidelines in a checklist format that can be easily followed.</p><h3>✔️ Are you using semantic HTML?</h3><p>By default, <a href="https://motherfuckingwebsite.com/">HTML is accessible</a>. However, the more elaborate a website becomes — as is the case nowadays — the greater the need to ensure that it remains accessible. Using semantic HTML sets the foundation.</p><p>Semantic elements (header, footer, main, aside, article, button, nav, menu cite, em, to name a few) introduce meaning to a webpage which means that assistive technologies are able to establish landmark regions and identify what the layout and sections of the page are.</p><blockquote>“Developing semantic websites solves more than 50% of the most common accessibility issues.” — Leonardo Graterol</blockquote><figure><img alt="Comparison between semantic and non-semantic code" src="https://cdn-images-1.medium.com/max/1024/1*TniA1RQHQpl62SRG0_Mz9Q.png" /><figcaption><em>Semantic vs Non-semantic code</em></figcaption></figure><p>In some cases, there might be no semantic element in existence for what needs to be achieved — for example, building a dropdown menu. The alternative would be to create a custom, non-semantic component which has the potential to affect accessibility. This is where ARIA comes in (discussed later on).</p><p>More on semantics: <a href="https://learn-the-web.algonquindesign.ca/topics/html-semantics-cheat-sheet/">HTML semantics cheat sheet</a>.</p><h3>✔️ Does every element have a name?</h3><p>Just as people are addressed by name, so are web elements when it comes to accessibility. The name of an element (also called “accessible name”) is one of the values that screen readers will announce to users as they navigate a website.</p><p>Elements get their default accessible names from different sources:</p><ul><li>Image names come from the alt attribute.</li><li>Button names come from the button’s text contents (or from the alt value of an enclosing image, if one exists).</li><li>Table names come from the title attribute.</li><li>Form input names come from the placeholder, associated label or title attribute.</li></ul><p>Here are some examples of three web elements followed by a screenshot of the MacOS screen reader announcement of each element:</p><pre>&lt;button class=&quot;button&quot;&gt;Settings&lt;/button&gt;</pre><figure><img alt="Screen reader announcing a link on a webpage as “Settings, button”" src="https://cdn-images-1.medium.com/max/880/0*iDOI8YG1xq8E2K5S.png" /><figcaption><em>Screen reader announcement for a button</em></figcaption></figure><pre>&lt;a href=&quot;/settings/labels&quot;&gt;Manage Labels&lt;/a&gt; </pre><figure><img alt="Screen reader announcing a link on a webpage as “link, Manage Labels”" src="https://cdn-images-1.medium.com/max/880/0*ZnE3GZ84T1Ab6k8R.png" /><figcaption><em>Screen reader announcement for a link</em></figcaption></figure><pre>&lt;form role=&quot;search&quot;&gt;<br>   &lt;label for=&quot;q&quot;&gt;Search:&lt;/label&gt;<br>   &lt;input type=&quot;text&quot; id=&quot;q&quot; name=&quot;q&quot; /&gt;<br>&lt;/form&gt;</pre><figure><img alt="Screen reader announcing a search form on a webpage as “Search, menu pop-up, edit text, search”" src="https://cdn-images-1.medium.com/max/880/0*hEUNSywkmgybKMbR.png" /><figcaption><em>Screen reader announcement for a form with a search field</em></figcaption></figure><p>Sometimes, an element needs to be explicitly given its accessible name. Here are two example scenarios:</p><ul><li>A “Read more” link that requires additional context for visually impaired users</li><li>Icon buttons that have no text</li></ul><figure><img alt="A group of icon buttons that have no text" src="https://cdn-images-1.medium.com/max/880/0*0PPKaA_H3dIOWRu7.png" /><figcaption>Icon buttons without text</figcaption></figure><p>ARIA to the rescue!</p><p>If you scroll up to the screenshot of Chrome’s Accessibility Tree at the beginning of the article, you’ll notice the section titled “ARIA attributes”.</p><blockquote><strong><em>ARIA (Accessible Rich Internet Applications) is a set of roles, states and properties that can be added to an element to specify how it should behave.</em></strong></blockquote><p>The aria-label attribute will override an element&#39;s accessible name.</p><pre>// The buttons below get their accessible names from the aria-label attribute</pre><pre>&lt;button class=&quot;button&quot; aria-label=&quot;Shopping Cart&quot;&gt;<br>  &lt;svg&gt;...&lt;/svg&gt;<br>&lt;/button&gt;</pre><pre><br>&lt;button aria-label=&quot;Read more about article on global travel&quot;&gt;<br>   Read more<br>&lt;/button&gt;</pre><p>Key things to note:</p><ul><li>All images should have an alt attribute.</li><li>If the image is purely decorative (e.g. a question mark icon next to a Help button or a magnifying glass icon within a search input), the alt text should be an empty string (this prevents screen readers from announcing a redundant element).</li><li>If the image is not redundant and serves a purpose, the alt text should describe exactly <strong>what the image is</strong> or in some cases, <strong>what the image does</strong>.</li><li>All HTML form inputs should have an associated descriptive label to enhance accessibility.</li></ul><p>So it’s pretty obvious that an element with no name could affect a user’s experience. Examining the Accessibility Tree to make sure elements have proper naming will increase the amount of context screen readers provide to users.</p><p>More on accessible names: <a href="https://sarahmhigley.com/writing/whats-in-a-name/">What’s in a name?</a></p><h3>✔️ Are headings in hierarchical order?</h3><p>Some assistive technology users prefer to navigate a page using headings, especially on sites that have a lot of content, for example Wikipedia. Headings should have the correct hierarchy (i.e. &lt;h3&gt; must come before &lt;h4&gt;) to give users a sense of how the page content is structured.</p><p>Headings should also be as succinct and as descriptive as possible to properly illustrate the content they introduce.</p><blockquote>The heading elements should be organized in descending order without skipping a level, meaning that an h4 should only come after an h3. Skipping heading levels will cause screen reader users to wonder if content is missing — WCAG</blockquote><p>It can be tempting to order headings by size and not by level. In such cases, CSS utility classes can be used to make elements appear visually smaller or bigger regardless of their heading level.</p><p>More on headings hierarchy: <a href="https://www.a11yproject.com/posts/how-to-accessible-heading-structure/">Accessible heading structure</a></p><h3>✔️ Does your content have a logical tab order and visible focus indicators?</h3><p>Not all users make use of a mouse or a trackpad. Some have to rely on the keyboard, while others choose to. Regardless, ensuring that this group of users can successfully navigate a webpage should be a priority.</p><p>HTML elements are either presentational (div, span, section, article) or interactive (a, button, input, select, textarea). By default, interactive elements are focusable. A keyboard user will click the tab key to jump from one focusable element to the next.</p><p>The order in which users tab through the page is based on the order of the DOM, and the order of the DOM is based on the order of the HTML markup. Therefore, it is important to prioritise how you write your code as it will determine how keyboard users navigate your site. For example, if your UI is supposed to display article content to the left and the article heading to the right, your HTML should be written in the normal order with the article heading appearing first and the article content second. CSS can then be used to adjust the visual appearance of the page.</p><p>The page tab order can also be altered using tabindex — this attribute determines where an element will fall in the tab flow. The default tabindex value of interactive elements is 0. An element given a value of -1 will be removed from the tab flow, while an element given a value of 1 will take precedence over other elements. The latter should be avoided as it could affect the user&#39;s navigation flow on the page.</p><pre>&lt;div tabindex=&quot;1&quot;&gt;I will be focused before all other elements&lt;/div&gt;</pre><pre>&lt;div tabindex=&quot;0&quot;&gt;I am the default&lt;/div&gt;</pre><pre>&lt;div tabindex=&quot;-1&quot;&gt;I will never be in focus&lt;/div&gt;</pre><p>Key things to note:</p><ul><li>Make sure any element that the user needs to interact with, particularly custom controls like a dropdown menu, have a tabindex value of 0. Otherwise, a keyboard user will never be able to access it.</li><li>If an element is visually hidden but may be interacted with at some point by the user (e.g. a pop-up modal), it should be set to display: none or visibility: hidden to prevent focus until it becomes visible.</li><li>If an element is visually hidden and will never involve any interaction from the user, it should be given a tabindex value of -1 to remove it from the focus flow entirely.</li><li>When used for interactive controls, non-semantic elements are inaccessible via the keyboard (e.g. using a &lt;div&gt; to create a button) and will require some Javascript to be written to be made accessible. Semantic elements on the other hand have built-in keyboard accessibility.</li></ul><p>So how does a keyboard user know what element is in focus while they tab through the page?</p><p>As <a href="https://www.sarasoueidan.com/blog/focus-indicators/#:~:text=%20a%20keyboard%20user%E2%80%99s%20cursor%20equivalent%20is%20the%20focus%20indicator.">Sara Soueidan wrote</a>:</p><blockquote>A keyboard user’s cursor equivalent is the focus indicator.</blockquote><p>Removing the browsers default focus indicator (using outline: none) without replacing it with another one makes a site inaccessible. Today, in addition to :focus, most browsers support the :focus-visible pseudo-class which will be applied when an element is in focus and the user&#39;s input is a keyboard.</p><figure><img alt="A screenshot of a website showing the focus indicator ring around one of the menu items during  keyboard navigation" src="https://cdn-images-1.medium.com/max/880/0*HGg-nptmuo7u0yNn.png" /><figcaption><em>The focus indicator is displayed on the “Paid Courses” menu item via a keyboard</em></figcaption></figure><p>Here’s how to use :focus-visible from MDN&#39;s docs:</p><pre>.button {<br>  margin: 10px;<br>  border: 2px solid darkgray;<br>  border-radius: 4px;<br>}</pre><pre>.button:focus-visible {<br>  /* Draw the focus when :focus-visible is supported */<br>  outline: 3px solid deepskyblue;<br>  outline-offset: 3px;<br>}</pre><pre>@supports not selector(:focus-visible) {<br>  .button.with-fallback:focus {<br>    /* Fallback for browsers without :focus-visible support */<br>    outline: 3px solid deepskyblue;<br>    outline-offset: 3px;<br>  }<br>}</pre><p>More on focus indicators:</p><ul><li><a href="https://www.sarasoueidan.com/blog/focus-indicators/">A guide to designing accessible, WCAG-compliant focus indicators</a></li><li><a href="https://www.w3.org/TR/WCAG22/#focus-appearance">WCAG guidelines on focus indicators</a></li></ul><h3>✔️ Are you using ARIA appropriately?</h3><p>As we saw above, ARIA lets you modify the way an element is presented to assistive technologies.</p><p>You can use ARIA to define the role of an element e.g. role=&quot;dialog&quot;, or set its state e.g. aria-checked=&quot;true&quot;. You can also use it to make custom controls accessible. For example, if you choose to create a checkbox instead of using HTML&#39;s native checkbox element, you would need to add ARIA states and properties to make your checkbox usable and accessible.</p><p>As useful as ARIA is however, it is not always required. Semantic markup should always be used where possible.</p><p>More on ARIA: <a href="https://gomakethings.com/when-should-you-use-aria/">When should you use ARIA</a></p><h3>✔️ Are you letting users know when dynamic content changes?</h3><p>Imagine a visually impaired user sending messages on a website’s customer service chat widget but not being made aware whenever they receive a response?</p><p>If you have any time sensitive notifications on your website that are vital to a user’s experience, you should explore using aria-live. This attribute can be added to any element and allows website developers determine how screen readers should notify users about changes on a webpage.</p><ul><li>aria-live=&quot;off&quot;: No announcements will be made (&quot;off&quot; is the default).</li><li>aria-live=&quot;polite&quot;: Announcements will be made only after a user has completed a process i.e. the user will not be interrupted.</li><li>aria-live=&quot;assertive&quot;: The user will be interrupted so the announcement can be made.</li></ul><h3>✔️ Are you choosing colours carefully?</h3><p>Very often, when it comes to colours, I have prioritised aesthetics over accessibility without realising it, neglecting a large group of people in the process.</p><p>With more awareness comes more consideration for users who are blind or have low vision. This means prioritising the following:</p><ul><li>Making sure all text has the right amount of contrast with its background. WCAG expects a website’s background to text contrast ratio to be at least <a href="https://www.w3.org/TR/WCAG21/#contrast-minimum:~:text=The%20visual%20presentation%20of%20text%20and%20images%20of%20text%20has%20a%20contrast%20ratio%20of%20at%20least%204.5%3A1">4.5:1</a>.</li></ul><figure><img alt="A screenshot of Chrome’s colour contrast tool showing the contrast ratio of two different colours" src="https://cdn-images-1.medium.com/max/880/0*wbWEmNgc4MVsHkG_.png" /><figcaption><em>Chrome’s colour contrast tool which shows selected colours pass (left) and fail (right) contrast ratio check</em></figcaption></figure><ul><li>Including text alternatives to depict different coloured interactive states. For example, error, success or warning states.</li><li>Using focus indicators that have enough contrast with the surrounding element or background.</li><li>Although this is unrelated to colour, it’s important to also take into account other UI elements like font sizes, line heights and letter spacing, and consider how well content can be perceived on a website.</li></ul><p>More on colour: <a href="https://uxmovement.com/content/why-you-should-never-use-pure-black-for-text-or-backgrounds/">Here’s why you should never use pure black for text or backgrounds</a>.</p><p>Web accessibility is a much broader topic than this article covers. However, as I started to prioritise it in all the ways mentioned above, it led to a major shift in my perspective, motivated me to re-evaluate the way I build user interfaces, and is ultimately making me a more thoughtful developer.</p><p><strong>Helpful resources:</strong></p><ul><li><a href="https://aneventapart.com/news/post/practical-tips-for-building-more-accessible-front-ends">Practical tips for building more accessible front-ends</a></li><li><a href="https://www.a11yproject.com/">The A11y Project</a></li><li><a href="https://gomakethings.com/hidden-content-for-better-a11y/">Hidden content for better a11y</a></li><li><a href="https://a11y-101.com/development/skip-link">Skip links</a></li><li><a href="https://github.com/pa11y/pa11y">Pa11y — automated accessibility testing tool</a></li><li><a href="https://www.codehousegroup.com/insight-and-inspiration/tech-stream/google-lighthouse-accessibility">Google Lighthouse</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c80c51ca659" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/a-checklist-for-prioritising-web-accessibility-2c80c51ca659">A checklist for prioritising web accessibility</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everything I learnt building my first DApp — a frontend perspective]]></title>
            <link>https://coinsbench.com/everything-i-learnt-building-my-first-dapp-a-frontend-perspective-ba810be1493f?source=rss-242454fe7e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba810be1493f</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[Dara Olayebi]]></dc:creator>
            <pubDate>Sat, 09 Apr 2022 11:51:32 GMT</pubDate>
            <atom:updated>2022-07-20T09:52:17.066Z</atom:updated>
            <content:encoded><![CDATA[<h3>Everything I learned building my first DApp — a frontend perspective</h3><h4><em>This article is a walkthrough of my process and learnings of building a DApp using React, WAGMI &amp; ethers.js.</em></h4><p>I was recently given a task at work to build the client side of a DApp (decentralized application). I watched a number of tutorials but still had a hard time figuring out why I needed certain libraries / services and more importantly, how to put all the various pieces together. If you’re trying to figure this out too, then keep reading!</p><p>The frontend of a DApp is built very similarly to a traditional web application (using a mix of HTML, CSS &amp; JavaScript), but instead of interacting with a database via an API, you’re interacting directly with the blockchain via a smart contract (a program written to execute a set of instructions). In order to be fully decentralised, DApps are also often hosted on peer-to-peer (P2P) networks instead of centralised hosting servers.</p><p><strong>Traditional web application:</strong> Client → API → Database<br><strong>Decentralised application:</strong> Client → Smart Contract → Blockchain</p><p>Here’s how it went!</p><h3>Setting up the DApp</h3><p>After initialising a new React project, the first thing I did was to install a package that will enable communication with the blockchain. Two of the most widely-used Javascript libraries for this are <a href="https://web3js.readthedocs.io/">Web3.js</a> and <a href="https://docs.ethers.io/v5/">Ethers.js</a>. I did some digging to understand how they work under the hood.</p><p>The blockchain is made up of many nodes, each of which stores a copy of the data on the blockchain. To read or write any of this data, my application needed to be able to communicate with one of these nodes. These libraries provide developers with access to various modules (with methods and properties) for interacting with a local or remote Ethereum node. For example:</p><p>ethers.Wallet is used to connect to an Ethereum wallet.<br>ethers.Contractis used to interact with a smart contract on the Ethereum blockchain.</p><p>Both libraries will allow you to achieve the same things. However, if you’re unsure about which one to use, <a href="https://blog.infura.io/ethereum-javascript-libraries-web3-js-vs-ethers-js-part-i/">this article</a> does a good comparison study.</p><p>I also needed a crypto wallet. A wallet acts as a login / gateway to a DApp. In traditional web applications, users are prompted to sign in with an email address and a password. In the decentralised world, DApps need to be given permission to access a user’s wallet in order to enable certain functionality (more on this later). I installed <a href="https://metamask.io/">Metamask</a> which is one of the most popular wallet solutions, and is accessible via a <a href="https://chrome.google.com/webstore/detail/metamask/nkbihfbeogaeaoehlefnkodbefgpgknn">Chrome extension</a> or a mobile app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*0zwEpkVn6IGvErpn.jpg" /></figure><p>Once I had both ethers.js and Metamask installed, I was good to go.</p><h3>Interacting with the smart contract</h3><p>I had what I needed to communicate with the blockchain. Next, I needed to figure out how to interact with the “middleman” — the smart contract.</p><p>Connecting to a smart contract requires you to have:</p><ul><li>The contract address</li><li>The contract ABI</li><li>A provider and/or a signer</li></ul><p>The contract address is the address of the contract on the blockchain. The ABI (Application Binary Interface) is a file that contains a breakdown of each function in the contract along with its input parameters (if any), expected output and data types, in JSON format. Both of these can be found on <a href="https://etherscan.io/">Etherscan</a>, a blockchain explorer for Ethereum that allows you to view smart contracts (plus much more).</p><p>Providers and signers are essential parts of a DApp. A smart contract can consist of both read and write functions. To read data from a smart contract, you require a provider. To write data (i.e. perform transactions that will change the state of the data on the blockchain), you require a signer. To do both, you require a signer that has a provider.</p><p>A provider provides (pun intended) a link to an Ethereum node that your application will communicate with. There are multiple third party services that offer node providers so you don’t have to run your own local node. Some of them are Infura, Metamask (uses Infura under the hood), Quicknode and Alchemy.</p><p>I got started with <a href="https://infura.io/">Infura</a>, created an account and got a Project ID in a few minutes. I was able to create a provider using the built-in Infura provider option on Ethers.js:</p><pre>const provider = new ethers.providers.InfuraProvider(&#39;rinkeby&#39;, INFURA_PROJECT_ID);</pre><p>Signers on the other hand are essentially an abstraction of the user’s wallet address. If you are performing any write operation to the blockchain, you will need to sign the transaction (i.e. prove that you are who you are).</p><p>Finally, I created a contract instance that will be used across the application, passing in the contract address, ABI and signer.</p><pre>const contract = new ethers.Contract(CONTRACT_ADDRESS, CONTRACT_ABI, provider or signer);</pre><p>With this done, I could call any smart contract function like this:</p><pre>const result = await contract.functionName();</pre><h3>Handling the wallet connection</h3><p>The final bit was to figure out how to handle connecting the DApp to a wallet.</p><p>In addition to Metamask, my application was to provide users with two other wallet connector options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*HPJ01acjjTTWlPq6.jpg" /></figure><p>Fortunately, there are several packages that remove the need to write code for each connector separately. I used <a href="https://wagmi.sh/">WAGMI</a> which is a React hooks library built on top of ethers.js. WAGMI does a lot more than just handle wallets. It uses over 20 different hooks to abstract a lot of the ethers.js functionality.</p><p>This <a href="https://wagmi.sh/guides/connect-wallet">guide</a> on their website explains in detail how to configure wallets. I found it really easy to integrate. Other similar libraries include web3-react and web3-modal.</p><p>One important thing to note: Wallets come with a number of networks you can select from.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/0*xcgycJR80juK8JIh.png" /></figure><p>There is the main network (Ethereum mainnet) which is for production purposes and multiple test networks (Ethereum testnets) that replicate the Ethereum production environment and are used to develop and test smart contracts. Each testnet has its own properties and supports a specific set of clients.</p><p>It’s also important to make sure that your wallet is on the same network your smart contract is deployed on, otherwise, requests will fail. I used WAGMI’s useNetwork hook to check when the user is on the wrong network.</p><p>Other things worth mentioning:</p><ul><li>To fund your wallet with test tokens (particularly to test write functions as they incur gas fees), you will need to use a faucet — a website that distributes small amounts of crypto for free. I used <a href="https://faucet.rinkeby.io/">Rinkeby’s faucet</a> and got some test ETH within minutes. However, other options are <a href="https://faucets.chain.link/rinkeby">Chainlink’s faucet</a> and <a href="https://app.mycrypto.com/faucet">MyCrypto</a>.</li><li>It’s extremely important to pass each contract function the correct data in the expected data type. Otherwise, you might end up paying an exorbitant amount in gas fees due to an input error. Thankfully, Metamask warns you when your transaction is likely to fail.</li><li>If your application needs to display a list of tokens (with their meta information, current prices etc), I would recommend <a href="https://www.coingecko.com/en/api/documentation">Coingecko’s API</a> which is what I used.</li></ul><p>Helpful resources:</p><ul><li><a href="https://mirror.xyz/dhaiwat.eth/O5CK6Tjfv8uhl6FPbjT0yZ8LUwViDPWGYHdu9khRWpM">A guide to Web3 for Web2 Frontend Developers</a></li><li><a href="https://bitsofco.de/calling-smart-contract-functions-using-web3-js-call-vs-send/">Understanding how to call different smart contract functions</a></li><li><a href="https://dev.to/edatweets_/intro-to-dapps-create-your-dapp-frontend-wreact-38fi">Create your DApp frontend with React</a></li><li><a href="https://dev.to/nazeeh21/integrate-your-react-app-with-smart-contracts-4o3m">Integrate a smart contract into your React app</a></li></ul><p>Please feel free to reach out if you have any questions, comments or notice any errors.</p><p>Also, here’s to finally publishing my first tech article! 🥂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba810be1493f" width="1" height="1" alt=""><hr><p><a href="https://coinsbench.com/everything-i-learnt-building-my-first-dapp-a-frontend-perspective-ba810be1493f">Everything I learnt building my first DApp — a frontend perspective</a> was originally published in <a href="https://coinsbench.com/">CoinsBench</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Surviving 2020]]></title>
            <link>https://medium.com/@DaraOlayebi/surviving-2020-8bc7de898cba?source=rss-242454fe7e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bc7de898cba</guid>
            <category><![CDATA[2020]]></category>
            <category><![CDATA[surviving2020]]></category>
            <dc:creator><![CDATA[Dara Olayebi]]></dc:creator>
            <pubDate>Mon, 20 Jul 2020 21:08:16 GMT</pubDate>
            <atom:updated>2020-07-20T21:12:30.232Z</atom:updated>
            <content:encoded><![CDATA[<p>This year has been one hell of a ride.</p><p>It’s been unusual, unpredictable, disconcerting … plus a hundred other adjectives that come to mind. And we’re only halfway through. If you’re reading this and you’ve been feeling overwhelmed about the future, then you’re in good company.</p><p>For the first time in many of our lives, the entire world faces a collective uncertainty that, to varying degrees, overshadows everything that we do day-to-day. The terms “lockdown”, “quarantine” and “social distancing” are this year’s buzzwords (and probably the next), and unfortunately, it feels like there’s bad news on every corner.</p><p>With all that’s going on, it’s been a struggle to see that famous “light at the end of the tunnel” and I slowly started to shift my focus to 2021, in the hopes that it will be better. However, in an effort to treasure the good in the present moment, and in a bid to stay positive, I decided to create my own “light”, mid-tunnel — something that would serve as a reference for right now, and for the months and years to come.</p><p>And so, <a href="https://www.our2020stories.com/">Surviving 2020</a> was born.</p><p><a href="https://www.our2020stories.com/">Surviving 2020</a> is a web project that was built to connect people through stories and shared experiences. It is a virtual invitation to document significant moments of your year in a few sentences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eZWkvnheukfwnWT0bCDIwg.png" /></figure><p>First, you select one of four phrases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TiPTNaH8Hjq3Pw4qf9KXJA.png" /></figure><p>Then you enter a response based on your selection. Once you submit, your statement will appear on the Stories page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_mjcnSU1XjkEjkmOVNgK2w.png" /></figure><p>For me:</p><p><strong>My 2020 has been</strong> nothing short of significant.</p><p><strong>During self isolation, I</strong> began to understand what the truly important things in my life are. And also started learning French!</p><p><strong>In this season, I have learnt</strong> how to handle uncertainty with faith.</p><p><strong>After the pandemic, I will</strong> (hopefully) travel to the country at the top of my bucket list at the moment — Greece.</p><p>The pandemic has changed the way I think about life and has brought with it so many lessons that I didn’t know I needed. In summary, the phrase “Carpe diem” has never been more relevant. I built this project with the hope that it will bring you some level of peace, knowing that you are not alone, and your worries, confusion, grief, fear, and any other emotion you might be feeling are felt by so many others.</p><p>I hope you enjoy the experience of reading other people’s stories, and <a href="https://www.our2020stories.com/">sharing yours</a> as much as I enjoyed working on this project!</p><p>Here’s to surviving this crazy year together!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bc7de898cba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[If I could be the woman of my dreams, who would I be?]]></title>
            <link>https://medium.com/@DaraOlayebi/if-i-could-be-the-woman-of-my-dreams-who-would-i-be-e7ba07f94eb8?source=rss-242454fe7e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7ba07f94eb8</guid>
            <category><![CDATA[women]]></category>
            <category><![CDATA[michelle-obama]]></category>
            <category><![CDATA[oprah-winfrey]]></category>
            <category><![CDATA[future]]></category>
            <category><![CDATA[maya-angelou]]></category>
            <dc:creator><![CDATA[Dara Olayebi]]></dc:creator>
            <pubDate>Fri, 25 Aug 2017 21:01:32 GMT</pubDate>
            <atom:updated>2017-08-28T11:08:44.312Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*vbTd5hL2u8q3NefxJiUA8Q.jpeg" /></figure><p>When I think ‘my dream woman’, three people immediately pop into my head - the number one woman figure in my life, my mum, Oprah Winfrey and Michelle Obama. Others also spring to mind - Maya Angelou, Emma Watson, Serena Williams. But I’ve realised that it’s really not enough for me to just see these women as role models. So I decided to dig a little deeper. What particular traits did I admire? What about their characters stood out for me? Only upon answering these questions was I then able to look completely inwards, see where I could improve, see where my potential lay and finally begin working towards becoming this woman whose shoes I pray to one day be wearing.</p><p><strong>If I could be the woman of my dreams …</strong></p><p>I would be more aggressive with my ambitions. I like to consider myself a go-getter but sometimes I tend to become slack and procrastinate. My dream woman has constant fire in her and doesn’t let life or people bring her down. Her focus is on her future, her vision is clear as day, and she lives life fearlessly and with purpose.</p><p><strong>If I could be the woman of my dreams …</strong></p><p>I would be an example and a source of inspiration to all the young people around me, always willing to teach, mentor and encourage. My dream woman knows that she’s far from perfect but at the same time is a leader in her field and is able to inspire and influence.</p><p><strong>If I could be the woman of my dreams …</strong></p><p>I would be more giving - it will be second nature to me. I want my empathy to stop being so short-lived. I want to see a problem in society and immediately work towards a solution. My dream woman is able to make a difference and enrich people’s lives. She has learnt how to be sacrificial. She knows how to step away from herself and put others first.</p><p><strong>If I could be the woman of my dreams …</strong></p><p>I would be stronger. Not stronger physically but stronger in character. My dream woman has a mind of her own and is not too concerned with the affairs or opinions of other people. She is able to speak up for herself and her voice resonates whenever she does. She is not fazed by challenges and always holds her head high.</p><p><strong>If I could be the woman of my dreams …</strong></p><p>I would be a Proverbs 31 woman - “she sets about her work vigorously; she opens her arms to the poor and extends her hands to the needy; she is clothed with strength and dignity; she can laugh at the days to come; she speaks with wisdom and faithful instruction is on her tongue.” My dream woman holds onto God so tight and acknowledges Him every single day, in every single moment.</p><p>My dream woman is a powerhouse.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7ba07f94eb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons from Adam Braun]]></title>
            <link>https://medium.com/@DaraOlayebi/lessons-from-adam-braun-d38f72fe3dbb?source=rss-242454fe7e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/d38f72fe3dbb</guid>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[nonprofit]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[tedtalks]]></category>
            <dc:creator><![CDATA[Dara Olayebi]]></dc:creator>
            <pubDate>Fri, 17 Feb 2017 20:01:56 GMT</pubDate>
            <atom:updated>2017-02-17T20:56:46.795Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*n3KrHLxx56IG4WK5day7Ww.jpeg" /></figure><p>One of my favourite TED Talks is by a guy called Adam Braun, who started the organisation Pencils of Promise. In his talk, he told the story of how he travelled round different countries, and in each one, he would ask one child “if you could have anything, what would it be?” On one occasion, one child answered “a pencil”, and after a series of realisations, Adam’s organisation was born. Today, he has built almost 400 schools around the world.</p><p>I loved his talk mostly because I am passionate about education for the young and less privileged. But then beyond that, his talk gave me some life lessons that always make me feel ten times more motivated whenever I come across them. So I put them together in this post, in the hopes that it’ll inspire you as much as it did me:</p><ol><li>Know and believe that you are on this earth to serve a unique purpose and that you are different. Your time is right now.</li><li>Make your life a story worth telling. Become the story that will inspire your generation.</li><li>Get out of your comfort zone and aim to be uncomfortable. Immerse yourself in something new that challenges everything you’ve ever believed.</li><li>Speak the language of the person that you seek to become.</li><li>Big dreams start with small unreasonable acts.</li><li>Each person is a revolution being carried within a vessel. Believe that you actually do have the capability to change the world.</li><li>Ask yourself, with the knowledge that the world will change in the next 10 years and you will change within it, how can you create the most positive impact for as many lives as possible?</li><li>Find your purpose and activate it.</li></ol><p>Here’s his <a href="https://www.youtube.com/watch?v=Z8oE2kqVXkk">TED Talk</a> if you’d like to watch it. It’s titled “The Five Phrases That Will Change Your Life”, although I definitely took away more than 5 phrases!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d38f72fe3dbb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2016.]]></title>
            <link>https://medium.com/@DaraOlayebi/2016-1320229155c0?source=rss-242454fe7e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/1320229155c0</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[graduation]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Dara Olayebi]]></dc:creator>
            <pubDate>Sat, 31 Dec 2016 10:34:19 GMT</pubDate>
            <atom:updated>2017-01-03T09:25:02.201Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*0fnIvpctgAxMLywTPYxt3Q.jpeg" /></figure><p>2016 was my most significant year yet, mostly because I hit a few important milestones — I graduated from university, turned 21, and got my first proper job. It was also my most significant year yet because for the first time in my life, I didn’t know what was coming next. I had always been so sure of my next steps, next venture, the next phase of my life. This time however, my vision was unclear and I had absolutely no clue what career path I wanted to follow.</p><p><strong>I eventually learnt that it is perfectly okay to be confused.</strong></p><p>I struggled so much with accepting this and put a lot of pressure on myself because I wanted everything to be all figured out right there and then. I wanted to realise my passion, start a business, make money and be successful, all at the same time. But none of these things happened in the space of time I hoped they would.</p><p><strong>I learnt to throw myself in. Literally, to seek all opportunities.</strong></p><p>So, I volunteered at university, applied for internships, took online courses, started reading again, and attended more networking events. I truly believe that these experiences, some seemingly insignificant, some more memorable, started to mould me.</p><p><strong>I learnt to properly visualise my future.</strong></p><p>In 2016, I found that I would spend a lot of time thinking about how I imagined my future to be, but never really thought of the in-between — all the little steps I would need to take to get me to the top. So I started to ask myself these questions: Who am I in 5 years? 10 years? Where do I live and work? What would I have accomplished by then? How will my goals challenge me? What obstacles might I face? What experiences might I have had by then?</p><p>All of these 2016 teaching moments have brought me to a place where I’m content with my progress thus far and more motivated than ever to not just be, but to do, to inspire, to make a huge impact in whatever place I find myself.</p><p><strong>To anyone who might be at a similar stage in life, this is the prime of our lives — our youth, our freedom. Remember that your liberty is not restricted to where you are, so make it a point to experience and learn as much as you possibly can.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1320229155c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>