#SHAREX SCREENSHOT WITHOUT BORDER UPDATE#

I would then upload the images to TinyPNG to compress them, and download the compressed images. I would do those and then give all the images proper, descriptive names - both for own sanity, but also to help SEO. Some images would require annotation, for example, to highlight a certain area. Once I am done with the blog post, I would then go back to the images folder.

#SHAREX SCREENSHOT WITHOUT BORDER UPDATE#

!(), in my markdown document as a placeholder so I can remember to update it with the correct path to the image. When I took a screenshot, I would place an empty markdown image tag, i.e. It would use random names for these screenshots, e.g.

Until I started looking at optimising this screenshot process, what would happen was that I would take a screenshot in ShareX which would then save it to a sub-folder in my Documents folder. I also take these screenshots as I progress with writing the blog post and the source code, as I find this the least interrupting to my “flow”. These screenshots will typically be of the Visual Studio IDE, the web browser, the command line prompt, etc. While doing this, I will also take a bunch of screenshots to demonstrate certain things. I will write the blog post and the source code in tandem, so both progress at the same time. I will however typically create a new GitHub repository with a project which demonstrates whatever is being discussed in the blog post. When writing a blog post, I will typically already have a piece of code somewhere which demonstrates (at least in broad terms) what I want to blog about, since I usually blog about issues I come across during my daily software development. So the markdown file for this blog post is located at /content/blog/-using-sharex-for-blogging-screenshots.md and all the images are located in the folder /assets/images/-using-sharex-for-blogging-screenshots. using-sharex-for-blogging-screenshots.md

Sharex screenshot without border