| Quant Agency |
|
| Website of a creative agency. | |
| Cyfe |
|
| All in one dashboard. | |
| Sublime Text Desktop Wallpaper |
|
| SublimeText cheatsheet that you can print and put on the wall. | |
| Makefile tutorial |
|
| The good old makefiles still kicks, this cheatsheet can help catching up with the original Makefile way. | |
| Helium |
|
| Hardware and software to connect things to your cloud. | |
| Random useful website |
|
| Click the button, and get to a random more or less useful website. Perfect for procrastination. | |
| Graphana 2.1 |
|
| A lot of improvement in that new version. | |
| Postcss |
|
| Transforming CSS with JS plugins. | |
| TODO-show package |
|
| Atom plugin to find all the TODO, FIXME, CHANGED, ... comments in your project. | |
| PeerVPN |
|
| Virtual ethernet networks between multiple computers. | |
| Now UI Kit |
|
| A cross-platform UI kit for photoshop or sketch. | |
| Writing a Mumble Bot in Ruby |
aug 2
|
| The gem mumble-ruby provides a library to connect and interact with Mumble as a client. | |
| A Recipe for Rails Continuous Integration |
aug 3
|
| Matt shares the script he uses for his own Rails projects, and the reasoning behind it. | |
| How Rails fancy exception page works |
aug 3
|
| How error pages work in rails. | |
| How I Learned to Program in Elixir |
aug 4
|
| Joseph explains how he jumped into Elixir. | |
| Understanding and Using Ruby Rake |
aug 5
|
| Rake, how it works and what you will find yourself using it for. | |
| CSS: Why we need localized constants |
aug 5
|
| Discussion about the need for CSS to evolve in a more programmatic way. | |
| Responsive Solutions for Feature Comparison Tables |
aug 5
|
| The markup is rendered on the server and fed to the browser as complete HTML. | |
| Creating Isomorphic Apps with Node.js, React, and Express |
aug 5
|
| The markup is rendered on the server and fed to the browser as complete HTML. | |
| Browser Trends August 2015: Chrome Exceeds 50% |
aug 5
|
| Worldwide Desktop & Tablet Browser Statistics. | |
| Is There a Perfect Paragraph Length for the Web? |
aug 5
|
| The general consensus has been getting shorter for 200 years. | |
| Patching Rails Performance |
aug 6
|
| In a recent patch we improved Rails response time by >10%, our largest improvement to date. | |
| JWT with Rails, Sorcery and AngularJS |
aug 6
|
| JWT is being favored over the classic cookie scheme in Single Page Applications. | |
| Phoenix for Railsies |
aug 6
|
| Phoenix is a web framework in Elixir, here presented from the rails point of view. | |
| Ruby Occurrence Counting |
aug 7
|
| Some benchmarks on what is the fastest method for counting things. | |
| JSChannel 2015 (13 videos) |
aug 3
|
| 17-18 July 2015 in Bangalore | |
| JRuby Conf EU 2015 (11 videos) |
aug 8
|
| 31 july in Postdam | |
I'm currently involved in a community project and I installed a wordpress. From time to time I get one up to see how it evolves. But really this thing is not to my taste. To much trouble for making simple things. I reckon it can be useful for people with no technical knowledge but then they are going to mess up everything. The technical advisor still can't be avoided.
So because now I saw a recent wordpress and didn't like it more than the previous attempts, I will give a try to the new octopress 3.0. The octopress author explains that he's been doing it all wrong and now on version 3.0 he gets back to sort of a collection of gems that plug into jekyll. I kind of like the idea.
Well to be honest I was also tempted to give a try to phoenix, but I know jekyll already and I don't have that much server resources for that community project. Static web always have had my preference. But the idea behind Phoenix is appealing. Like any new project it includes the new things and don't have to bother about legacy. The channels ideas, creating a stream between client and server, sounds very appealing.
But to get back to why I will prefer jekyll over wordpress, is that my contributors are a mess. They don't care about styling, they copy-paste random html all over the place and the final look is totally inconsistent. My hope is that markdown would limit the possibilities of making a mess. But then I will have to propose them the github edit, as a backend, unless I cheat and use etherpad-lite as a pre-production backend.
That etherpad-lite thing is amazingly simple, I used sometimes and making it accessible behind a single password for everybody makes tings pretty direct. But totally unsafe, I reckon. I will probably have to write some kind of tool for managing the publication workflow. Hmm, that sounds like fun. If you ever had the same kind of adventure, please share with me :)
