On Fri, Oct 20, 2017 at 10:05 PM, Paul W. Frields <stickster(a)gmail.com>
On Fri, Oct 20, 2017 at 12:53:50AM +0530, Jogender Kvs wrote:
> Hello all,
> On Thu, Oct 5, 2017 at 12:17 AM, Paul W. Frields <stickster(a)gmail.com>
> > On Tue, Oct 03, 2017 at 11:57:25PM +0530, Jogender Kvs wrote:
> > > Hi,
> > > I would like to write the following article:
> > >
> > > Summary: Install Visual Studio Code in Fedora
> > > Description: This article is aimed to tell viewers about a powerful
> > source
> > > code editor i.e. Visual Studio Code and can they install it in their
> > > system. After this the article will also guide you through certain
> > > that the viewers can follow after the installation. The general
> > > is as follow:
> > > • What is Visual Studio Code? And its Advantages
> > > • How to install Visual Studio Code
> > > • After installation – Some useful commands
> > > • Installing Packages
> > > • Themes
> > >
> > > If you like the idea then please let me know.
> > Hearty +1 on this idea. A couple ideas:
> > * In talking about VSCode and advantages, definitely explain its open
> > source nature. (Does it have a community of non-MS contributors?
> > etc.)
> > * How does it compare to using something like Atom or even standard
> > Vim/Emacs?
> @Paul, thanks a lot for the suggestions, I have worked on the same.
> I have explained the open source nature of the editor, and am not sure if
> there is a community of non-MS contributors, but there are surely other
> non-MS developers contributing to the same.
> I have added my pitch here and am yet to add the comparative study of
> the editors, to hero VSCode :)
>  https://fedoramagazine.org/wp-admin/post.php?post=19105&action=edit
I quite like this article. Here are some tips for you to try in
tuning up the draft a bit:
* Try to eliminate "we" or "I" in articles. Instead, just give
command-style instructions where needed, like "Type the following
* Describe a bit more beyond the simple file and theme functions. Can
you show the debugger and the git integration a little more fully?
Thanks and we look forward to reading your revisions!
@Paul, I have worked on the suggested changes.
Please review the same. Thanks again for your time.