adr-tools
pandoc-templates
adr-tools | pandoc-templates | |
---|---|---|
3 | 4 | |
4,679 | 74 | |
- | - | |
0.0 | 0.0 | |
8 months ago | about 2 years ago | |
Shell | Shell | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
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.
adr-tools
-
What tools do you use to plan software features?
For architectural decisions I have used this in the past: https://github.com/npryce/adr-tools
- More persistent and less frenetic communication: alternatives to Slack
-
Documenting Software Architecture Decisions
👍 This approach is becoming more popular. It's a great way to document decisions and, for many teams, is a core part of their documentation bundle. ADRs don't take very long to put together, but they are incredibly useful to look back on, to help tell stories about how/why things changed, etc. Definitely recommended if you're not using them already, and Nat Pryce's adr-tools tool is an easy way to get started.
pandoc-templates
-
Strange Machines: An Anthology of Dark User Manuals
Also anyone can write a story in markdown then run it through a Pandoc template: https://github.com/prosegrinder/pandoc-templates
-
Manuscript format in other languages?
What inspired the question was this script that helps you format your manuscript: https://github.com/prosegrinder/pandoc-templates
-
How do you format a script to send to agents/publishers?
Automation if you're computer savvy: https://github.com/prosegrinder/pandoc-templates
-
Always write notes for your story ideas. Especially if you’re not writing them yet. Holy crap
Rich text/WYSIWYG editing will only get in your way when you're writing standard fiction without multimedia elements or weird typesetting, and even in those cases it's arguably not the right way to go while you're still working on your manuscript. Tools like Pandoc make it easy enough to compile sets of Markdown files into any kind of .docx-based manuscript format you like (e.g. using scripts like these) or reasonably attractive epubs using some simple CSS.
What are some alternatives?
log4brains - ✍️ Log and publish your architecture decisions (ADR)
pandoc-from-markdown-to-pdf - Use pandoc to convert from markdown to PDF with our preferred options
udoxy - Guidelines and script (bash) for generic standalone code documentation
pandoc - Universal markup converter
standard-readme - A standard style for README files
Zettlr - Your One-Stop Publication Workbench
jellyfin-docs - Documentation for Jellyfin
nb - CLI and local web plain text note‑taking, bookmarking, and archiving with linking, tagging, filtering, search, Git versioning & syncing, Pandoc conversion, + more, in a single portable script.
github-action-markdown-link-check - Check all links in markdown files if they are alive or dead. 🔗✔️
pandoc-markdown-latex-pdf - Example of how to produce scientific, academic, and technical PDF documents such as essays, reports, or thesis by writing Markdown and converting with Pandoc via LaTeX. We also included build and release automation with GitHub actions.
docs - Rundeck documentation
EMBA - EMBA - The firmware security analyzer