diff --git a/orcmid.github.io.txt b/orcmid.github.io.txt index dba4aa4..7b8cdfb 100644 --- a/orcmid.github.io.txt +++ b/orcmid.github.io.txt @@ -1,4 +1,4 @@ -orcmid.github.io.txt 0.0.4 UTF-8 2023-08-28 +orcmid.github.io.txt 0.0.5 UTF-8 2023-08-29 *---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--* @@ -12,17 +12,18 @@ orcmid.github.io.txt 0.0.4 UTF-8 2023-08-28 The GitHub project orcmid.github.io is created, by convention, to anchor documentation files published as GitHub pages from various - github/orcmid projects. + GitHub/orcmid projects. Although the documentation provided in docs/ folders of projects will appear under https://orcmid.github.io/ as subfolders, they - are not visible directly on this special project. + are not visible directly within this special repository. The only direct materials beyond README.md here are those intended to address overall matters and provide some documentation-only materials, such as in the orcmid/ folder. - Some material here will be referenced from "subordinate" projects. + Much material incorporated in the web site will be supplied from + anchored "subordinate" projects. This level may also serve to preserve some nfoCentrale.com anchor materials and materials from retired domains originally housed at @@ -34,16 +35,21 @@ MANIFEST orcmid.github.io.txt this synopsis and manifest - README.md - the orcmid.github.io/ home/front-porch page Markdown for - + README.md the orcmid.github.io/ home/front-porch page Markdown for + + + images/ All of the images in support of Orcmid on GitHub. + construction/ construction materials for the anchor site + + orcmid/ All about Orcmid on GitHub. This set of web pages is + provided directly, along with some others, as part of the + orcmid.github.io repository. + + docEng/ supplied from docs/ + miser/ supplied from docs/ + nfoTools/ supplied from docs/ - orcmid/ All About Orcmid on GitHub. This is a documentation- - only set of web pages that is maintained at this level - for general reference and also preservation. - construction/ construction materials for the anchor site overall, - potentially *---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--* @@ -66,59 +72,52 @@ MANIFEST ATTRIBUTION Hamilton, Dennis E. Orcmid GitHub Anchor/Scaffolding Documentation. - Project file construction.txt version 0.0.4 dated 2023-08-28, available + Project file construction.txt version 0.0.5 dated 2023-08-29, available on the Internet as a version of TODO - * Identify any further folders specific to the anchor. - - * Identify folders that are merged - - * Add an orcmid/ subfolder for overall information about Orcmid. - * Find the best "What's an Orcmid?" page and account. * See if nfoCentrale.com level has some useful material to mirror/continue here. - * I need orcmid/readings here using the shared/branched/host folder trick - in VXP2. I can then resolve where I want readings distributed. I think - having readings at the top level here might be more helpful. Some of the - materials are global to different projects and others are just about - orcmid. The common maintenance is difficult. The referencing and cross- - referencing is tricky. - - * Check to see if relative URLs work from project docs/ GitHub Pages to this - orcmid.github.io level. - - * I must reconcile preservation here, especially the technical materials from - orcmid.com and elsewhere, on fundamental shared content in preservation - locations. + * Material at this level is reachable from anchored docs/ sources and there + can be relative references up into this level. * Decide quickly about where to put "What's an Orcmid" so that preservation elsewhere will function properly. - * Figure out how cross-references will work among former readings/ folders - too. + * Bring Orcmid's Lair readings/ here, perhaps as bib/, depending on who uses + what. + + * In order to have reliable maintenance of the bibliographies, it would be + useful to have them all in one place. This does make for longer links, + but they can still be relative. In that case, bib/ is superior to + readings/. That takes care of the maintenance problems. I wonder what it + does for referencing from anchored sites though. It would be nice to tie + in bibliographical material elsewhere, such as + . + + * I've concluded that preserving/transposing construction structure here is + worthwhile now that I have FrontPage available to do the work. It takes + care, and I am thrilled about the prospect. + + * Setup construction structure the anchor level and work through the + preservation process in construction/ here. - * I'm conflicted about elevating orcmid to here, and/or not providing any - construction/ here, since docEng/ will cover most of it as will the - individual orcmid/ and miser/ folders if I want. + * Find a way to treat the subprojects separately, so there does need to be + some anchor provision. This decouples the maintenance of anchored-docs + from each other and the anchor level. - * Part of this quandary has to do with splitting up Orcmid's readings/ even - more than just between orcmid/ and miser/. Also, I realize they need to - be curated better, and there is room for many additions. I'm also happy - about how these have been authored in FrontPage and I am inclined to - preserve that, with all of its limitations. It will take considerable - improvement before I would use a framework for these. + * See if there is something in the former anchor page, c000002.htm, that + applies to this. - * And I still do not know whether the best consolidation is at - orcmid.github.io/bib rather than orcmid.github.io/orcmid/bib or /readings *---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--* + 0.0.5 2023-08-29T16:04Z Elaborate the anchor role and relevant TODOs 0.0.4 2023-08-28T16:21Z More ponderings 0.0.3 2023-08-27T20:36Z Ponderings 0.0.2 2023-08-27T17:09Z Prioritize preservation of materials that had tied