Web Developer | Digital Designer | Business Owner | Content Creator
Today is September 11, 2020, and for this Friday Facts episode we're covering:Landing Pages that ConvertScaffolding Web Development ToolsDesign SystemsLet's dive in!----Landing pages can make or break a product sale or other intended call-to-action. It can be difficult to create a landing page that boils down your product or service into a quick and easily consumable page. Yesterday, Dribbble posted about how to design a landing page that converts which offers several helpful tips on designing phenomenal landing pages. Tips include removing the main navigation, using shorter forms, and more.----Many of us as web developers are constantly coming up with ideas and creating new repositories for them. But we want to get right in and starting coding our idea, and the last thing we want to do is take a long time setting up the basic elements of a new project. On Wednesday, SitePoint posted about 10 scaffolding web development tools to start new projects faster. The list includes Meteor, Sails, Svelte, and more, giving a great place to start for any developer.----Design systems help maintain consistency and brand presence across an organization. They take a lot of time and effort to create and maintain, but they are well worth the result of a elite-looking company. Toptal recently posted a guide to design system models that includes use case and principles to remember when creating a design system for your organization.----Want to know more? Head to fewdaily.com for more of today’s topics and other front-end web content! If you liked what you heard be sure to rate, review, and subscribe on your platform of choice. That's all for today, tune in tomorrow!This podcast uses the following third-party services for analysis: Podcorn - https://podcorn.com/privacy
Today is September 10, 2020, and for this Thursday Thoughts episode we're covering:Improving App SupportWebsite Considerations for Blind PeopleTools for Website AccessibilityLet's dive in!----Without a doubt, when you think of a company you love, one of the key components is most likely a great support team. For me, the way a company handles a support request can make or break my opinion of the company. Luckily, Shopify brought together a panel of experts to give their opinions on how to improve support for your application. Tips range from automation to product ownership and can greatly assist coming into the end of the year.----Many website users have disabilities or impairments that limit the way they interact with a website and it is important to consider as many of these use cases as possible. One such case is accessibility for blind users. A post yesterday on the DEV community listed 5 annoying website features for blind people, which include image descriptions, heading structure, and more. Check it out and make sure to consider these issues when building your next project.----To continue on the accessibility route, there are many components of website design that us as developers only see through our lens. This is why it is important to research accessibility and solutions, but it can be hard to sift through all the information. Another post yesterday on the DEV community outlined some more considerations for web accessibility and also some tools to help. Make sure to add some of these tools to your design and development workflow if you haven't already.----Want to know more? Head to fewdaily.com for more of today’s topics and other front-end web content! If you liked what you heard be sure to rate, review, and subscribe on your platform of choice. That's all for today, tune in tomorrow!This podcast uses the following third-party services for analysis: Podcorn - https://podcorn.com/privacy
Today is September 9, 2020, and for this Wednesday Wisdom episode we're covering:Reduced Motion DesignLinking to the Web ArchiveImproving Client CommunicationLet's dive in!----Modern web browsers now support a wide range of CSS and JavaScript properties that can create awesome interactive features and animations. However, it is important to keep accessibility in mind and realize that some people have sensitivities to too much motion. Yesterday's post on Smashing Magazine outlined how to use the prefers-reduced-motion media query to take these users into account. The feature has fairly good support now across browsers (sorry IE users) and can be used in both CSS and JavaScript.----When linking to an internal page on your website you can be confident that the content will always be there, or at least be redirected to. But when you link to an outside resource you are at the mercy of that website owner, or are you? A post on Monday from Hawaii GenTech brought up the interesting idea of linking to a web archive version of that page to ensure consistency, avoid broken links, and perhaps have better link authority. What do you think: should you link to an archive like the WaybackMachine or to the direct source?----Quality communication with your client is the key to any successful project. Finding that perfect zone of not over-communicating or under-communicating can be challenging for many, especially those newer to client interactions. Last week SpeckyBoy published a post about how to improve client communications to avoid wasting your time and the client's. For example, being very specific about your services up-front can help avoid headaches down the line.----Want to know more? Head to fewdaily.com for more of today’s topics and other front-end web content! If you liked what you heard be sure to rate, review, and subscribe on your platform of choice. That's all for today, tune in tomorrow!This podcast uses the following third-party services for analysis: Podcorn - https://podcorn.com/privacy
Today is September 8, 2020, and for this Tuesday Tips episode we're covering How to Rename Your Master Branch on GitHubLet's dive in!----Recent events have brought to light the negative connotations of having the main branch on a repository called master. Whether you want to change your primary branch name for this reason or just for fun, it is important to know how to do so and there are a few key steps to ensure that the change goes smoothly.----Before we jump into changing our existing repos, let's make sure that we avoid the issue altogether in our future projects. In GitHub, under Settings > Repositories there is an option to name your default branch for future projects. Remember, this changes it for your personal account, but you can do the same for an organization.As a note, on October 1st of this year, GitHub will be setting the default branch for new repositories to main.----Now, to change an existing repo to a new name add a new branch from the existing master, which we will call main for this example. With an exact copy now on main go to the repository Settings > Branches and change the default branch to main. Then we can delete the master branch, which will alert us that the open pull requests for master will be affected. You can use a tool, like this one from Edward Thomson, to re-target the pull requests to the new branch.And that's it! You've made the change away from the master branch. If you still think it sounds a bit too complicated or too much work, GitHub announced that it will be releasing a feature to make a seamless transition when renaming the default branch by the end of the year.----Today's Tuesday Tips was adapted from a post on the DEV Community.----Want to know more? Head to fewdaily.com for more of today’s topics and other front-end web content! If you liked what you heard be sure to rate, review, and subscribe on your platform of choice. That's all for today, tune in tomorrow!This podcast uses the following third-party services for analysis: Podcorn - https://podcorn.com/privacy
View 137 more appearances
Share Profile
Are you Morgan? Verify and edit this page to your liking.

Share This Creator

Recommendation sent

Join Podchaser to...

  • Rate podcasts and episodes
  • Follow podcasts and creators
  • Create podcast and episode lists
  • & much more

Creator Details

Birthdate
Jun 19th, 1993
Episode Count
47
Podcast Count
2
Total Airtime
3 hours, 55 minutes
PCID
Podchaser Creator ID logo 552466