Our great sponsors
proselint | docs | |
---|---|---|
9 | 8 | |
4,280 | 1,377 | |
0.6% | 0.2% | |
4.6 | 9.8 | |
4 days ago | 7 days ago | |
Python | Python | |
BSD 3-clause "New" or "Revised" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
proselint
-
Getting Started with Technical Writing
So cool. Looks like the proseline site is down. For anyone else who wanted to read the approach - https://github.com/amperser/proselint/blob/b5b7536bec5fd461e...
-
Writing like a pro with vale & neovim
You can try proselint, which also has built-in support in null-ls. Its LaTeX support isn't perfect, but it's workable.
-
Help with autocompletion for prose writing.
Something like grammar-guard, proselint and/or language-tool?
-
Grammar checker for scientific writing
Yep, though there's not a lot to see! Follow the instructions for installing proselint at https://github.com/amperser/proselint and configure as follows:
-
Is there a reliable Grammarly package for Emacs?
Vale uses a customizable grammar checker, and you can download some open-source configurations to start working with from the link above. Then, you just need to add something like below to your Emacs configuration: (flycheck-define-checker vale "A prose linter" :command ("vale" "--output" "line" source) :standard-input nil :error-patterns ((error line-start (file-name) ":" line ":" column ":" (id (one-or-more (not (any ":")))) ":" (message) line-end)) :modes (markdown-mode org-mode text-mode) ) (add-to-list 'flycheck-checkers 'vale 'append) (setq flycheck-vale-executable "/usr/local/bin/vale") It looks like you can do something similar with Proselint, which looks wonderful and I have been meaning to try using in my day-to-day: https://unconj.ca/blog/linting-prose-in-emacs.html .
-
Markdown Linting
proselint
-
Setting up VIM for blogging
Full list here. Since the tool is a linter, it sounds like it should work with language servers. I use CoC.nvim for LSP features. Thankfully some smart guys have figured out how to make proselint work with coc.nvim & coc-diagnostic (see here). Now it works for my blog posts just like clangd does for my C++ code.
-
novelWriter 1.0
You're looking for proselint. https://github.com/amperser/proselint
docs
-
Question: Best affordable host to have multiple domains?
I can recommend https://linode.com, their documentation is excellent https://www.linode.com/docs/ and ready made images also https://www.linode.com/docs/marketplace/
- Looking to get into designing and maintaining websites. Do you guys have any course recommendations so I can be knowledgeable about all things websites?
- Ask HN: Classic Self-managed web app hosting resources
-
I want to set up a simple blog page, securely.
>In other words, let the machine do your thinking for you No, this was idiotic. A generator tool like Hugo doesn't "think" for you. it's a tool, used by a thinking person. Even if someone new to HTML publishing happens to adopt Hugo, they are going to learn things. By the sounds of it, it's likely they will learn things you have not. They will still learn about HTML and CSS. They may optionally learn about optimizing their HTML and CSS, if it matters for performance of their finished product. Not all sites are the same, after all. The output of Hugo is static HTML (and CSS, js if used, images and other supporting files). The input of Hugo is also static - a collection of HTML templates, CSS and, usually, Markdown text files as the primary content store. Creatively used, Hugo sites can appear as feature-rich as many database-driven sites and in a manner that you simply could not do armed with only an editor, unless your site is only a handful of pages. Any Hugo site can be configured to generate other representations of the site, too, automatically. You probably think that's nonsense, but then again you probably also do not publish a hand--crafted [Atom](https://spf13.com/index.xml) or RSS feed to go along with your hand-crafted HTML. Hand-crafted does not automatically mean better. Even the simplest Hugo site implementation typically makes use of categories or tags (or both) to help readers find other relevant content. Inserting a new page into an existing hierarchy of categories and/or tags is trivial. Edit a file; tag it. The navigation structure is rebuilt, in milliseconds, whether there are five pages or five hundred. [Steve Francia's site](https://spf13.com/) provides examples of these facets in use. With Hugo you can also produce large documentation sites/subsites, and even more importantly, maintain them. The [Let's Encrypt documentation site](https://letsencrypt.org/docs/) is a textbook case study. It's too bad the `vim` project DOES NOT use a tool like Hugo, because then its documentation would stand a chance of being current instead of: > The [VimDoc project](https://www.vim.org/docs.php) has links to various types of Vim documentation. The online, hyperlinked copy of the documentation is currently outdated. Send in the drones to edit. "Currently" has lasted a long time! Another example: [Linode's documentation site](https://www.linode.com/docs/) is generated by Hugo (according to the meta attribute inside, v0.83). You can see the source code for all their documentation, including the site theme and Hugo specifics, here https://github.com/linode/docs. Shocking, isn't it? A tool being used for productivity! You portray using a productivity tool like Hugo as being somehow lazy. That's ridiculous. It's a powerful tool that happens to scale from the simplest of use cases to the complex, and for every use case, makes it possible to produce far richer sites than is possible completely by hand. And all of that without a database or need for a runtime language on a server, or client. A generated Hugo site has no need for PHP includes or other helpers. It can run on the simplest HTTP server; it's just static content. It's a tool, like an editor is a tool, to make an author more productive.
- Akamai to Acquire Linode
-
SSGs through the ages: The ‘Reinvention’ era
Hugo has seen success with corporate customers, including 1Password, Linode Digital.gov, KeyCDN, and Let’s Encrypt, to name just a few. Bjørn Erik Pedersen took over as the lead maintainer in 2015 and continues to lead Hugo’s thriving community.
-
Markdown Linting
Besides the official Vale style guides Buildkite, Linode, and Write The Docs have rules online that you can copy into your repo or use as inspiration for your own rules.
-
Download all of Linode documentation
- https://github.com/linode/docs
What are some alternatives?
vim-pencil - Rethinking Vim as a tool for writing
Sculpin - Sculpin — Static Site Generator
vale - :pencil: A markup-aware linter for prose built with speed and extensibility in mind.
markdownlint - A Node.js style checker and lint tool for Markdown/CommonMark files.
write-good - Naive linter for English prose
markdownlint - Markdown lint tool
novelWriter - novelWriter is an open source plain text editor designed for writing novels. It supports a minimal markdown-like syntax for formatting text. It is written with Python 3 (3.8+) and Qt 5 (5.15) for cross-platform support.
Openly - A Vale linter style that aims to replicate Grammarly in an open-source, privacy-friendly way
lsp-grammarly - lsp-mode ❤️ grammarly
coc-diagnostic - diagnostic-languageserver extension for coc.nvim
vale-styles - Checks for Vale based on popular style guides