For Homebrew v2.6.x and below:
brew cask install ngrok
For Homebrew v2.7.x and above:
{% comment %} | |
* | |
* This loop loops through a collection called `collection_name` | |
* and sorts it by the front matter variable `date` and than filters | |
* the collection with `reverse` in reverse order | |
* | |
* To make it work you first have to assign the data to a new string | |
* called `sorted`. | |
* | |
{% endcomment %} |
В trello board-а има няколко отделни списъка с карти. Всеки отделен списък отговаря на определен жанр от книги, а всяка карта в списъка е отделна книга:
Всяка отделна карта (книга) може да има няколко статуса: свободна, заета, желана, физическо копие, електронно копие.
{ | |
"keys": ["tab"], | |
"command": "expand_abbreviation_by_tab", | |
// put comma-separated syntax selectors for which | |
// you want to expandEmmet abbreviations into "operand" key | |
// instead of SCOPE_SELECTOR. | |
// Examples: source.js, text.html - source | |
"context": [ | |
{ |
# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env | |
# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced | |
# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start | |
# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running. | |
# Add the following to your shell init to set up gpg-agent automatically for every shell | |
if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then | |
source ~/.gnupg/.gpg-agent-info | |
export GPG_AGENT_INFO | |
else |
It’s all about the key selector
What determines the impact of a selector is its key selector. The key selector is a very important thing in the world of CSS as browsers read selectors
right to left
. This means the key selector is the last one before the opening {, for example:
.header ul { /* ‘ul’ is the key selector */ }
.ul li a { /* ‘a’ is the key selector */ }
p:last-child { /* ‘:last-child’ is the key selector */ }
# push relevant tags when pushing branches | |
git config --global push.followTags true | |
# Make git pull do a --recurse-submodules flag on each pull | |
git config --global submodule.recurse true | |
# Make git push do an on-demand try of pushing sub-modules before pushing main repos | |
git config --global push.recurseSubmodules on-demand | |
# push only current branch on a push |
1. Highlight a recommended option, | |
2. Allow users to switch currency (€/$/£) | |
3. Allow users to switch pricing monthly/yearly | |
4. Keep the entire pricing plan area clickable | |
5. Use slider to calculate how much a user would save | |
6. Provide free first month for good engagement | |
7. Prominently highlight testimonials prominently | |
8. Repeating call to action on top and bottom | |
9. Sell benefits instead of features | |
10. Indicate that users can cancel any time |
#This guide will walk you through the steps needed to setup an empty project using the 2 frameworks into a single repository.
##You will need to have installed:
apache: >= 2.4.9
php: >= 5.5.12
composer: >= 1.2.1
node: >= 4.1.0
npm: >= 3.0.0
git: >= 1.9.5
Once you are ready to hire a developer, what should you do to mitigate execution / build risk?
Writing a good functional specification is key to getting the build phase of this project right. It's not easy to do but it's mostly just about thinking hard and writing out all the boring details of your desired outcome. The best guide for this is Joel Spolsky (recently sold Trello for $425M). He wrote a 4 part series on this, starting here, and also has an example (real) spec on his website here (the PDF link is broken, this is the real one)
Before you start on a spec, trim down your functionality to the absolute bare minimum - and be brutal with it! Imagine you had to complete it in one day, or imagine it was only a single feature... take away everything that isn't fundamental