At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
| <?php | |
| if ( ! defined( 'ABSPATH' ) ) die('-1'); | |
| /* | |
| * WDG-customized version of the Events Calendar Pro mini calendar widget. | |
| * Changes are noted inline. | |
| * Replacing class name: Tribe__Events__Pro__Mini_CalendarWidget | |
| */ | |
| class MultisiteTribeEventsProMiniCalendarWidget extends WP_Widget { | |
| function __construct() { |
| The MIT License (MIT) | |
| Copyright (c) 2015 Justin Perry | |
| Permission is hereby granted, free of charge, to any person obtaining a copy of | |
| this software and associated documentation files (the "Software"), to deal in | |
| the Software without restriction, including without limitation the rights to | |
| use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of | |
| the Software, and to permit persons to whom the Software is furnished to do so, | |
| subject to the following conditions: |
| var areWeOpen = function() { | |
| var bizHours = [ | |
| ["0900", "1800"], | |
| ["0630", "2000"], | |
| ["0630", "2000"], | |
| ["0630", "2000"], | |
| ["0630", "2000"], | |
| ["0630", "2000"], | |
| ["0800", "2000"] | |
| ]; |
| //The following section is an add-on to this tutorial - https://tri.be/gravity-forms-events-calendar-submissions/ | |
| //Shout to CreativeSlice.com for their initial work | |
| /* Before Starting: | |
| - Make sure you have these three plugins installed | |
| - Gravity Forms | |
| - The Events Calendar | |
| - Gravity Forms + Custom Post Types | |
| - Once Gravity Forms is installed, create a form with these fields | |
| - Single Line Text (Event Title) | |
| - Paragraph Text (Event Description) |
| @mixin for-phone-only { | |
| @media (max-width: 599px) { @content; } | |
| } | |
| @mixin for-tablet-portrait-up { | |
| @media (min-width: 600px) { @content; } | |
| } | |
| @mixin for-tablet-landscape-up { | |
| @media (min-width: 900px) { @content; } | |
| } | |
| @mixin for-desktop-up { |
| let webpack = require('webpack') | |
| module.exports = { | |
| devtool: 'inline-sourcemap', | |
| context: __dirname, | |
| entry: "./index.js", | |
| output: { | |
| path: "./js", | |
| publicPath: '/js', | |
| filename: "bundle.js" |
