Markup language: Markup language is used to write documents in a way that distinguishes them from plain text. Most SSGs utilize lightweight markup languages, such as Markdown. However, alternatives like AsciiDoc, Textile, and ReStructuredText are also used. These lightweight languages simplify content creation and are converted into HTML during the site generation process. - Source: dev.to / 8 months ago

Uses Sphinx, reStructuredText And the sphinx-rtd-theme for writing, building And rendering the documentation. Source: 9 months ago

If we're dreaming, ReStructed Text support. Source: about 1 year ago

You can always switch to rst¹ and sphinx² to produce html/pdf came join the dark side, we have tables³ :) 1. https://docutils.sourceforge.io/rst.html. - Source: Hacker News / over 1 year ago

ReStrutucturedText is still useful to look at for inspiration here. It had the concepts of extensible metadata ("field lists"), spans ("interpreted text"), and blocks ("directives"). Including things like applying metadata to spans (using essentially Footnotes to provide field lists to interpreted text sections, like but better than Markdown's reference style for hyperlinks which almost no one uses but were much... - Source: Hacker News / almost 2 years ago

Eslint: It analyzes our code to quickly find problems. We will use the default setup provided by Vite. - Source: dev.to / 13 days ago

A big part of my work revolves around JavaScript tooling, and as such it's important to keep an eye on the ecosystem and see where things are going. It's no secret that recently lots of projects are native-ying (??) parts of their codebase, or even rewriting them to native languages altogether. Esbuild is one of the first popular and successful examples of this, which was written in Go. Other examples are Rspack... - Source: dev.to / 16 days ago

ESLint: A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. - Source: dev.to / about 1 month ago

Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency. - Source: dev.to / about 1 month ago

If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem. - Source: dev.to / about 2 months ago