README - General description of the doxphinx project
Copyright (C) 2018-2023 Angel Linares Zapater
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License, version 2, as published by the Free Software Foundation. See the COPYING file.
This program is distributed WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Getting started
doxphinx is a theme for the Sphinx documentation system. The purpose of doxphinx is to provide a single mechanism to generate the documentation of a project, both in HTML and PDF formats, from a common source.
This common source of documentation consists of a set of text files written in reStructuredText markup language along with a set of conventions for writing and organizing the different files. The Sphinx tool can then be used to automatically generate a HTML website or a PDF book, both from the same single documentation source.
How to use
In order to use doxphinx to document any project, just install it using:
$ pip install doxphinx
Then create a directory for the documentation files and using the Sphinx tool:
$ sphinx-quickstart
Initialize the directory as a Sphinx project and configure the conf.py file that has been created, and you are ready to build the documentation using doxphinx.
See “The doxphinx Handbook” <https://docs.phyglos.org/doxphinx> to learn how to use doxphinx in your documentation project.
At this point you can focus on the actual documentation work for your project. Whenever the documentation is ready to be published or updated, use Sphinx to format again the HTML website or the PDF book from the documentation source files.
Status
The doxphinx project is in STABLE status.
More information
The COPYING file contains the GNU License for this software.
The RELEASE file describes the main changes in this release.
See https://docs.phyglos.org/doxphinx for more information.
Metadata
Release files for doxphinx 1.7.0
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 |
|---|---|---|---|---|
| doxphinx-1.7.0.tar.gz | 16.3 kB | Without provenance | Details for doxphinx-1.7.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| doxphinx-1.7.0-py3-none-any.whl | Python 3 | none | any | Details for doxphinx-1.7.0-py3-none-any.whl |
Total release size: 35.6 kB
Release files / doxphinx-1.7.0.tar.gz
| Download URL | doxphinx-1.7.0.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75044f057be8713136b2784085eef2c8cdd5d7dc432e120b684f60473facb6a5
|
|
BLAKE2b-256 checksum How to use checksums |
a77a954448306f8a6d482871c4f811aad1a4720da287a661d3f9c4e45d61c38b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.2
|
Release files / doxphinx-1.7.0-py3-none-any.whl
| Download URL | doxphinx-1.7.0-py3-none-any.whl |
|---|---|
| Size | 19.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
57274703246e53fdfafb341072075cfe775f26fb4bc28343afd948b9504726b5
|
|
BLAKE2b-256 checksum How to use checksums |
4c535542376dc9d518c7a194b84de1c29420d4d56a23b6045ec3d9c2165fa2ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.2
|
Security for doxphinx 1.7.0
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.