|
You are here |
www.miketheman.net | ||
| | | | |
takeonrules.com
|
|
| | | | | The following article is specific to Software Services by Scientist.com ?? . While the specifics are for my day job, the general approach is something I find useful to share. In this playbook article we'll list the steps to take when upgrading. We'll also mention some of our conventions and how to build a checklist from those conventions. | |
| | | | |
avelino.run
|
|
| | | | | I constantly hear people saying that to contribute to an Open Source project you need to be able to program very well, have a lot of knowledge, be able to handle code criticism, etc. I see the above statements as excuses and focus in the wrong place. In the last few months, I haven't had as much time to contribute to open source projects as I like (writing code), but that didn't stop me from contributing. Actually, the lack of priority (not lack of time) has made me contribute by reporting problems that I run into in the projects/software I use in my day-to-day life and this has been more work than writing code with a defined specification (issue that someone invested time detailing). | |
| | | | |
stuartsierra.com
|
|
| | | | | ||
| | | | |
roneo.org
|
|
| | | Note: You need to run Hugo ? 0.81, and Hugo 0.108.0 provides interesting improvements on this topic Enable Markdown Attributes In config.toml [markup.goldmark.parser.attribute] block = true title = true or in config.yml markup: goldmark: parser: attribute: block: true title: true Usage Add a single class:  {.custom-css-class} Add multiples classes:  {.myclass class="custom-css-class1 custom-class2"} Example This picture surrounded by a frame is the result of this image together with some CSS and the following markup: | ||