cloning
These Wiki GitHub pages are a separate sub-project of orcmid/miser, named orcmid/miser.wiki. It is cloned to my local PC and can be edited and pages created at that location. There are a few matters to understand for operation of the Wiki and authoring and publishing from a PC-located clone.
The value of the wiki, for me, is its more-casual usability and also the existence of Page History rather than what happens to make the project docs/ folder work. It is the combination that is useful.
I mean for the Wiki to be farely casual, but I thought construction management
needed to be documented on the Wiki. I could document it on docs/
where things are already more formal and it takes a pull request for others
to contribute. I am willing to open the wiki a bit more generously, so long
as it doesn't create a serious curation problem.
The GitHub help files specify the URL to use when cloning a wiki. I did that and the cloning happened into a folder I create alongside my existing GitHub clones.
I learned I cannot do this within the GitHub Windows client. It indicates that the repository does not exist.
I can register the cloned repository as an existing repository with GitHub. It will recognize changes and allow me to make commits to that local clone. Attempts to push simply fail. There is no message yet nothing happens.
Thanks to Stack Overflow, I found a way to do a manual Git Push that succeeds. The advice was at https://stackoverflow.com/questions/10573957/pushing-from-local-repository-to-github-hosted-remote
For the first push, git push origin master, there was a pop-up to log into
GitHub and then provide my (Microsoft) Authenticator code. After that first
time, I am apparently set up just fine. I can do git push and git pull
operations just fine. The GitHub client is no good for these. I made
lapsing in and out of command-line operation easier and I'm satisfied with
that much.
In my local editing of miser.wiki, I created a subfolder, construction/,
based on the idea that pages that having their own assets need to be in a
subfolder in company with their unique assets. On the GitHub side, there is
no repository view of the wiki, so I can't see into the subfolders there.
I also discovered that MarkDown pages in subfolders, such as this one are elevated in the published wiki as if the folder has been flattened away. References to assets (i.e., image files) must be as if relative from the home level. That is how the images here have been brought into view.
Even though this page is at a different level than the URL shown for it in the Wiki view, editing in the Wiki view puts its results in the correct (sub-folder) place.
I can make the document engineering and my adaptation of construction zones/materials visible also by linking, the only way to make that public short of someone cloning the orcmid/miser.wiki.git repository. The construction.txt manifest and TODOs can be seen this way.
Let's see how else we are getting on so far.