Skip to content


markdown libraries

Library Language Website
MkDocs Python
Docusaurus JavaScript
GitBook Multiple Languages
Docsify JavaScript
Hugo Go
Jekyll Ruby
Gatsby JavaScript
VuePress JavaScript
Hexo JavaScript
Bookdown R


Library Website


Utility Description Link
fzf Command-line fuzzy finder used for quickly searching and opening files and directories Link
ripgrep Line-oriented search tool that recursively searches directories for a regex pattern while respecting gitignore rules Link
bat Syntax highlighting cat command Link
fd Simple, fast and user-friendly alternative to find Link
tldr Simplified and community-driven man pages Link
exa Modern replacement for the ls command that provides a long list of information about files Link
entr Runs arbitrary commands when files change Link
ag Code-searching tool similar to grep but faster Link
tokei Code statistics generator Link
youtube-dl Command-line program to download videos from YouTube and other video sites Link
Command Line Utility Description Link
taskwarrior Command-line TODO list manager with a focus on GTD Link
todo.txt-cli Simple, todo.txt-based command line task manager Link
t Simple task tracking on the command line Link
bugwarrior Consolidate bugs from multiple services into one unified database Link
go-todoist Command line tool for todoist Link

command line

Library Name Description
Pandoc A universal document converter that supports Markdown and many other markup languages
grip A GitHub Readme Instant Preview tool that renders Markdown files locally before pushing them to GitHub
markdown-cli A command-line interface for converting Markdown files to HTML or PDF
multimarkdown A lightweight markup processor that supports many different output formats
marked A fast and reliable Markdown parser and compiler
mdcat A command-line utility that provides syntax highlighting and paging for Markdown files
mdp A command-line based markdown presentation tool
cmark A reference implementation of CommonMark, a standardized specification of Markdown syntax

gitlab style guide1

GitLab has a comprehensive style guide that covers various aspects of software development, including coding, testing, and documentation. Here are some key points from the GitLab style guide:

  • Code formatting: GitLab recommends using the standard formatting for the programming language you are using. It also suggests using tools like RuboCop, ESLint, or Prettier to automate formatting.
  • Naming conventions: GitLab suggests using descriptive and meaningful names for variables, functions, and classes. It also recommends using camelCase for variables and functions in JavaScript, and snake_case for variables and functions in Ruby.
  • Comments: GitLab advises developers to write comments that explain why the code is written in a certain way, rather than what the code does. It also recommends avoiding unnecessary comments, such as commenting out code instead of deleting it.
  • Testing: GitLab suggests writing automated tests for your code, including unit tests, integration tests, and end-to-end tests. It also recommends using a testing framework like RSpec or Jest.
  • Documentation: GitLab recommends writing documentation for your code, including README files, inline comments, and API documentation. It also suggests using tools like Swagger to generate API documentation automatically.
  • Security: GitLab advises following secure coding practices, such as avoiding hard-coded passwords, using secure libraries, and validating user input.
  • Code reviews: GitLab recommends using code reviews to ensure code quality and catch potential bugs before they make it into production.

These are just a few key points from the GitLab style guide. For more detailed information, you can check out the GitLab handbook on their website.