<?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 Tosin Orimogunje on Medium]]></title>
        <description><![CDATA[Stories by Tosin Orimogunje on Medium]]></description>
        <link>https://medium.com/@reemtos?source=rss-8b5f212c5e6f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hv68pTwf7tVKdUClr9Xr2w@2x.jpeg</url>
            <title>Stories by Tosin Orimogunje on Medium</title>
            <link>https://medium.com/@reemtos?source=rss-8b5f212c5e6f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:40:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@reemtos/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[Dangling Element Selectors in CSS and Why You Should Avoid Them]]></title>
            <link>https://medium.com/@reemtos/dangling-element-selectors-in-css-and-why-you-should-avoid-them-171f6cd989b1?source=rss-8b5f212c5e6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/171f6cd989b1</guid>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[css-selectors]]></category>
            <category><![CDATA[code-quality]]></category>
            <dc:creator><![CDATA[Tosin Orimogunje]]></dc:creator>
            <pubDate>Tue, 18 Feb 2020 18:06:00 GMT</pubDate>
            <atom:updated>2020-03-02T18:47:38.054Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e65ErfQ2c8YsO96yaNva8w.jpeg" /><figcaption>Photo: <a href="https://www.pexels.com/@negativespace">Pexels.com/@negativespace</a></figcaption></figure><p>CSS selectors are used to specify what elements a set of CSS rules are applied to. There are different types of CSS selectors: pseudo, class, attribute, etc. You can <a href="https://www.w3schools.com/cssref/css_selectors.asp">look here</a> for a full list of the selectors and how they can be used.</p><p>One particular type of selector that is of interest here is the <strong><em>(element) type selector</em></strong>. Type selectors are usually reserved for making extensive changes in stylesheets as they match elements by node name. They are usually found in base and reset stylesheets where they define default properties.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d8322f4a7d5344de8ad25299007a4226/href">https://medium.com/media/d8322f4a7d5344de8ad25299007a4226/href</a></iframe><p>Type selectors are often advised against for regular styling and are usually considered <strong><em>“bad practice”</em></strong>. When used inappropriately, they cause several issues that affect code maintenance. One of the most common of these issues is what is referred to as a <strong><em>dangling element selector</em></strong>.</p><h3>What are dangling element selectors?</h3><blockquote>Dangling element selectors are, in most cases, child elements that are styled using a type selector (element name), as opposed to using a class or an id.</blockquote><p>For better context, let’s examine the CSS code below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6aa45d65afc5c87e8ffe78a8e61835b7/href">https://medium.com/media/6aa45d65afc5c87e8ffe78a8e61835b7/href</a></iframe><p>From the example, the properties defined will be applied to any span element found in that parent element. That span element is an example of a dangling element selector.</p><p>Unfortunately, they are very rampant in a lot of stylesheets today, and they pose a threat to the long term maintainability of projects. They can have unexpected side effects in the long run, and it is important that we understand these effects beforehand.</p><h3>What are the problems associated with dangling element selectors?</h3><p>There are a number of pitfalls associated with dangling selectors and I’ll highlight a couple of them as follows...</p><h4>1. They don’t provide context or clarity about what they are being used for.</h4><p>Looking at the span element in the snippet below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6aa45d65afc5c87e8ffe78a8e61835b7/href">https://medium.com/media/6aa45d65afc5c87e8ffe78a8e61835b7/href</a></iframe><p>It is difficult to know what the span element is actually being used for. It is possible that it is used to emphasize a short text, or as a label or tag on a post. The purpose can be anything really, but unfortunately, there is no clue here.</p><h4>2. The dangling element cannot be used for something else in that block.</h4><p>If there is a need to use another span element in that code block, say for an entirely different purpose, there are going to be issues because the properties from that snippet will automatically be applied to all available span elements in that parent-element.</p><p>For more context, let’s examine the html code below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/39070f9ac6017ce0a9c6682285e91efa/href">https://medium.com/media/39070f9ac6017ce0a9c6682285e91efa/href</a></iframe><p>From this snippet, the second span will be affected by the dangling selector in the CSS. Its position (inside of the paragraph) won&#39;t matter, and neither will its own style definitions.</p><h4>3. The dangling selector can lock your styles to a specific HTML structure, and that can hinder code reusability.</h4><p>If there is a need to apply the same styles to elements with different markups in several sections of the project, there will be a problem. Code duplication will most likely occur, and that is not good.</p><p>For example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c6ffa586bb80456eacf7297175a8365f/href">https://medium.com/media/c6ffa586bb80456eacf7297175a8365f/href</a></iframe><p>The CSS properties defined for the list above cannot be applied outside of the post element, even if we need our lists to be the same across several sections.</p><h4>4. Maintenance becomes difficult as that code block can (and will) break easily if the element changes.</h4><p>There are various cases during code refactoring where you discover semantic errors in the HTML and decide to fix them. Maybe an em or strong tag is more appropriate in place of the second span element (in the example in 2 above).</p><p>If you substitute the span element for the desired element, it will cause the text that it wraps to loose the desired styling, causing a possible break in that section or page. There will be a need to revisit the CSS, which may not be necessary in the first place.</p><p>Mike Riethmuller, one of my favorite CSS developers and writers, also addressed a similar concern about dangling selectors in a tweet.</p><h3>Mike Riethmuller on Twitter</h3><p>Can we have a quick chat about dangling element selectors? That&#39;s something like this `.my-component span` that empty element on the end is loose in terms of specificity, if the html structure changes it can break. Also can&#39;t use spans for anything else in this component.</p><h4>5. The stylesheet becomes difficult to understand without seeing the corresponding html markup.</h4><p>To understand what that span element is used for, one would need to check the HTML for the data that it contains, and for further clarity, you might be required to preview the section/page in the browser, which is really unnecessary.</p><h4>6. Changes in the markup or stylesheet become dependent on each other.</h4><p>Unless your intention is to break the code or cause some discrepancies in a specific section or page, it is completely impossible to make any structural change in the html markup without consulting the stylesheet, and vice-versa.</p><h4>7. Properties set on the dangling element can cascade to child elements unintentionally.</h4><p>Even though the style definitions were intended for the dangling element, some of the styles may be inherited by child elements inside of it.</p><p>For example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/44f943485c9ba3bbbf78350deb8121d3/href">https://medium.com/media/44f943485c9ba3bbbf78350deb8121d3/href</a></iframe><p>The CSS properties defined above for the list will definitely cascade down the nested list, and that might not be intended. Maybe we want the nested list to look different from its parent, that won’t be the case here.</p><h3>How do you avoid dangling element selectors?</h3><p>At the barest minimum, just add an appropriate and meaningful class attribute to the element and use that to style instead.</p><p>For example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/83eb8947605f4ed513d08d316c9f22c3/href">https://medium.com/media/83eb8947605f4ed513d08d316c9f22c3/href</a></iframe><h4>This simple fix has the following implications:</h4><ol><li>Only the span element with the post__date class is affected by the properties defined, and only the one with the highlight class will have blue color. This means that one can easily add several span elements in the post element as desired.</li><li>One can easily substitute the span in the html markup for any other element (e.g. strong) as appropriate, and give the highlight class to it and everything remains intact.</li><li>Anybody can make a conscious change or substitution in the html markup keeping the class(es) in mind.</li><li>With the use of appropriate class names, one can simply have an understanding of what the element with any of the selectors is doing just by looking at the stylesheet, without having to consult the html markup.</li><li>Also, when we do away with dangling selectors and use classes appropriately, it fosters reusability. You can simply apply classes to several elements with different structures without duplicating your styles or complicating them.</li></ol><h3>In conclusion.</h3><p>As much as possible, it is recommended that the use of dangling selectors be avoided if scalability, maintenance or readability are a concern.</p><p>There is no use case for a dangling element selector. Every element can be styled using a class or an id. Do not make code maintenance frustrating for yourself, or for participants in a collaborative project.</p><p><em>Thanks to </em><a href="https://twitter.com/MikeRiethmuller"><em>Mike Riethmuller</em></a><em> for his input on this article.</em></p><p><strong><em>Thank you for reading. If you find this post insightful in any way whatsoever, please endeavor to share it with someone.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=171f6cd989b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning Frontend Masters: Part II (Courses Page)]]></title>
            <link>https://medium.com/@reemtos/redesigning-frontend-masters-part-ii-courses-page-885fb9264a49?source=rss-8b5f212c5e6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/885fb9264a49</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[frontend-masters]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-challenge]]></category>
            <dc:creator><![CDATA[Tosin Orimogunje]]></dc:creator>
            <pubDate>Fri, 15 Feb 2019 16:55:26 GMT</pubDate>
            <atom:updated>2019-02-15T19:08:26.020Z</atom:updated>
            <content:encoded><![CDATA[<p>Okay.. So like the title suggests, this is actually a second part to a design publication. I recently completed a design challenge where I gave some parts of <a href="https://frontendmasters.com/"><strong>Frontend Masters</strong></a> a design overhaul and I documented how I went about the new designs.</p><p>Due to the length of the entire documentation, I decided to split them into two, with each part representing an entire aspect of the design. I published <a href="https://medium.com/@reemtos/redesigning-frontend-masters-part-i-pricing-page-da57c8144409">the first part</a> where I focused on their <strong>Pricing Page</strong> some days ago and here goes the second part.</p><h3>The Courses Page: Current Design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7AQjOWv0MOCu4V1BNfpQpA.jpeg" /><figcaption>Current Courses Page</figcaption></figure><p>This page simply does one thing: it lists available courses. You get to browse from their ample list of courses, and there is a very effective search feature for when you have a particular course or instructor in mind.</p><p>Taking a look at the design however, there are a number of inadequacies as regards how information is presented, that affect the usability of this page. For better analysis, I’ll split this page into two sections; the head or introductory section and the listing section.</p><h4>The Head Section</h4><p>This section contains the navigation menu (nav bar), the notification panel, the page heading or title, the filter tabs and the search box. Looking at this section, there is so little and so much going on at the same time. We have a number of elements and colours improperly implemented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fFS3g8rKHofbUBODlnta9w.jpeg" /><figcaption>Current Head Section</figcaption></figure><p>Looking at this section, the most obvious problem here has to be the colour combinations. Having a nav bar with wine colour, the slant orange line (which I addressed in <a href="https://medium.com/@reemtos/redesigning-frontend-masters-part-i-pricing-page-da57c8144409">part 1 of this publication</a>), and a notification with two different blue shades is not the best colour combination.</p><p>First off, I would place the notification close to the nav bar, covering up the orange line, at least until the notification is dismissed. This helps to reduce the number of contrasting colours.</p><p>On the notification panel, the idea of enclosing the information in an overlay (dark box) to maybe draw more attention to it is rather unnecessary. The blue background colour that it has already does the job.</p><p>What I’ll do here is to stick with the dark blue shade created by the overlay (#347384) as our new background colour. This is because this colour is quite cooler compared to the background colour (#4EA2B8) which is quite bright.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*g_s6g5jsxa78DxfK6d9CFw.png" /><figcaption>The different colours as seen in the notification panel</figcaption></figure><p>Also, the hyperlink property on the course title (Introduction to Python) might not be necessary, as it links to the same page that the “register to join online” button leads to. We can definitely do away with it.</p><p>Lastly on the notification, the button’s background colour makes it seem like a primary action rather than the secondary action that it is. When styling several buttons on a page, one has to be careful as regards how much importance is attached to the actions that they perform by their appearance.</p><p>In an article tagged <a href="https://medium.com/refactoring-ui/7-practical-tips-for-cheating-at-design-40c736799886"><strong><em>7 Practical Tips for Cheating at Design</em></strong></a>, this ideology was addressed. See excerpt of the section addressing buttons below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wPbZhzs3AaA9EL_GyfwIVA.png" /><figcaption>Excerpt from aforementioned article</figcaption></figure><p>Keeping this in mind, I’ll stick with a dark, low-contrast button colour for the notification section. This way, it doesn’t scream on the page, and neither does it compete with the “Join Now” button on the navigation section, which is actually a primary action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b-uLFN9rVOOWTne6dTTRUA.jpeg" /><figcaption>New Navigation Bar with Notification</figcaption></figure><p>Moving on..</p><p>The current heading on this page reads “Frontend Masters Courses”. While this is simple and straight-forward, it also appears as unnecessary as the very-legible, typography-based logo already reads “Frontend Masters”.</p><p>I’ll substitute this title with a different phrase along with a sub-heading to accompany it. That way, we get some form of consistency with the Pricing Page.</p><p>Immediately superseding the title section, I’ll introduce an interesting filter that I hinted in part 1 of this article. This filter section is a modified version of the course icons collage that we currently have on the Home and Pricing Pages as seen below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dhd1NrqpRQsveoN1emY3Fg.png" /><figcaption>Current course icons as seen on Home and Pricing Pages</figcaption></figure><p>Currently, on the homepage, this icons serve as filters for courses. While this is a brilliant feature, the implementation in terms of UX doesn’t compliment it, as the icons do not appear as clickable, making the feature less obvious.</p><p>What I’ll do here is to introduce a subtle border around the icons so that they appear as small cards that are clickable. Also, with the help of <a href="https://fontawesome.com/"><strong>Font Awesome Icons</strong></a>, I’d substitute the brand images for icons to eradicate the contrasting colours of the listed courses.</p><p>In addition, I’ll go ahead and introduce labels for each icon listed so as to ensure that people of different technical backgrounds can relate with them. With these, we have a more user-friendly filter section as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RWyNsdqPVcXoFNMDij5giA.jpeg" /><figcaption>New Icon Section with Hover Effect</figcaption></figure><p>In the last part of this section, I’ll bring the search field together with the tabs, because they actually perform similar function — they streamline the listed resources as per user needs.</p><p>Also, I think it’s best we remove the “Learning Paths” link as it points to an entirely different page which unconsciously redirects users from this section. And considering that it is already listed as part of the links in the nav bar, it really doesn’t belong here.</p><p>Lastly, I’ll do away with the blue colour highlighting an active tab and introduce a subtle pink and a wine colour (as seen in the header), for background and text colours respectively. This helps to create a colour blend and ensure that the entire section is clean and simple.</p><p>See below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_GRt5wYGqi1HN-3nyfeFwA.jpeg" /><figcaption>New Title and Filter Section</figcaption></figure><h3>The Listing Section</h3><p>This section is pretty much the major reason why I chose this page. The UI and UX design here can definitely be improved, and I’ll explain how. Let’s take a look at what it looks like..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_CsqRMWxt-WmxWyrX9W0Mg.png" /><figcaption>A fraction of the current Listing Section</figcaption></figure><p>The presentation of each course; the card design, the use of colours, fonts, and the way the images are placed too somehow don’t feel right.</p><p>There is also some sort of inconsistency as regards how the courses are presented when switching between ALL and POPULAR courses. We get a grid layout for the former, and a list layout for the latter.</p><p>While the grid style may be a deliberate implementation so as to display more courses, I totally feel the list style provides a better and cleaner UI. And moreover, I don’t see how displaying that much courses to a user is of any good. The list becomes overwhelming really.</p><p>Also, taking a look at how the images are presented, the course details are deliberately positioned to cover major parts of the image and this creates a huge mess. The resulting design is disturbing and difficult to process as you find yourself trying to see what the image is.</p><p>An interesting fact here is that the images somehow compliment the course details as they are the first to catch one’s attention. One can simply identify with a course in less than a second with the help of the images without having to read through the course details, and this is a huge plus in terms of UX.</p><p>So, first off, I’ll lose the grid layout to allow for courses to be displayed in list form, as implemented in the <strong>Popular Courses</strong> section. This will allow the accompanying images to be clearly visible and also, it ensures design consistency across all tabs.</p><p>The alternative to this would be to have the course details sit beneath the image, allowing for the grids to stay, but the individual course cards will however be tall; tall enough to take two rows of the list format, which is a lot more preferable.</p><p>The details section of each course will retain the structural look that it currently has, but with little modifications. I’ll substitute the black background for a white background so as to allow the contents in it pop. The colours of the texts inside of it will be inverted to have different shades of black.</p><p>The course titles will however have their colours changed to orange ONLY when you hover on their individual cards, so as to subtly distinguish them from the rest.</p><p>The buttons for “preview” and “access” will also be modified. They currently draw too much attention together so I’ll keep the background colour for the preview button while I substitute that of the access button for black.</p><p>I’ll also introduce some befitting icons to compliment each one and also to add some life to them. These changes, although minor, somehow improve the design and more importantly, the usability.</p><p>Let’s preview:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aI59PIBmRkOK0KRMVv-u6g.png" /><figcaption>New List Section for Courses</figcaption></figure><p>Last change I’ll make here is the implementation of pagination. Currently, this section scrolls infinitely as ALL of the courses on the platform get listed at a go, without some form of pagination or a “load more” button to ensure user control and friendliness.</p><p>While a “load more” button would be a nice-to-have, it actually causes the list to grow endlessly as a user clicks on it, and eventually makes the page lengthy; bringing us back to the current problem.</p><blockquote>A major pitfall of the load more button is its irreversibility. Once new entries are loaded, they can’t be unloaded or removed unless the page itself is reloaded.</blockquote><p>This therefore makes “pagination” the most appropriate choice to solve this problem. Users can navigate to see more courses by simply moving to different pages, and can also move back to older pages with the aid of next and previous buttons respectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*hnLKKlHhdkceP_ciTJGTRQ.png" /><figcaption>Pagination section</figcaption></figure><p>Bringing all of the modifications and sections together, along with the improved Footer section (implemented in the Pricing Page), we have a cleaner version of this page, with a better UX and accessibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u-Ot_Jy4IPRHbsDy6OJmhQ.jpeg" /><figcaption>New Courses Page</figcaption></figure><h4>A comparison of the old and the new Courses Page..</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gq5wB4TZsJW4QQ4f5M0zjw.png" /></figure><p>If you missed the first part of this publication, <a href="https://medium.com/@reemtos/redesigning-frontend-masters-part-i-pricing-page-da57c8144409">click here</a> to read it.</p><p><strong><em>I would love to have your feedbacks as regards the entire redesign. Please endeavour to drop comments and also share.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=885fb9264a49" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning Frontend Masters: Part I (Pricing Page)]]></title>
            <link>https://medium.com/@reemtos/redesigning-frontend-masters-part-i-pricing-page-da57c8144409?source=rss-8b5f212c5e6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/da57c8144409</guid>
            <category><![CDATA[frontend-mas]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-challenge]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Tosin Orimogunje]]></dc:creator>
            <pubDate>Mon, 11 Feb 2019 10:18:43 GMT</pubDate>
            <atom:updated>2019-02-16T06:43:55.310Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sYS931L1IoRaD1Pw80JjHQ.jpeg" /></figure><p><a href="https://frontendmasters.com/">Frontend Masters</a> is an online learning platform with some of the best front-end engineering courses that there are, taught by industry heavyweights with decades of experience and know-how.</p><p>I got on the platform for some React tutorials and after a couple of days into the course, I started paying attention to the site’s user interface (UI) and user experience (UX). I realised how bad some vital parts of the site were and I thought I’d take another design challenge following <a href="https://medium.com/@reemtos/redesigning-gary-simons-coursetro-69ee49d77aa8">my last one</a>.</p><blockquote>The design challenge is something I embarked on last year to better my UI/UX design skills. I simply pick a site that I like and use quite frequently, look at areas of improvement on the site, and see how I can better what they have in terms of design and usability.</blockquote><p>So for this challenge, I opted for two of their pages, the <strong>Pricing Page </strong>and the <strong>Courses</strong> <strong>Page</strong>. I redesigned these two pages but due to how much detail is required for documenting the process, I decided I’d write about both designs in separate publications.</p><p>As a matter of fact I took a poll on Twitter to decide on this..</p><h3>Oluwatosin O. on Twitter</h3><p>Hi guys! Would you rather read a lengthy @Medium article or have it splitted into 2 separate (but linked) articles? Poll required for my next publication, please. 🙂</p><h3>Current <strong>Pricing Page</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*svHODPcwzMrWre9aGSQtlA.png" /><figcaption>Current Pricing Page - Frontend Masters</figcaption></figure><p>Looking at this page, the data presentation needs some improvement. The use of space, colour choice and font use also. The flow for plan selection could be enhanced to ensure better usability. Also, there is no central focus on the page. Every piece of information is almost consumed together at a go.</p><p>While the navigation section is almost perfect, the slant orange line creates a mess. For a sharp orange colour (on a black background), it appears as too thick and lousy. It would be nice to have it as thin yet visible, so it appears as creative and clean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aIRXzjv6yx6DlWACiNqZ2w.png" /><figcaption>Navigation, Heading and Course Icons Section</figcaption></figure><p>The heading and sub-heading on the page, as shown, are alarming. They carry too much weight and size. I also think the course icons do not belong here, as the heading and sub-heading are actually sufficient. They do not make any significant impact in the plan selection process. If you have them on the Courses Page, however, that would make a lot more sense.</p><p>So what I’d do is to de-emphasise the heading by reducing the font-size and also the weight of the sub-heading. I’ll also kill the icon section that immediately follows and give some adequate spacing to allow for clarity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*An-pTD20_Qsr9RmUXP8sSQ.jpeg" /><figcaption>Improved Navigation and Heading</figcaption></figure><p>Looking at the Plans Section, it’s quite a mess. The cards, the labels, colour choice, selection hint (orange colour) and data presentation are not great. The listed plans also, are somewhat misleading as regards how many plans there are. At first glance, you’d see four (4) plans in total.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JbESr8ltevVYxeTb3cHTbg.png" /><figcaption>Current Plan Section — Frontend Masters</figcaption></figure><p>On a closer look, there are actually just two (2) plans; an <strong>Individual Plan</strong> for a single-user and a <strong>Team Plan </strong>for multiple users. The two plans, however, have two (2) methods of payment each, <strong>monthly</strong> and <strong>annually</strong>. The lack of proper categorisation and the naming convention for each plan makes the entire information confusing and quite difficult to digest.</p><p>What I’ll do here first is to categorise the plans into “<strong>Individual Plan</strong>” and “<strong>Team Plan</strong>”. These plans will both emphasise the different payment methods available, which are <strong>monthly</strong> and <strong>yearly</strong>, along with their respective prices, perks and details.</p><p>For the purpose of clarity, I’ll present these information on a tall, white card, with a top border colour of red to show what plan is being considered for selection. I’ll also display the payment options in a form-like presentation, specifically using radio buttons, so as to create a sense of actual selection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iHyzzUeOu3nBpk8KbPE4jw.jpeg" /><figcaption>New Plan Cards</figcaption></figure><p>The perks for each method of payment is listed underneath, as shown above, and a call-to-action (button) is displayed at the bottom of each card to initiate payment after selection is done.</p><p>Another improvement in this section is the decision to opt for a light background, an actual shade of the wine colour on the header with 0.1 opacity. While this could pass as a personal preference, it also makes the contents of this section pop.</p><p>With these changes, our plan section, along with the heading, is a lot improved; as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZgmmwYegMkB_miFsJnVzfQ.jpeg" /><figcaption>New Heading and Plans Section</figcaption></figure><p>Moving on..</p><p>From the current design, what immediately supersedes the plan section is a form for account creation, see below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*483QP9RpmO5IRUosymTvmg.png" /><figcaption>Current Form Section as seen below the Plans</figcaption></figure><p>While this may hasten the process, I completely feel it breaks the natural flow of plan selection/purchase. One doesn’t get the feeling that a plan has been selected as one plan is automatically “highlighted” (with an orange background colour on the plans card) as soon as the page is served. For most people, the highlight on the card doesn’t imply a form of selection, considering the fact that it is not user-initiated.</p><p>What I would do here is to exclude the form from here, and introduce it on a different page (which I’ll present later on), as soon as a user clicks on the “<strong>Start Learning</strong>” button. That way, a user is aware that he/she has selected a plan and is ready to create an account.</p><p>I would also go ahead to introduce an “<strong>FAQ Section</strong>” immediately after the plans section. According to an article on Shopify’s blog as regards <a href="https://www.shopify.com.ng/blog/120928069-how-to-create-faq-page"><strong><em>the benefits of an FAQ page</em></strong></a>, FAQs do more than answering probable questions; they actually perform numerous other functions, some of which are highlighted below in an excerpt of the article:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dn_4sV4H8-Q_T9t4904DHw.png" /><figcaption>Taken from aforementioned Shopify article</figcaption></figure><p>The new FAQ section will also contain a means of contact to enable answering of further questions. With these, we have:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uu1BQ4GxRfv8YbmnQErl_w.jpeg" /><figcaption>New FAQ Section</figcaption></figure><p>Moving on to the current Testimonial Section, which is a collection of Twitter embeds, a couple of adjustments would be made. Personally, I despise default Twitter embed design on a site simply because they sort of convey lack of design depth on whatever site that showcases it.</p><blockquote>Twitter embeds come with extra information that are sometimes needless, as the case may be. The like button and count, the timestamp, etc. are examples.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zzLyEzIJFKqC06uN6VKpFQ.png" /><figcaption>Current Testimonial Section</figcaption></figure><p>In the example above, I do not see a need for the timestamp of the tweet because it doesn’t add a significant value to the displayed feedback. Also, a link to the person’s “other tweets” is very inessential, as I doubt that anybody would want to see unrelated tweets to a particular feedback. So for design consciousness, I’d definitely do away with both of them, along with the likes button.</p><p>Another worthy improvement would be to substitute a person’s username for their field of study or stack choice. That way, we display feedbacks that aren’t just site-specific, but also course-specific. A react native developer, for example, could simply provide feedbacks regarding an awesome React course on the platform, which I think makes more sense.</p><blockquote>While the “field of study” information may not be available in the tweet retrieved, I’d suggest that feedbacks should be obtained directly from members of the platform, say for example, upon starting, completing or mid-way through a course.</blockquote><p>With these changes, and also by moving things around in the currently distorted Footer Section, we get a cleaner closing section of this page, as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nIYTSU7WSTbv3FVdwg9lhg.jpeg" /><figcaption>New Testimonial and Footer Section</figcaption></figure><p>Piecing the entire changes together, we have a much cleaner design with better user experience. There is clarity of information and the plans, which are the central focus of this page, have a better presentation.</p><h4>See complete design below:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NPR65sLUIPZxIdivMsTXUw.jpeg" /><figcaption>New Pricing Page in Full</figcaption></figure><h3>Lastly, the Checkout Page..</h3><p>The checkout page is served when a user selects a plan and clicks on the “Start Learning” button. This page simply displays information as regards what plan was selected and presents a form for account creation, as used in the current design.</p><p>On this new design, we highlight a number of things: what plan has been selected, the perks of the plan, its price, the payment method, a link to switch between available plans, and a testimonial to encourage plan purchase.</p><p>We also get the form for account creation as used in the current design, but in a much cleaner and well-segmented format. Let’s take a look..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QBVWr6y9EQ3LfFlJXNOdEA.jpeg" /></figure><p>All of these changes somehow create a better user-experience and ensures that the entire process of choosing and registering for a plan is smooth and interesting.</p><h4>A comparison of the old and the new pricing page..</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HHQv25ASU8cI372v2OuVEA.jpeg" /></figure><h4><strong>The second part to this publication focuses on the Courses Page, and is </strong><a href="https://medium.com/@reemtos/redesigning-frontend-masters-part-ii-courses-page-885fb9264a49"><strong>available here</strong></a><strong>.</strong></h4><p><strong><em>Please leave your feedbacks in the comment section, and don’t forget to share.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da57c8144409" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning Gary Simon’s Coursetro]]></title>
            <link>https://medium.com/@reemtos/redesigning-gary-simons-coursetro-69ee49d77aa8?source=rss-8b5f212c5e6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/69ee49d77aa8</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Tosin Orimogunje]]></dc:creator>
            <pubDate>Thu, 30 Aug 2018 06:22:17 GMT</pubDate>
            <atom:updated>2018-08-30T06:22:17.367Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://coursetro.com/"><strong>Coursetro</strong></a> (dot com) is an online learning platform founded by <strong>Gary Simon</strong> where he teaches design and code. Gary himself is the instructor, and his lectures and tutorials cover a wide range of topics; from mobile development, to web, including front-end and back-end development.</p><p>I stumbled on his platform about six months ago, while I was searching for <strong>Vue.js</strong> tutorials. I went ahead to purchase a number of courses on the site, and I have since become a fan of Gary himself, his courses and tutorials.</p><p>Recently, I realised how much improvements his site could use, so I decided to give his site a well-deserved makeover.</p><p><strong>The Current Design</strong></p><p>I’m only going to work on the home (lading) page, so this is what it currently looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xtpHPJsb-dCy7RQzZsbXTA.png" /><figcaption>Current Coursetro Homepage</figcaption></figure><p>At a glance, what you get is the course listing, which is quite alright. The logo is awesome and the colour theme is good. The presentation is not great and the site is almost empty, if you take away the course listing.</p><p>It looks like something that was swiftly put together in other to make the courses accessible; which is forgivable really. The overall user-experience and presentation could use a lot of revamping.</p><p><strong>The Head Section</strong></p><p>The head section is almost perfect, no major glitch, font looks great and navigation links are ok. The choice of lower casing (for the links) is perfect as it compliments the logo in a way. However, due to the gradient going on in the background, the links appear to have a faint colour, compared to that of the logo.</p><p>What I would do here is to stick with the green colour from the left (<strong><em>#179B98</em></strong>) as the header’s background colour. This same colour appears as labels on the course cards, so the colour choice isn’t out of the blue. By applying a white colour on the links, they appear clearer.</p><p>Lastly, I’ll move the search icon (and field) away from here as it doesn’t belong with the navigation links, knowing fully well that it is meant for the courses.</p><blockquote>Search icons (or fields) when presented here (in the header) sometimes convey an overall website search, and that is not what is intended for here.</blockquote><p><strong>Introducing a Hero Section</strong></p><p>A hero section is (often times) the first visual element that a visitor encounters on a web page. It is used to provide an overview of a site’s most important content, to introduce a brand, or to sell a product.</p><p>This section usually consist of a big banner (and sometimes videos), either as a background, a component or a slide. It always contains an introductory text, sometimes a paraphrase and a call to action (button).</p><p>The Hero section compliments a web page visually. A huge percentage of websites today usually have this section. An example is Slack’s hero section, as seen below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xIh23tpjTcJaiVqfZgONXA.png" /><figcaption>Slack’s Hero Section</figcaption></figure><p>Back to the design, I introduced an image, courtesy of <a href="https://www.pexels.com/"><strong>Pexels</strong></a>, a heading and a paraphrase that highlights some of <strong>Coursetro’s</strong> biggest features. Also included, is a button that provides access to all courses.</p><p>With these modifications, the header and hero section looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q02k-yIpWsHIql5qEINixQ.png" /><figcaption>New Header and Hero Section</figcaption></figure><p><strong>Improving The Listing Section</strong></p><p>This section will have a number of improvements as the current design didn’t do much as regards consistency or visual appeal. First major change here is the inclusion of the search box.</p><p>I will be placing it here permanently in order to accompany the listings and to enable quick and easy search of courses without having to toggle it’s display.</p><blockquote><strong>One thing about togglers when used for search fields is that the entire search feature is likely to be missed.</strong></blockquote><p>Next improvement is the inclusion of a quick links (or filters) section. Let’s take a look at this screenshot from <a href="https://www.udemy.com/"><strong>Udemy</strong></a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F550bAqD_sBvpFalFPNXEg.png" /><figcaption>Udemy Filter Section</figcaption></figure><p>The filters (above the courses) are intended to ease the burden of search as they provide quick access to specific categories of courses without having to type or navigate the entire site.</p><p>So, by selecting a number of top (or important) categories, we have a couple of tag-like categorisations. They appear as white tags but take on the primary colour when hovered; as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OlGeSdEcqfR88qsDiZJzig.png" /><figcaption>New Search and Filter Section</figcaption></figure><p><strong>The Course and Tutorial Cards</strong></p><p>In the listing section of the current design, we have two categorisations happening; one (supposedly) for tutorials and the other for courses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vcZvotNlQh8uEchOZH2Qaw.png" /><figcaption>Current Listing Section</figcaption></figure><p>This section is poorly executed because the top listing doesn’t carry a heading that describes what the cards represent. What you get is a label on the card with (code) braces. The course section on the other hand has a heading.</p><p>Everything almost looks fine, except for the clustering of the cards, the overlapping of card sizes due to varying text lengths and image dimensions. There is also a slight misalignment of the heading too, so I’ll clean this all up.</p><p>First, I’ll ensure that all images are of the same dimensions, and also implement an ellipsis (three dots) on titles that are longer than expected; so they get displayed in full on hover or when you click on them. This ensures that the display of the cards are uniform and clean.</p><p>I’ll label the top section and kill the code label that the cards currently carry. With these, we have some sort of structural and data consistency. The buttons also stay, but they’ll carry the primary colours to have more life to it and would have befitting labels.</p><p>This gives us a cleaner look as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KYc2u6p9MwYpLAQtIwGG6Q.png" /><figcaption>New Listing Section</figcaption></figure><p><strong>Improving The ‘About’ Section</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cm06Kj1DI4SAWxAwtsesWw.png" /><figcaption>Current About Section</figcaption></figure><p>This section currently appears lifeless, under-utilised and misprioritized. Take a look at this section from <a href="https://teamtreehouse.com/"><strong>Treehouse</strong></a>, where they combine the power of texts, image and right colours to elaborate more on their offers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KZr0ECO8vk9LXlNfgMUpnA.png" /><figcaption>Treehouse screenshot</figcaption></figure><p>This seems more like it. What I’ll do here is to insert Gary’s image here considering the introduction is from him, so as to present him to the visitors. Also, in addition to the current introduction on the site, I’ll highlight some major benefits of using Coursetro in order to sell the platform further.</p><p>With these changes, we have:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*89gN-no1KdqvIYmKiO_HUA.png" /><figcaption>New About Section</figcaption></figure><p><strong>Introducing a Testimonial Section</strong></p><p>Testimonials are an extremely vital part of the success of a product or business. They serve as feedbacks and comments from happy customers and are one of the best ways to build credibility and to show potential customers that you are worthy, reliable and more importantly, to emphasise a sense of community belonging.</p><p>I’ll add a slide-like form of testimonials that will contain as many entries as desired.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v-G6oP4Cg4pLLxK-KrDAhA.png" /><figcaption>Testimonial Section</figcaption></figure><p><strong>Adding A Call To Action (CTA) Section</strong></p><p>This section further emphasises the <strong><em>pro membership feature</em></strong> so as to encourage people to signup by highlighting briefly, the benefits of having a pro account. This section also compliments the entire page visually.</p><p><strong>Cleaning Up The Footer</strong></p><p>I’ll also clean up the footer, include missing and relevant links or items to ensure a meaningful and clean presentation. I’ll bring in the Youtube and Twitter links to encourage community growth across various media; and I’ll categorise the footer links properly so as to convey appropriate meaning.</p><p>Let’s see..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GhDl1UAQtXv_9qHuyTJDFQ.png" /><figcaption>New CTA and Footer Section</figcaption></figure><p><strong>Bringing Everything Together</strong></p><p>Overall, the new design takes the current user experience, the cleanliness and data presentation from good to better, and obviously, to great. It gives Coursetro the look and feel that it deserves, and it also highlights how tiny improvements can play vital roles on a site’s structure, presentation and functionality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CcS3N9ut0gSOo8b8OYDILg.jpeg" /><figcaption>New and Improved Design</figcaption></figure><p><strong><em>Please share your thoughts in the comment section and share with people. Thank you :)</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69ee49d77aa8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>