Sublime is my favourite text editor. Python, Bash, Markdown, C++, html... you name it. It can even handle Matlab!
## Why I love Sublime
What I particularly love about [Sublime](https://www.sublimetext.com/download) is that I can switch between different languages very comfortably), and it takes care of everything the same way, no matter what you are writing. It handles the colours, the spacing, the formatting/syntax, [linting](https://en.wikipedia.org/wiki/Lint_(software)), the keyboard shortcuts, autocompletions, commenting, spell checking, searching / find+replace across multiple files, all the important stuff! You can also use the companion software "Sublime Merge" to use Sublime with Git.
You must think "WOW, this is incredible! And is it Open Source?"
Well, no it is not.
Now you must wonder why I am advertising for Sublime on a website which advocate for open source. Well since Atom has been [discontinued](https://github.blog/2022-06-08-sunsetting-atom/), we must find alternatives that have comparable options.
This is why, on this page I will list text editors that are, for me, good alternatives to Atom.
Please contact us if you know other great alternatives :)
## Why you should use Text editors
To host your documentation on GitHub pages, you're going to be writing across multiple documents, and potentially in more than one language. Best are text editors which also have a directory tree that enables you to navigate around your project file easily.
Good text editors also provide a graphical point-and-click way of committing changes to your GitHub repo. This can be useful if you're not familiar with the process, but for these tutorials we're going to stick to command line and the terminal for GitHub, because you get more informative error reports.
## Other good text editors
If you want to use a good open science text editor (and you should!). You might want to try [Vim](https://www.vim.org/download.php). This powerful text editor is available on Windows, Linux and MacOS. Although git is not directly build in the software, you can find a lot of Git plugins that will satisfy you.
Atom is my fave editor for all types of "code". Python, bash, markdown, html... I've not tried with LaTeX, but I wouldn't be surprised if it can handle that. My guess is it probably can't handle MATLAB, but that's cool.
## Why I love Atom
Same can be said about [Geany](https://geany.org/) which bear the same characteristics! And several git plugins for Geany exists as well!!!
What I particularly love about Atom is that I can switch between different languages very comfortably), and Atom takes care of everything the same way, no matter what you are writing. It handles the colours, the spacing, the formatting, [linting](https://en.wikipedia.org/wiki/Lint_(software)), the keyboard shortcuts, autocompletions, commenting, spell checking, searching / find+replace across multiple files, all the important stuff! I guess that is what you get from an open source tool developed by and for users who write code for a living! Other tools are available which I'm sure do a great job, but this is the one I am most comfortable with and consistently pleased by.
## Why you should use Atom
You can also use Microsoft Visual Studio (BOOOOOOOOOOOOOH - sorry, I went through terrible nights trying to make a C#/C++ software work).
To host your documentation on GitHub pages, you're going to be writing across multiple documents, and potentially in more than one language. Atom also has a directory tree on the left which enables you to navigate around your project file easily, and also do things like create, duplicate and delete files using good old point-and-click.
The most important is that you must feel confortable using a text editor. Try several of them and do not be afraid to change, most of them have the same qualities!
Atom also provides a graphical point-and-click way of committing changes to your GitHub repo. This can be useful if you're not familiar with the process, but for these tutorials we're going to stick to command line and the terminal for GitHub, because you get more informative error reports.
## How to start with Atom
Before we crack on with creating and editing documentation, I'd love for you to get familiar with working in Atom. Here's a short video which shows you how to [install and start using Atom](https://www.youtube.com/watch?v=EyG20hhON6E).
There are tones of packages you can add on to make your workflow easier, but for these tutorials you'll only need the markdown basics which come preloaded.
