Merge branch 'dev' into statusline

.SpaceVim.d/autoload/SpaceVim/dev/releases.vim

@@ -1,5 +1,5 @@
 function! s:body() abort
-    return 'SpaceVim development (pre-release) build.'
+    return 'SpaceVim development (pre-release:' . g:spacevim_version . ') build.'
 endfunction
 
 function! SpaceVim#dev#releases#open() abort

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2016 SpaceVim
+Copyright (c) 2017 SpaceVim
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

autoload/SpaceVim/layers/lang/markdown.vim

@@ -24,7 +24,7 @@ function! SpaceVim#layers#lang#markdown#config() abort
         autocmd BufEnter *.md call s:mappings()
     augroup END
     if executable('firefox')
-        let g:mkdp_path_to_chrome= 'firefox'
+        let g:mkdp_path_to_chrome= get(g:, 'mkdp_path_to_chrome', 'firefox')
     endif
 endfunction
 

docs/_posts/2017-05-31-SpaceVim-Newsletter-A-New-Hope.md

@@ -0,0 +1,9 @@
+---
+title: Newsletter #1 - A New Hope
+categories: newsletter
+excerpt: "A new hope: tern vim/neovim to be an IDE for most languages"
+---
+
+# [newsletter](https://spacevim.org/development#newsletter) > A New Hope
+
+Welcome to the first newsletter for SpaceVim, a project that hopes to tern vim to be an IDE for most languages.

docs/index.md

@@ -52,3 +52,40 @@ git clone https://github.com/SpaceVim/SpaceVim.git vimfiles
 ```sh
 git clone https://github.com/SpaceVim/SpaceVim.git AppData\Local\nvim
 ```
+
+## Features
+
+## News
+
+[Newsletter #1 - A New Hope]()
+>    Published on: 2017-5-31 
+
+More posts are in the [SpaceVim's Blog](https://spacevim.org/blog/)
+
+[Follow @SpaceVim](https://twitter.com/SpaceVim) 
+
+## Impressions
+
+## Get Involved
+
+Discuss the project at [gitter.im/SpaceVim](https://gitter.im/SpaceVim/SpaceVim), IRC (**#spacevim** on **irc.freenode.net**) or the [mailing list](https://groups.google.com/forum/#!forum/spacevim). 
+
+Contribute code, report bugs and request features at [GitHub](https://github.com/SpaceVim/SpaceVim). 
+
+## FAQ
+
+1. What is the project status?
+
+The current stable version is 0.2.0. See the milestones page for development progress and the roadmap for high-level plans.
+
+2. Is SpaceVim trying to turn Vim/Neovim into an IDE?
+
+With layers feature, this [version]() of vim distribution to tern vim/neovim into an IDE for many language.
+
+3. Will SpaceVim deprecate Vimscript?
+
+No, the custom configration file is written in vim script.
+
+4. Which version of vim/neovim is needed?
+
+vim 7.4/neovim v0.1.7 

docs/roadmap.md

@@ -0,0 +1,35 @@
+---
+title:  "Roadmap"
+---
+
+# Roadmap
+
+The roadmap and [milestones](https://github.com/SpaceVim/SpaceVim/milestones) define the project direction and priorities.
+
+## Current
+
+### [0.3](https://github.com/SpaceVim/SpaceVim/milestone/3)
+- statusline with mode support
+- Plugin manager ui for dein
+
+## Meta
+
+There are release milestones and meta milestones ("buckets"). 
+
+- Version-number milestones (0.1, 0.2, 0.3, …) assign issues to production releases.
+    - The nearest upcoming version is assigned a target date.
+    - Low-risk fixes in the current branch are first committed to the stable branch, then merged to master. For example, if the current stable release is `0.1.1` and a bug-fix is assigned to the `0.2` milestone, it does not mean users need to wait until 0.2 to get the fix. The patch will be committed to the stable branch and released in `0.1.2`. 
+- [todo](https://github.com/SpaceVim/SpaceVim/milestone/4) is a bucket for triaged tickets which should be on the roadmap but cannot yet be assigned to a concrete milestone.
+- [unplanned](https://github.com/SpaceVim/SpaceVim/milestone/5) is a bucket for low-priority items or items lacking a feasible path to completion.
+
+## Completed
+
+### [0.2](https://github.com/SpaceVim/SpaceVim/milestone/2)
+- Mnemonic key bindings
+- Denite support
+- Unite work flow
+- Windows support
+
+### [0.1](https://github.com/SpaceVim/SpaceVim/milestone/1)
+- The primary goal of the 0.1 release ("first public release") is to reach a stable, functional baseline that can be built upon and used as a benchmark for further progress.
+- Layers feature