papers-cli 2.16__tar.gz → 2.17__tar.gz

papers_cli-2.17/.github/workflows/docs.yml

@@ -0,0 +1,34 @@
+name: docs
+
+on:
+  push:
+    branches: [master]
+    paths:
+      - "docs/**"
+      - "mkdocs.yml"
+      - "README.md"
+      - ".github/workflows/docs.yml"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.x"
+      - name: Cache mkdocs-material assets
+        uses: actions/cache@v4
+        with:
+          key: mkdocs-material-${{ github.sha }}
+          path: .cache
+          restore-keys: |
+            mkdocs-material-
+      - run: pip install .[docs]
+      - run: mkdocs gh-deploy --force

papers_cli-2.17/.github/workflows/pypi.yml

@@ -0,0 +1,47 @@
+# Publishes to PyPI on tag push (e.g. v2.16.1).
+# If this job fails with "400 Bad Request", the package may still be on PyPI: that usually
+# means the workflow ran twice (e.g. tag pushed twice or job re-run) and the second upload
+# failed because the version already exists. Use verbose: true output to see the real error.
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - 'v*'
+
+jobs:
+  build-and-publish:
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+    permissions:
+      id-token: write  # This is required for OIDC
+      contents: read
+
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v6
+
+    - name: Set up Python
+      uses: actions/setup-python@v6
+      with:
+        python-version: '3.x'
+
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install build
+
+    - name: Build distribution
+      # PEP 517 build: resolves build-system.requires from pyproject.toml in an
+      # isolated environment (the legacy `setup.py sdist` path fetched the newest
+      # setuptools_scm without its dependencies and broke when it split out
+      # vcs-versioning)
+      run: |
+        python -m build
+
+    - name: Publish to PyPI
+      uses: pypa/gh-action-pypi-publish@release/v1
+      with:
+        # Show full PyPI error (e.g. "400 File already exists") when upload fails
+        verbose: true

{papers_cli-2.16 → papers_cli-2.17}/.github/workflows/release.yml

@@ -13,7 +13,7 @@ jobs:
 
     steps:
     - name: Checkout code
-      uses: actions/checkout@v4
+      uses: actions/checkout@v6
       with:
         fetch-depth: 0  # Fetch all history for changelog generation
 

{papers_cli-2.16 → papers_cli-2.17}/.github/workflows/tests.yml

@@ -13,9 +13,9 @@ jobs:
         python-version: [ "3.9", "3.10", "3.11", "3.12", "3.13", "3.14", "3.14t"  ]
 
     steps:
-    - uses: actions/checkout@v5
+    - uses: actions/checkout@v6
     - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v5
+      uses: actions/setup-python@v6
       with:
         python-version: ${{ matrix.python-version }}
     - name: Install dependencies

{papers_cli-2.16 → papers_cli-2.17}/.gitignore

@@ -9,7 +9,10 @@ papers/_version.py
 dist/
 .coverage
 htmlcov/
-.venv
+.venv*
 .pytest_cache
 papers.sublime-project
-papers.sublime-workspace
+papers.sublime-workspace
+site/
+notes/
+dummy_library.bib

papers_cli-2.17/PKG-INFO

@@ -0,0 +1,112 @@
+Metadata-Version: 2.4
+Name: papers-cli
+Version: 2.17
+Summary: utilities to keep your PDF library organized
+Author-email: Mahé Perrette <mahe.perrette@gmail.com>
+License: MIT
+Project-URL: homepage, https://github.com/perrette/papers
+Project-URL: Documentation, https://perrette.github.io/papers/
+Keywords: bibtex,references,bibliography
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyMuPDF
+Requires-Dist: unidecode
+Requires-Dist: crossrefapi
+Requires-Dist: bibtexparser>=2.0.0b2
+Requires-Dist: scholarly
+Requires-Dist: rapidfuzz
+Requires-Dist: python-slugify
+Requires-Dist: bs4
+Requires-Dist: platformdirs
+Provides-Extra: docs
+Requires-Dist: mkdocs<2,>=1.5; extra == "docs"
+Requires-Dist: mkdocs-material>=9.5; extra == "docs"
+Requires-Dist: mkdocs-include-markdown-plugin>=6.0; extra == "docs"
+Dynamic: license-file
+
+# papers
+
+[![pypi](https://img.shields.io/pypi/v/papers-cli)](https://pypi.org/project/papers-cli)
+[![python](https://img.shields.io/badge/python-3.9-blue.svg)]()
+[![python](https://img.shields.io/badge/python-3.14t-blue.svg)]()
+[![test](https://github.com/perrette/papers/workflows/CI/badge.svg?query=branch%3Amaster)](https://github.com/perrette/papers/actions)
+[![docs](https://img.shields.io/badge/docs-perrette.github.io%2Fpapers-blue)](https://perrette.github.io/papers/)
+
+Command-line tool to manage your bibliography (PDFs + BibTeX).
+
+Disclaimer: This tool requires further development and testing, and might never
+be fully production-ready (contributors welcome). \
+That said, it is becoming useful :)
+
+<!-- intro-start -->
+A light-weight, command-line bibliography management tool built like `git`,
+with a main command `papers` and a range of subcommands. It lets you:
+
+- **Maintain a PDF library** with appropriate, customisable file naming.
+- **Maintain one or several BibTeX collections**, linked to their PDFs.
+- **Fetch metadata from the internet** — enough PDF-parsing capability to pull
+  metadata from [crossref](https://github.com/CrossRef/rest-api-doc) (by DOI or
+  fulltext search) or google scholar.
+- **Search and act on your library** with a `find`/`grep`-inspired
+  `papers list` (tag, edit, delete, rename, fetch, deduplicate).
+- **Stay in control** — plain BibTeX files, optional git tracking, and
+  undo/redo for every change.
+<!-- intro-end -->
+
+## 📖 Documentation
+
+Full documentation lives at **<https://perrette.github.io/papers/>**:
+
+- [Installation](https://perrette.github.io/papers/installation/) (incl. external dependencies)
+- [Quickstart](https://perrette.github.io/papers/quickstart/)
+- [Adding entries](https://perrette.github.io/papers/adding-entries/)
+- [Listing and searching](https://perrette.github.io/papers/listing/)
+- [Renaming files and keys](https://perrette.github.io/papers/renaming/)
+- [Configuration and install](https://perrette.github.io/papers/configuration/)
+- Also: [managing your library](https://perrette.github.io/papers/library-management/),
+  [git integration](https://perrette.github.io/papers/git/),
+  [undo/redo](https://perrette.github.io/papers/undo-redo/),
+  [features](https://perrette.github.io/papers/features/)
+
+## Install
+
+```bash
+pip install papers-cli
+```
+
+Note there is another project registered on PyPI as `papers`, hence
+`papers-cli` for command-line-interface. See the
+[installation page](https://perrette.github.io/papers/installation/) for
+external dependencies.
+
+## Quickstart
+
+```bash
+# extract metadata from a PDF and add it to your library
+papers add esd-4-11-2013.pdf --rename --copy --bibtex papers.bib --filesdir files
+
+# list and search your library
+papers list perrette scaling approach sea level
+```
+
+See the [quickstart](https://perrette.github.io/papers/quickstart/) for a full
+walkthrough.
+
+Consult inline help (`papers --help`, `papers <command> --help`) for more
+detailed documentation.
+
+## From the same author
+
+A few other open-source tools I maintain.
+
+**Scientific writing & data**
+
+- [**texmark**](https://perrette.github.io/texmark/) — write scientific articles in Markdown and convert them to journal-ready LaTeX/PDF.
+- [**datamanifest**](https://perrette.github.io/datamanifest/) — declarative, reproducible dataset management. *(See also the [datamanifest.toml](https://perrette.github.io/datamanifest.toml/) format spec and the [DataManifest.jl](https://awi-esc.github.io/DataManifest.jl/) Julia port.)*
+
+**Speech to Text (dictate) and Text to Speech (read-aloud) tools**
+
+- [**scribe**](https://perrette.github.io/scribe/) — speech-to-text dictation.
+- [**bard**](https://perrette.github.io/bard/) — text-to-speech reader.

papers_cli-2.17/README.md

@@ -0,0 +1,84 @@
+# papers
+
+[![pypi](https://img.shields.io/pypi/v/papers-cli)](https://pypi.org/project/papers-cli)
+[![python](https://img.shields.io/badge/python-3.9-blue.svg)]()
+[![python](https://img.shields.io/badge/python-3.14t-blue.svg)]()
+[![test](https://github.com/perrette/papers/workflows/CI/badge.svg?query=branch%3Amaster)](https://github.com/perrette/papers/actions)
+[![docs](https://img.shields.io/badge/docs-perrette.github.io%2Fpapers-blue)](https://perrette.github.io/papers/)
+
+Command-line tool to manage your bibliography (PDFs + BibTeX).
+
+Disclaimer: This tool requires further development and testing, and might never
+be fully production-ready (contributors welcome). \
+That said, it is becoming useful :)
+
+<!-- intro-start -->
+A light-weight, command-line bibliography management tool built like `git`,
+with a main command `papers` and a range of subcommands. It lets you:
+
+- **Maintain a PDF library** with appropriate, customisable file naming.
+- **Maintain one or several BibTeX collections**, linked to their PDFs.
+- **Fetch metadata from the internet** — enough PDF-parsing capability to pull
+  metadata from [crossref](https://github.com/CrossRef/rest-api-doc) (by DOI or
+  fulltext search) or google scholar.
+- **Search and act on your library** with a `find`/`grep`-inspired
+  `papers list` (tag, edit, delete, rename, fetch, deduplicate).
+- **Stay in control** — plain BibTeX files, optional git tracking, and
+  undo/redo for every change.
+<!-- intro-end -->
+
+## 📖 Documentation
+
+Full documentation lives at **<https://perrette.github.io/papers/>**:
+
+- [Installation](https://perrette.github.io/papers/installation/) (incl. external dependencies)
+- [Quickstart](https://perrette.github.io/papers/quickstart/)
+- [Adding entries](https://perrette.github.io/papers/adding-entries/)
+- [Listing and searching](https://perrette.github.io/papers/listing/)
+- [Renaming files and keys](https://perrette.github.io/papers/renaming/)
+- [Configuration and install](https://perrette.github.io/papers/configuration/)
+- Also: [managing your library](https://perrette.github.io/papers/library-management/),
+  [git integration](https://perrette.github.io/papers/git/),
+  [undo/redo](https://perrette.github.io/papers/undo-redo/),
+  [features](https://perrette.github.io/papers/features/)
+
+## Install
+
+```bash
+pip install papers-cli
+```
+
+Note there is another project registered on PyPI as `papers`, hence
+`papers-cli` for command-line-interface. See the
+[installation page](https://perrette.github.io/papers/installation/) for
+external dependencies.
+
+## Quickstart
+
+```bash
+# extract metadata from a PDF and add it to your library
+papers add esd-4-11-2013.pdf --rename --copy --bibtex papers.bib --filesdir files
+
+# list and search your library
+papers list perrette scaling approach sea level
+```
+
+See the [quickstart](https://perrette.github.io/papers/quickstart/) for a full
+walkthrough.
+
+Consult inline help (`papers --help`, `papers <command> --help`) for more
+detailed documentation.
+
+## From the same author
+
+A few other open-source tools I maintain.
+
+**Scientific writing & data**
+
+- [**texmark**](https://perrette.github.io/texmark/) — write scientific articles in Markdown and convert them to journal-ready LaTeX/PDF.
+- [**datamanifest**](https://perrette.github.io/datamanifest/) — declarative, reproducible dataset management. *(See also the [datamanifest.toml](https://perrette.github.io/datamanifest.toml/) format spec and the [DataManifest.jl](https://awi-esc.github.io/DataManifest.jl/) Julia port.)*
+
+**Speech to Text (dictate) and Text to Speech (read-aloud) tools**
+
+- [**scribe**](https://perrette.github.io/scribe/) — speech-to-text dictation.
+- [**bard**](https://perrette.github.io/bard/) — text-to-speech reader.

papers_cli-2.17/docs/adding-entries.md

@@ -0,0 +1,61 @@
+# Adding entries
+
+The `papers add` command adds entries to your library, with or without a PDF
+attachment.
+
+## Add a PDF (extract metadata automatically)
+
+```
+$> papers add esd-4-11-2013.pdf --rename --copy --bibtex papers.bib --filesdir files --info
+INFO:papers:found doi:10.5194/esd-4-11-2013
+INFO:papers:new entry: perrette_landerer2013
+INFO:papers:mv /home/perrette/playground/papers/esd-4-11-2013.pdf files/perrette_et_al_2013_a-scaling-approach-to-project-regional-sea-level-rise-and-its-uncertainties.pdf
+INFO:papers:renamed file(s): 1
+```
+
+That is equivalent to doing:
+
+```
+papers extract esd-4-11-2013.pdf > entry.bib
+papers add entry.bib --bibtex papers.bib --attachment esd-4-11-2013.pdf --rename --copy
+```
+
+See [Renaming files and keys](renaming.md) for how to specify file naming
+patterns.
+
+## Add a whole directory of PDFs
+
+It is possible to do this on a full directory of files, recursively:
+
+```
+papers add --rename --recursive /home/perette/playground/papers/papers_test
+```
+
+where, above, the `papers_test` directory contains a few PDF files. For each
+PDF, `papers` will attempt to extract the metadata and add the relevant file to
+the bibliography, and rename files into the files directory.
+
+## Add an entry from its DOI
+
+If you already know the DOI of a PDF, and don't want to gamble the fulltext
+search and match, you can indicate it via `--doi`:
+
+```
+papers add esd-4-11-2013.pdf --doi 10.5194/esd-4-11-2013 --bibtex papers.bib
+```
+
+The `add` command above also works without any PDF (create a bibtex entry
+without file attachment):
+
+```
+papers add --doi 10.5194/esd-4-11-2013 --bibtex papers.bib
+```
+
+## Add an entry without DOI from bibtex + PDF
+
+Some old files don't have a DOI. The best approach is to add the entry from its
+bibtex:
+
+```
+papers add entry.bib --attachment esd-4-11-2013.pdf
+```

papers_cli-2.17/docs/comparison.md

@@ -0,0 +1,25 @@
+# Comparison with other tools
+
+## Why not JabRef, Zotero or Mendeley (or...) ?
+
+- JabRef (2.10) is nice, light-weight, but is not so good at managing PDFs.
+- Zotero (5.0) features excellent PDF import capability, but it needs to be done
+  manually one by one and is a little slow. Not very flexible.
+- Mendeley (1.17) is perfect at automatically extracting metadata from
+  downloaded PDFs and managing your PDF library, but it is not open source, and
+  many issues remain (own experience, Ubuntu 14.04, Desktop Version 1.17):
+    - very unstable
+    - PDF automatic naming is too verbose, and sometimes the behaviour is
+      unexpected (some PDFs remain in an obscure Downloaded folder, instead of
+      in the main collection)
+    - somewhat heavy (it offers functions of online syncing, etc)
+    - poor search capability (related to the point above)
+
+Above-mentioned issues will with no doubt be improved in future releases, but
+they are a starting point for this project. Anyway, a command-line tool is per
+se a good idea for faster development, as noted
+[here](https://forums.zotero.org/discussion/43386/zotero-cli-version), but so
+far I could only find zotero clients for their online API (like
+[pyzotero](https://github.com/urschrei/pyzotero) or
+[zotero-cli](https://github.com/jbaiter/zotero-cli)). Please contact me if you
+know another interesting project.

papers_cli-2.17/docs/configuration.md

@@ -0,0 +1,101 @@
+# Configuration and install
+
+## install: make bibtex and files directory persistent
+
+```
+$> papers install --global --bibtex papers.bib --filesdir files
+papers configuration
+* configuration file: /home/perrette/.config/papersconfig.json
+* cache directory:    /home/perrette/.cache/papers
+* absolute paths:     True
+* files directory:    files (1 files, 5.8 MB)
+* bibtex:            papers.bib (1 entries)
+```
+
+With `--global`, the configuration applies to the whole user account: any
+`papers` command, from any directory, will know about these settings. A
+fresh `papers install` without scope option is *local* to the current
+directory (see below); re-running `papers install` on an existing install
+keeps its scope, so `--local`/`--global` are only needed to be explicit.
+
+Running `papers install` again *updates* the existing configuration: options
+you pass change, everything else is kept. Pass `--reset` to discard the
+existing configuration and start over from defaults. Use `--no-prompt` to
+accept all defaults non-interactively (at the prompts, `Enter` accepts the
+proposed default, typing a value sets it, and `unset` clears it).
+
+Type `papers status -v` to check your configuration.
+
+You also notice a cache directory. All internet requests such as crossref
+requests are saved in the cache directory. This happens regardless of whether
+`papers` is installed or not.
+
+## Local install
+
+A local install keeps separate configurations per project — one bibliography
+per folder. It is the default for a fresh install (`--local` makes it
+explicit):
+
+```
+$> papers install
+Bibtex file name [default to existing: papers.bib] [Enter/path/'unset']:
+Files folder [default to new: papers] [Enter/path/'unset']: pdfs
+papers configuration
+* configuration file: papersconfig.json
+* cache directory:    /home/perrette/.cache/papers
+* absolute paths:     True
+* git-tracked:        False
+* files directory:    pdfs (90 files, 337.4 MB)
+* bibtex:             papers.bib (82 entries)
+```
+
+Creates a local configuration file (`.papersconfig.json`) in the current
+directory. By default, it expects existing or creates new `papers.bib`
+bibliography and `files` folder in the local directory, though `papers` will
+ask first unless explicitly provided. Note that every call from a subfolder
+will also detect that configuration file (it has priority over global
+install).
+
+By default, the local install is meant to be portable with bibtex and files, so
+the file paths are encoded relatively to the bibtex file. If instead absolute
+paths make more sense (example use case: local bibtex file but central PDF
+folder), then simply specify `--absolute-paths`:
+
+```
+papers install --local --absolute-paths --filesdir /path/to/central/pdfs
+```
+
+## Uninstall
+
+Getting confused with papers config files scattered in subfolders? Check the
+config with:
+
+```
+papers status -v
+```
+
+and remove the configuration file by hand (`rm ...`). Or use the `papers
+uninstall` command:
+
+```
+papers uninstall
+```
+
+It removes the configuration file and reports what it leaves behind (the
+bibtex file, the files directory, and the backup directory if any). Pass
+`--remove-backup` to also remove the backup directory.
+
+You may repeat `papers status -v` and cleaning until a satisfying state is
+reached, or remove all config files recursively up to (and including) global
+install:
+
+```
+papers uninstall --recursive
+```
+
+## Relative versus absolute paths
+
+By default, the file paths in the bibtex are stored as absolute paths (starting
+with `/`), except for local installs. It is possible to change this behaviour
+explicitly during install or in a case-by-case basis with `--relative-paths` or
+`--absolute-paths`, with or without install.

papers_cli-2.17/docs/features.md

@@ -0,0 +1,50 @@
+# Features
+
+## Current features
+
+- parse PDF to extract DOI
+- fetch bibtex entry from DOI (using crossref API)
+- fetch bibtex entry by fulltext search (using crossref API or google scholar)
+- create and maintain bibtex file
+- add entry as PDF (`papers add ...`)
+- add entry as bibtex (`papers add ...`)
+- scan directory for PDFs (`papers add ...`)
+- rename PDFs according to bibtex key and year (`papers filecheck --rename [--copy]`)
+- some support for attachment
+- merging (`papers check --duplicates ...`)
+- fix entries (`papers check --format-name --encoding unicode --fix-doi --fix-key ...`)
+- configuration file with default bibtex and files directory (`papers install --bibtex BIB --filesdir DIR ...`)
+- integration with git
+- undo/redo command (`papers undo / redo`)
+- display / search / list entries: format as bibtex or key or whatever (`papers list ... [--key-only, -l]`)
+- list + edit or remove entry by key or else (`papers list ... [--edit, --delete]`)
+- fix broken PDF links (`papers filecheck ...`):
+    - remove duplicate file names (always) or file copies (`--hash-check`)
+    - remove missing link (`--delete-missing`)
+    - fix files name after a Mendeley export (`--fix-mendeley`):
+        - leading `/` missing is added
+        - latex characters, e.g. `{\_}` or `{\'{e}}` replaced with unicode
+
+## Tests
+
+Test coverage is improving (now 80%).
+
+Currently covers:
+
+- `papers extract` (test on a handful of PDFs)
+    - parse pdf DOI
+    - fetch bibtex on crossref based on DOI
+    - fetch bibtex on crossref based on fulltext search
+    - fetch bibtex on google-scholar based on fulltext search
+- `papers add`
+    - add entry and manage conflict
+    - add pdf file, bibtex, directory
+    - add one pdf file with attachment (beta, API will change)
+    - conflict resolution
+- `papers install`
+- internals:
+    - duplicate test with levels `EXACT`, `GOOD`, `FAIR` (the default), `PARTIAL`
+- `papers list`
+- `papers undo / redo` (partial)
+- `papers filecheck --rename` (superficial)
+- `papers check --duplicate` (fix DOI etc.) (superficial)

papers_cli-2.17/docs/git.md

@@ -0,0 +1,49 @@
+# Git integration
+
+## Git-tracked library
+
+By default (when a git binary is available), a fresh `papers install`
+git-tracks any change to the bibtex file. Pass `--no-git` to opt out, and
+`--git-lfs` to also back up the attached files (see below):
+
+```
+$> papers install --bibtex papers.bib --filesdir files [ --no-git | --git-lfs ]
+```
+
+Installs made by older papers versions keep their saved setting; re-run
+`papers install` (or `papers install --edit --git`) to enable git-tracking
+on an existing install.
+
+From now on, every change to the library will result in an automatic git
+commit. And the `papers git ...` command will work just as `git ...` executed
+from the backup directory. E.g. `papers git remote add origin *REMOTE URL*`;
+`papers git lfs track files`; `papers git add files`; `papers git push`.
+
+Under the hood, every save commits a copy of the bibtex file to the backup
+repository. If `--git-lfs` is passed, the attached files are backed up along
+with the bibtex: they are hard-linked into the backup directory and tracked
+with git-lfs, together with a copy of the bibtex whose file paths point into
+the backup (so the backup is self-contained). Background in
+[issue 51](https://github.com/perrette/papers/issues/51).
+
+Backup occurs in a subfolder of `~/.local/share/papers/backups` regardless of
+the type of installation. Type `papers status -v` to find out, or
+`papers backup list` to see every backup directory papers knows of and which
+library each belongs to. Orphaned directories (e.g. whose library was
+deleted) can be cleaned up with `papers backup remove NAME` (glob patterns
+allowed; asks before deleting unless `--force` is passed).
+
+Backup directories are named after the bibtex file and its parent folder,
+plus a hash of the full path (e.g. `myproject-references-3f9a1c2b`), so two
+libraries can never share a directory and same-named libraries remain
+recognizable.
+Each directory also contains a `manifest.json` recording the bibtex file it
+backs up; if a backup operation finds a directory that belongs to another
+library (which could happen with directories created by papers versions that
+used the bibtex name alone), it moves the current library to a fresh
+directory instead of mixing the two histories. Directories created by older
+versions keep their name and are adopted as-is.
+
+For local installs that are already git-tracked, the feature remains useful as
+it is the basis for `papers undo` and `papers redo` (see
+[Undo and redo](undo-redo.md)).

papers_cli-2.17/docs/index.md

@@ -0,0 +1,55 @@
+<!--
+  Home page. The feature bullets are pulled straight from README.md (single
+  source of truth) via the include-markdown plugin; everything else links into
+  the guide.
+-->
+# papers
+
+Command-line tool to manage your bibliography (PDFs + BibTeX).
+
+{%
+  include-markdown "../README.md"
+  start="<!-- intro-start -->"
+  end="<!-- intro-end -->"
+%}
+
+## Get started
+
+```bash
+pip install papers-cli
+papers add mypaper.pdf --rename --copy --bibtex papers.bib --filesdir files
+```
+
+- **[Installation](installation.md)** — pip install and external dependencies.
+- **[Quickstart](quickstart.md)** — extract metadata, add a PDF, list entries.
+- **[Adding entries](adding-entries.md)** — from PDFs, DOIs, bibtex, or whole directories.
+- **[Configuration and install](configuration.md)** — make your bibtex and files directory persistent.
+
+## Guides
+
+- [Adding entries](adding-entries.md)
+- [Listing and searching](listing.md)
+- [Renaming files and keys](renaming.md)
+- [Configuration and install](configuration.md)
+- [Managing your library](library-management.md)
+- [Git integration](git.md)
+- [Undo and redo](undo-redo.md)
+
+## About
+
+- [Features](features.md)
+- [Comparison with other tools](comparison.md)
+
+## From the same author
+
+A few other open-source tools I maintain.
+
+**Scientific writing & data**
+
+- [**texmark**](https://perrette.github.io/texmark/) — write scientific articles in Markdown and convert them to journal-ready LaTeX/PDF.
+- [**datamanifest**](https://perrette.github.io/datamanifest/) — declarative, reproducible dataset management. *(See also the [datamanifest.toml](https://perrette.github.io/datamanifest.toml/) format spec and the [DataManifest.jl](https://awi-esc.github.io/DataManifest.jl/) Julia port.)*
+
+**Speech to Text (dictate) and Text to Speech (read-aloud) tools**
+
+- [**scribe**](https://perrette.github.io/scribe/) — speech-to-text dictation.
+- [**bard**](https://perrette.github.io/bard/) — text-to-speech reader.