3:48 p.m.
On Thu, 16 Apr 2020, Scott McCarty wrote:
On Thu, Apr 16, 2020 at 4:34 PM Robert P. J. Day <rpjday(a)crashcourse.ca> wrote:
On Thu, 16 Apr 2020, Scott McCarty wrote:
> Robert,
> My recommendation would be to wait a few weeks. I have committed
> to driving some major changes to the upstream docs. You are now on
> my list as the "third amigo" if you are OK with that. I'm
planning
> on creating a branch to work on docs, along with a development docs
> site (I need to work on that). Then, I will reach out, and we can
> all hack on it. Does that work?
yup. can i assume it will remain sphinx-based, as i am currently
knee-deep in helping convert another project to sphinx, so being able
to transfer all that know-how would be just ducky.
I don't think it was every Sphinx based? The Read The Docs stuff
appears to be in RST format. Where are you seeing Sphinx docs at? I
can dig in.
i'm looking at libpod/docs/Makefile:
# Minimal makefile for Sphinx documentation
#
# You can set these variables from the command line, and also
# from the environment for the first two.
SPHINXOPTS ?=
SPHINXBUILD ?= sphinx-build
SOURCEDIR = source
BUILDDIR = build
# Put it first so that "make" without argument is like "make help".
help:
@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)"
$(SPHINXOPTS) $(O)
clean:
rm -fr build/
.PHONY: help Makefile
# Catch-all target: route all unknown targets to Sphinx using the new
# "make mode" option. $(O) is meant as a shortcut for $(SPHINXOPTS).
%: Makefile
@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)"
$(SPHINXOPTS) $(O)
~
if you're not using sphinx, i am massively confused.
rday