FAQtory
FAQtory is a tool to auto-generate a FAQ.md (Frequently Asked Questions) document for your project.
Additionally, a "suggest" feature uses fuzzy matching to reply to GitHub issues with suggestions from your FAQ.
Getting started
Faqtory is best installed via pipx to avoid any dependency conflicts:
pipx install faqtory
Run the following from the directory you wish to store the FAQ document.
faqtory init
This will create the following files and directories:
faq.ymlA configuration file which you can edit../.faq/A directory which will contain templates../questions/A directory containing question documents.
Adding questions
To add questions create a file with the extension .question.md in the questions directory (./questions/ if you are using the defaults).
Question documents are Markdown with front-matter. Here's an example:
---
title: "What does FAQ stand for?"
alt_titles:
- "What is the meaning of FAQ?"
- "What does FAQ mean?"
---
FAQ stands for *Frequently Asked Questions*
The filename is unimportant, but a title is mandatory. You can also optionally add alternative titles under alt_titles which will be used with the faqtory suggest feature (but not displayed).
Building
Run the following command to build the FAQ:
faqtory build
With the default settings this will generate an FAQ.md file.
Suggest
The "suggest" subcommand can compile a list of FAQ entries that match a supplied issue title. Here's an example:
faqtory suggest "who is the author of FAQtory?"
This will generate a list of matching entries from the FAQ, and write Markdown to stdout. You can modify the output with the "suggest.md" template, which you will find in your ".faq/" directory (if you haven't configured it elsewhere),
This feature is designed to be used with a GitHub action to post an automated response. To enable this feature, copy new_issue.yml to a similarly named directory in your repository.
Disclaimer
This was a hastily put together tool by a maintainer that was tired of responding to the same old issues. I can't devote much time to this project, but I will happily accept PRs!
Metadata
Release files for faqtory 1.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| faqtory-1.1.3.tar.gz | 5.9 kB | Without provenance | Details for faqtory-1.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| faqtory-1.1.3-py3-none-any.whl | Python 3 | none | any | Details for faqtory-1.1.3-py3-none-any.whl |
Total release size: 13.4 kB
Release files / faqtory-1.1.3.tar.gz
| Download URL | faqtory-1.1.3.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd8686668e946d371d8cdc4dd43ef861b4018a3cd12314aa7a0fa768805f388a
|
|
BLAKE2b-256 checksum How to use checksums |
51b402695d5b202d17a471cb19478cd2534a7a3a094611d8240cdcf067c8bf8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.5 Darwin/23.2.0
|
Release files / faqtory-1.1.3-py3-none-any.whl
| Download URL | faqtory-1.1.3-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
391c56338334697b9c73b8e463d6b255e23c88d0f5966beff6ddb06f656af665
|
|
BLAKE2b-256 checksum How to use checksums |
320554a59e3b3fd2cef581468a64a9c3aa950b945890d3bd02aba80ed5bcc64a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.5 Darwin/23.2.0
|
Security for faqtory 1.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.