The post Preloader Style 212 appeared first on Best jQuery.
by Admin via Best jQuery
Tuesday, November 13, 2018
Fonts and Colors Used by Facebook, Twitter, Instagram + More
This article was updated in November 2018 to reflect the most recent colors and fonts used by social networks such as Facebook, Twitter, and Instagram. For the first time this doesn’t include Google Plus, which is now defunct. Was it ever really alive anyway?
Social login buttons, links to social media channels — in 2018 this is still a thing in web design and app design. I mean, what business isn’t on social media these days?
Having a collection of brand assets used social networks, so that we can incorporate them into our own designs, is quite handy. It’s something we Google every time we build an app or website (What is the color used by Facebook?, What is the Facebook color code?, or simply, Facebook blue). In fact, I bet that’s how you found this article!
Well, I won’t keep you waiting. Let’s take a look at the colors and fonts used by Facebook, Twitter, Pinterest, Instagram, Snapchat, LinkedIn, Facebook Messenger, YouTube, and Google Material Design. If I’ve missed something, hit me up on Twitter.
Just show me the main colors (Facebook, Twitter, Instagram, YouTube, Pinterest).
“Facebook Blue” Color Codes
- Hex: #4267b2
- RGB: 66,103,178
Facebook Fonts
- Windows: Segoe UI
- macOS: San Francisco
- iOS: San Francisco
- Android: Roboto
Facebook uses the Segoe UI font for the Windows version of their desktop website, and the Apple-made San Francisco font for the macOS version (both are the default system font). For iOS and Android, it’s San Francisco and Roboto respectively (again, both system fonts, for readability and familiarity. These fonts are becoming a standard.
Read more about Facebook’s Branding Guidelines here.
Twitter Color Codes
- Hex: #38A1F3
- RGB: 56,161,243
Combined with variants of “Twitter Grey” (which contains a mix of blue, black and white tones), Twitter blue (#38A1F3) is used as the primary brand color throughout.
Read more about Twitter’s Brand Guidelines here.
Twitter Fonts
- Windows: Helvetica
- macOS: Helvetica Neue
- iOS: San Francisco
- Android: Roboto
While Twitter has also defaulted to system fonts for their mobile apps (as most social networks do), the Windows version of the website uses Helvetica, and the macOS version Helvetica Neue — somewhat outdated but I’m sure they have their reasons.
Remember when Twitter randomly trialed Gotham Narrow?
Pinterest Color Codes
- Hex: #BD081C
- RGB: 189,8,28
Pinterest’s classic red color has never changed!
Pinterest Fonts
- Windows: Segoe UI
- macOS: San Francisco
- iOS: San Francisco
- Android: Roboto
Fun fact: while Pinterest uses roughly the same fonts that are standard with other social networks, Pinterest uses the Hiragino font for Japanese and other oriental languages, which reads better in comparison to the fonts used with Roman languages.
Read more about Pinterest’s Brand Guidelines here.
“Instagram Grey” Color Codes
- Hex: #231F20
- RGB: 35,31,32
Instagram also uses a combination of different gradients. It’s difficult to understand what the individual colors are and in which scenario they should be used, but you can find all of Instagram’s brand assets here. To be honest, it’s rare to see these colors in the wild — those referencing their social media channels tend to use “Instagram Grey.”
Instagram Fonts
- Windows: Segoe UI
- macOS: San Francisco
- iOS: San Francisco
- Android: Roboto
Nothing out of the ordinary here. As you can, Segoe UI, San Francisco, and Roboto are sort of becoming a standard with social networks, with Instagram being no different.
The post Fonts and Colors Used by Facebook, Twitter, Instagram + More appeared first on SitePoint.
by Daniel Schwarz via SitePoint
MeetMe Lite
MeetMe Lite is the free version of the MeetMe Resume HTML template by UIdeck. The free version includes this neat CV layout featuring a fixed header navigation (that smooth scrolls to sections), biography with profile photo, education timeline, work experience, image gallery with Lightbox functionality, stats and contact details.
by Rob Hope @robhope via One Page Love
Developing a WordPress REST API App: Getting Started
This article on developing a WordPress REST API app was originally published by Torque Magazine, and is reproduced here with permission.
Excitement over the WordPress REST API has been building for what seems like an eternity, but we’re still pretty much at the starting gate in terms of what it’s actually going to mean for site owners and developers once it finally lands.
Though I’ve written extensively about the potential implications of the REST API, I’ve been holding back on actually diving in and getting my hands dirty to date. With the REST API finally taxiing on the runway, now seemed a great time to grasp that nettle and really start digging into detail.
Over the course of this series, I’ll be taking the new hotness for a spin by putting together a simple JavaScript app that uses the REST API to power its content. It promises to be an intense learning experience, but one that will hopefully serve others who are coming from a non-technical background as well.
A Brief Note on My Background
Though WordPress has long been a passion of mine, I’m a writer and entrepreneur by trade. I can’t pretend to be coming at this project from any type of serious development background. “Knows just about enough to be dangerous” would be how I’d charitably classify my coding experience to date.
So, this series won’t be quite the deep dive you might expect from a theming professional such as Jack Lenox, or a senior web developer such as Ramsay Lanier. It should also be no great surprise that I’m not approaching this from the point of view of an established top-tier digital agency looking to kick the tires of the latest technology.
Major agencies such as Modern Tribe are already working with the REST APINope, this series will be much more along the lines of an average WordPress user looking to get to grips with the next generation of the platform via a practical, exploratory project.
Hopefully that’s an approach that will also resonate with a significant percentage of other site owners out there. Put it this way – if your eyes instantly start to glaze over at the introductions of other (admittedly excellent) tutorials such as the one below, this is the series for you:
In the following weeks, through a series of articles, I’ll explain how I’m using Node.js and Express on the backend with a GraphQL server hooked up to a MYSQL WordPress database that uses Apollo to fetch data and pipe it into React components. Don’t worry, I’ll still be using the tried and true WordPress admin interface.
With those caveats out of the way, let’s briefly recap why now is a great time to be really rolling up your sleeves and using the REST API in earnest.
Why Now Is the Time to Embrace the REST API
The launch of Calypso and Matt Mullenweg’s State of the Word address back in late 2015 made it crystal clear which way the wind is blowing in the world of WordPress at large. To put it in a nutshell, the REST API is going to be at the centre of the next stage of the platform’s future, and developers are going to have to get on board with JavaScript sooner rather than later.
We’ve already seen entire conferences devoted to exploring the implications of the REST API, and increasingly large real-world projects basing themselves around it, despite its late arrival. From Microsoft to the New York Times, blue-chip companies worldwide are chomping at the bit to really explore its power.
If you’re a theme or plugin developer, you can rest assured that the vast majority of your competition are already, at the very least, actively researching the topic. If you’re a site owner, you can expect the next five years or more of your site’s development to be significantly defined by the possibilities that the REST API opens up. No matter what way you look at it, now is the time to get on board this particular train.
The post Developing a WordPress REST API App: Getting Started appeared first on SitePoint.
by Tom Ewer via SitePoint
Subscribe to:
Comments (Atom)