Material Design for Bootstrap is a theme for Bootstrap 3 which lets you use the new Google Material Design in your favorite front-end framework.
I am currently working on a WPLMS enhancement for a customer, that allows to simplify the payout of instructor commissions. The whole system runs on the MyCred Points System and students pay for courses with Points. The problem is how to easily payout the instructor commissions via PayPal.
There is currently no addon for MyCred available that does that magic, so I build one myself.
At the moment the payment process via PayPal is completely manual, due to budget constraints. I am basically generating a custom „Send Money“ link that prefills the PayPal email and amount to send.
The interface itself handles the payout sessions, tracks the instructor balance, paid and unpaid points.
Here some images to illustrate the admin dashboard:
This list the instructors and their point balance and allows to start the payment process.
Payout sessions make sure, that only one session can be started per instructor, as the instructor could earn new points during the process. The points converted can be changed, allowing you to payout a fixed amount of points.
Its a 3 step process. Login at PayPal. Open the „Send money“ dialog and send money to instructor. Confirm that you manually send the money and than register the payment and payout points in the system.
The session can be cancelled at any point. You can also leave the session open and continue at a later point.
On the frontend I added an interface to the BuddyPress Profile, that allows the instructor to track his payouts and balance.
The whole setup could be updated using PayPal Adaptive Payments, to make the whole process completely automated. Something to consider for the future :) Pretty happy with the manual process so far and it will be a great help for my customer to keep track of the commission payouts.
The whole setup is currently targeted for WPLMS, but can easily be adapted to other setups using the MyCred Points System.
„This repository is a community-curated list of flexbox issues and cross-browser workarounds for them. The goal is that if you’re building a website using flexbox and something isn’t working as you’d expect, you can find the solution here.“
They built screensiz.es to quickly find the screen specifications of the most popular devices and monitors currently on the market.
Finally identical inputs across different browsers and devices — both desktop and mobile.
iCheck is verified to work in Internet Explorer 6+, Firefox 2+, Opera 9+, Google Chrome and Safari browsers.
Mobile browsers (like Opera mini, Chrome mobile, Safari mobile, Android browser, Silk and others) are also supported. Tested on iOS (iPad, iPhone, iPod), Android, BlackBerry and Windows Phone devices.
We are getting closer to Boostrap 4 and I really love what we are getting with the first alpha version.
I started adding a standard preface to emails from clients asking to work with me. So here it is, for potential new clients, that think about working with me :)
Anything else about me can be read here:
http://www.portalzine.de/services/
http://www.portalzine.de/services/about-alex/
http://www.portalzine.de/services/portfolio/
If you made it so far and you still would like to work with me, we can move to step 2 :)
Sadly IE8 is still a browser we need to build for. Sometimes loading a set of local webfonts can break the whole website, as needed resources are not being loaded or timeout.
Best way is to split IE8 webfonts loading from other browsers, by using conditionals:
|
1 2 3 4 5 6 |
<!--[if lt IE 9]> <link rel="stylesheet" href="fonts.ie.css" type="text/css" media="screen" /> <![endif]--> <!--[if gte IE 9]><!--> <link rel="stylesheet" href="fonts.css" type="text/css" media="screen" /> <!--<![endif]--> |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
@font-face { font-family: 'Black'; src: url('black-webfont.eot'); } @font-face { font-family: 'Regular'; src: url('regular-webfont.eot'); } @font-face { font-family: 'Bold'; src: url('bold-webfont.woff.eot'); } |
Only loading the required .EOT files.
|
1 2 3 4 5 |
@font-face { font-family: 'YourFont'; src: url('yourfont.eot'); src: url('yourfont.eot?#iefix') format('embedded-opentype'), url('yourfont.woff') format('woff'), url('yourfont.ttf') format('truetype'), url('yourfont.otf') format('opentype'), url('yourfont.svg#YourFont') format('svg'); } |
These are added within a <style> section in the header. This works all nicely in most modern email clients, but Outlook does not load webfonts and falls back to Times New Roman, which might not always be desired.
|
1 2 3 |
[style*="YourFont"] { font-family: 'YourFont', 'Century Gothic', CenturyGothic, AppleGothic, Arial, sans-serif !important } |
Add this to the header <style> section as well. This makes sure that in clients, that allow Webfonts, your font is actually being used.
|
1 2 3 4 5 6 7 |
<table> <tr> <td style="background:white;height:30px;font-family: Arial, 'YourFont', 'Century Gothic', CenturyGothic, AppleGothic, sans-serif;"> Some text! </td> </tr> </table> |
In the body of the email template, you assign your font-family styles for the text, but making sure that Arial is listed first.
Outlook will than use Arial for the text styling.
In modern clients this will be overwritten with the „style rule“ above, which checks for YourFont and updates the font-family styling accordingly.
