Madison Futsal would like to move their website, apps and email to a more stable and scalable service. Their current provider is 1&1. The current application instance is not stable and the provider does not offer much in terms of instance management.
| # Your init script | |
| # | |
| # Atom will evaluate this file each time a new window is opened. It is run | |
| # after packages are loaded/activated and after the previous editor state | |
| # has been restored. | |
| # | |
| # An example hack to log to the console when each text editor is saved. | |
| # | |
| # atom.workspace.observeTextEditors (editor) -> | |
| # editor.onDidSave -> |
People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
As a software developer myself, I've found that markdown is the most important tool in my toolbox. It's the glue that holds everything together. It's the key to keeping my projects organized and on track. Every day, I interact with people who build, use, maintain, support or manage the software my team builds. Markdown is the language that allows us to communicate with them. And because it's a content first format, it's the perfect tool for the job. My team uses markdown to write user guides, support docs and readmes. We use it in our pull requests, issues, slack messages and even in our code comments. When we have to write something for confluence so stakeholders can access it, we put it in a markdown file and publish it there. If confluence isn't available, we still have our source code and markdown files to refer to.
I first got acquainted with markdown when I created an account on github in 2010. At the time I was working as the software development man
