We are ready to firm up the long-running "overhaul" branch. When merged into
the "master" branch (soon!) it will cause significant changes to the HTML
surrounding your content. That means the header/banner, new footer, and
navigation via Table of Contents and Prev/Up/Next buttons. We want the new CSS
and Javascript to all make it look good. You can ensure *your* project looks
good down the line by alerting us to changes *now*, not later. Yes, I know it
is a busy time, but we are starting now so as to have everything in good working
order for the start of classes next term.
Your *content* on a page should not change, but certainly holler if it does.
The process is not as easy as using the CLI. If you understand and are able to
do the following, then please, please do. (And if the following makes no sense,
then count yourself out, and thank those who will do this.)
1. Clone the alternate repository and switch to the "overhaul" branch. My
clone is called "pretext-fork" below - you may want something similar.
https://github.com/rbeezer/pretext.git
2. Make a Python virtual environment. And "pip install" the "lxml" and
"requests" packages. Post here if there is a package I have forgotten.
https://pretextbook.org/doc/guide/html/python-virtual.html
https://pretextbook.org/doc/guide/html/pip-install.html
3. Build stock HTML output with a local/custom version of the following,
substituting your clone and your project.
$ pretext-fork/pretext/pretext -vv -c all -f html -p
pretext-fork/examples/sample-article/publication.xml
pretext-fork/examples/sample-article/sample-article.xml
4. If you can post live output someplace convenient/temporary, that will make
David's job even easier. For example:
https://pretextbook.org/doc/guide/html/processing-testing-html-globally.html
David F has an "overhaul" issues thread going. Please report there with
observations, and lets use this thread for the logistics of actually testing
this out. Thanks.
Rob