Aug 012017
 Posted by on UTC 2017.08.01Tue at 12:03 taxonomy N0C3Y3, www=World Wide Web N0C2LO  Add comments

OC1GOF: website ‘‘especially what I need to know’™’ :

  1. ‘section’
    1. ‘‘‘Pretty Link’ entry’ ‘anew’’
    2. ‘history in reverse order’

      1. OU092H: ‘op’ resume editing after {;date 2017.08.01TuePst0454 ;polish .75 ;version 1 ;words 5703 ;revision 1}
        1. after NY0WO6 with replacement qty {781+skip+496}
        2. after date 2017.07.31MonPst2344 after words 5927
        3. after entry template is /5812#ON705D
        4. OTZUNR: ‘publishing my articles for James’ reference in his thesis starting with his Proposal :OTZUJB
      2. OC1GK5: op’{resume editing after {;date 2016.08.16TuePst2243 ;polish .5 ;version 0 ;words 195 ;revision 1} after {factor back appropriate content: not applicable} after create {this ‘document’} starting date Pst2229 by following NXBIBI with ‘section’ template {/5611#OBUZH2 since {;post latest #1 ;related: no ;reuse: no}} after {realize a full post needed to properly-file topic {moved to, not created} here for ‘generators & results :OC155R’ fresh}}. :OC1GK5
    3. Reply. To reply & discuss, please use’s default methods (click) except: none.
    4. TOU(Terms Of Use) including {copyright © and info’s {confidentiality/privacy & allowed use}} is’s default TOU except: none.
    5. major subs:
    6. ‘additional’
      1. ‘name anew’
      2. ‘post category’

        1. OC1HF3: ‘www=World Wide Web N0C2LO’ as no smaller category
      3. sample table;
        or replace table with image and caption
        col heading
        row heading linked value


      4. ‘advertising/lessening additional’
      5. ‘motivation’
      6. ‘contributors including their {contributions & relevant background}’
      7. {to be put elsewhere} so ‘annex’
      8. ‘‘section history additional’ ‘in reverse start order’:’
        1. .
  2. OC1GZP:
    1. OC1GZY: static vs./over dynamic

      1. OC2IPV: notable pros thru cons –partially unified :OC2IPV
        1. OC2P8L: due to generators, static sites are making a come-back: while it originally seemed they were being replaced by dynamic sites, now it’s feeling the reverse
          1. OC2POS: for instance, the term ‘static site generators’ became notable in 2009.10 and (after period of hype so backlash in 2010) are since on the steady rise continuing today 2016.08, per the Google Trends
          2. OQI93I: why? Well one way to phrase it (at least what Lucy and especially I have found), in terms of getting a lot of features,
            1. OQI9CE: static sites used have a many holes (why seemingly most web developers fast moved to dynamic sites) but the holes have been slowly well filled in, in some areas (as notably via Disqus) so well even the dynamic sites are turning to use them instead
            2. OQI9HM: the dynamic sites maybe-especially WordPress:
              1. OQI9IX: is easier in the short-term but harder if not impossible in the long term
              2. OQI9HU: more specifically, it gives you a lot (of features) fast but an overwhelming several turn out to have problems & incompleteness that hard or impractical to fix
              3. OQIZWZ: {one of the leading static site generators: Hugo} was ‘written foremost out of frustration from extensive use of WordPress :OQJ015
        2. OQI3OB: have some notable editing pros, from biggest 1st:
          1. OQI8U0: after generally releasing/publishing an article, {drafts are still possible, specifically edits can still be made without releasing them until ready}
            1. OQIAG9: so for instance you one can start a fix or make notes on a fix, common operations which normally expect if not require {cleanup (at least spell & grammar check, or testing) and/or require approval or redaction} before release, without having to do special save/recovery procedures and/or risk/have premature release, by instead continuing to improvement edits on some separate internal copy which is not yet approved from release
            2. OQI8WS: at least this is very hard with WordPress, as after an article…
              1. OQIA68: is published, any further edits must be also published by the time the tab is closed else will result in a crash recovery of the article which as well as being ugly, permanently waste space as also…
              2. OQIA5Y: (after an article) has an edit explicitly saved, any further edits even if incomplete & few by the time the tab is closed, will result in another permanent revision of the article (which an apparently-costly full copy even if just 1 character changed!, and SQL database size is limited as to ~1GB on DreamHost shared hosting) either by explicit save or messy crash recovery
            3. OQI9PD: which is notably if not killer bad for {ongoing (not short-life) articles as probably most notably encyclopedic-like articles}
              1. OQI9QI: causing to not yet even first publishing most of my writings since 2016.01~ (as they increasingly encyclopedic and on running WordPress)
          2. OQI3RE: likely better prevention & correction of at least a single person simultaneously editing the same file/article in different editing sessions
            1. OQI3VE: as
              1. OQI3ZZ: every non-trivial ‘‘(editor) as a complete app for desktop .. :OQ8QIV’ :OQI327’ auto re-uses the file’s editing session if that exists if the file is additionally opened by it for editing
              2. OQI437: at least in the most popular dynamic site WordPress, there is no detection/prevention/correction when at least the same editor simultaneously opens the same article for editing, readily necessitating careful continual monitoring to prevent that as by ‘my leading [Sidewise] use: detailed in ‘Sidewise :O3MNUN’ :OA3Z4B
          3. OC2K5E: stored in {the normal method, non-locking VCS} and using common merge tools, simultaneous editors of the same file is possible, something often not {offered else well-managed} by dynamic sites; more at OC2MG9 :OC2K5E
          4. OQI4LA: gap
          5. OC2IWW: can do all edits offline (so also faster), presuming not having to look up much
        3. OQI5GI: if one is willing to code, getting the exact functions & look one wants seems generally easier OQI5GI, including:
          1. OQI4YR: (generally easier) fixing & extending the site function via programming (say when there isn’t a plugin), as
            1. OC2OXA: don’t need to know dynamic site internals, which are generally more complex that those of static
            2. OQI55N: don’t need to deal with databases except familiar text files
            3. OQI4Y8: don’t need to deal with languages beyond CSS & JavaScript, so notably don’t need to deal with {PHP, a language which needs to be replaced by JavaScript-server extension notably Node}
            4. OC2IRC: given some programming, likely notably easier to

              1. OC2IT1: include & maintain significant results from other sources, especially from document generators (comparison)
              2. OC2J0J: automatically convert content to another ‘markup language :OC1OE1
          2. OC2O1A: (generally easier) doing the page layout & templates (say when you can’t find an existing good enough theme)
            1. OC2O5D: including web page editing tools more {traditional} + {providing WYSIWYG editing}
            2. OC2O7Y: since one doesn’t have to deal-with & workaround CMS widgets & themes, which are usually also in another language as PHP
          3. OQI5MR: as standard dynamic sites at least leader WordPress have huge directories of plugins & themes, but which make it super easy if you find pretty near what you want, but the search pretty harder and if you don’t find what you want then {per OQI5GI, making it yourself seems harder}
        4. OC2R9R: with done with proper VCS, most notably git, as seems the norm,
          1. OC2KKS: notably better & generally-top versioning
            1. OC2KOK: including
              1. OC2KNF: version all templates & other files, not just body content, without having to have & use an add-on as ‘Revisr.Io NQBCW2
              2. OC2IUL: have small changes to a document be stored at-else-near fully compactly, thanks to great compression of notably git
              3. OC2QFC: prior content by default never lost and indeed shared (though probably not easy to find) :OC2QFC
            2. OC2MPR: further background at this entry ‘2) Version control for content’ in OC159U
          2. OC2RAU: normally uses the same tools & storage (already) used for code development
          3. OC2RD7: generally gets automatically continual great backup
        5. OC2P6G: the inside-workings are easier for everyone to understand and especially to see
        6. OC2KQI: notably more/batter hosting & tool (options), including
          1. OQIYWR: better hosting speed & security as noted in
          2. OC0NNS: hosting money cost: notably lower. For a site with content accessibility…
            1. OC0O0B: all public, hosting is commonly $0!
            2. OQIZ1A: for some private
              1. OQIZ4Y: some hosts offer this ability notably by protecting site or pages by a password
              2. OQIZ65: commonly there is a monthly charge similar to general web hosting, at least if one wants {own domain}
              3. ‘‘section history additional’ ‘in reverse start order’:’
                1. OQIZ3O: I don’t know why I wrote this so now cut it:
                  1. OC0O0H: only having to buy for web masters, so affordable during production but afterwards can become pricey
          3. OC2NW5: ‘host :OC1I8B’ing is
            1. OC2NWW: auto-scaling for the better hosting for static sites.
            2. OC2NX6: generally already fast & ready for surges without the need for complex ‘caching layers’ as mentioned in OC1H6T
        7. OC0PDT: if public, all info is automatically well-searchable under common web search engines :OC0PDT
        8. –(mixed)
          1. OC2IQC: see in OC159U
        9. OC2Q1R: for largest websites, there can be scaling problems
          1. OC2QRZ: where ‘largest’ here is at least 1 of:
            1. OC2QVY: where ‘multiple simultaneous editors .. :OC2MG9’ is over {say 100 maybe 1000}
            2. OC2QVD: where the content is
              1. OC2QS6: over say {what GitHub can handle in a single repo (~1GB, detailed in ‘file & repo size :OC0PRO’)}
              2. OC2QSF: say ‘Facebook’ or Google Groups or Wikipedia
          2. OC2R12: where how to handle that is not yet clear to me, but might be via special tools (which are advertised) used for really scaling git repos
        10. OQI57M: dynamic web features take require JavaScript usually linking-to & sourced-from from dynamic web services
          1. OQI587: for the basic, it’s increasingly & mostly built: use ‘external web service :OQHE5W
          2. OQI5DK: fortunately the coding generally easier as noted above
          3. OQIZKD: –the ‘disadvantage’ noted at
        11. OC2MMQ: to the degree one doesn’t routinely do auto-save and {backup offsite sources (as by commit & push)}, edits are at risk and not shared.
        12. OC2QB9: if sharing the site’s source repo, privacy will be compromised somewhat {how much & where hard to tell but probably ok} — due to OC2QFC and plus then generally hard if not impossible to permanently remove even bad content
        13. OQI2Z9: editing the actual articles has some notable cons:
          1. OQI290: requires use of, beyond just a web browser, normally also, from increasing tricky:
            1. OQI29M: computer with a {traditional so non-mobile} OS, as laptop or desktop
              1. OQI3FT: though it practice this seems to be required even for top dynamic sites as WordPress (as it doesn’t feel they can be well edited on a mobile OS)
            2. OQI2AC: at least 3 generally local apps:
              1. OQI327: ‘(editor) as a complete app for desktop and/or web browser :OQ8QIV’ :OQI327
              2. OQI35H: ‘(static website) generator :OC1G2X
              3. OQI389: normally VCS client as most famously GitHub client
              4. OQI3D1: merge & diff app(s) especially if the same file edited
          2. OC2MG9: multiple simultaneous editors is well-doable {including for same file :OC2K5E}, but gets notably more complex… :OC2MG9
            1. OC2MEW: don’t get real-time merging of a single document (unless something very unique setup)
              1. OC2OK6: in comparison, dynamic sites could this
                1. OC2ON3: but generally don’t, except for single documents it is done via Google Docs & Cloud 9 & others, but so far these offer weak comprehensive {site, so many-document} organization
              2. OC2MKU: a workaround would occasionally be to use to use Cloud9’s simultaneous editor
            2. OC2JY1: editors must do merging of variations merging, which {requires additional tools/commands and {is naturally notably complex, especially after {file/folder renames & moves} or/and {same-file edited}}
        14. OC2MTS: serious: problems so far for all private content
          1. OC2MYT: including
            1. OC2MUG: as site generally has 1 access level (at least via git), for each content with a particular privacy, handling it seems hard as it seems it either must be…
              1. OC2N8M: grouped into its own site with that particular privacy
              2. OC2N8R: encrypted, possibly inline, with that particular privacy
                1. OC2NED: which then, for normal view, to decrypt (and, for ending, re-encrypt) would have problems:
                  1. OC2NFF: for normal rendered output & within-editor, I’ve never heard of such tools though could be built.
                  2. OC2NI9: in editing mode, for higher privacy, there would be the danger of the unencrypted versions being stored insecurely
            2. OC2MZ6: even when published, it doesn’t get ‘automatically well-searchable under common web search engines :OC0PDT
      2. OC1H5A: static (website) :OC1H5A
        1. OC1H6T: entry :OC1H6T
        2. OC155R: (static website) generators & results :OC155R
          1. OC159U: intro + definition + pros & cons :OC159U
          2. OC1G2X: (static site) generator :OC1G2X
            1. OC1G3N: instance
              1. OQJ94P: shows every/most (‘(static site) generator :OC1G2X’ support 1 to 2 ‘template language :OQJ6L6’ per OQJ5ZK
                1. OQJ97N: and since there are about 1/10th as many of ‘template language :OQJ6L6’, picking that appears it can dramatically help pick among the too many ‘(static site) generator :OC1G2X
              2. OQJ5V1: list https://StaticSiteGenerators.Net :OQJ5V1
                1. OQJ5OB: notable pros thru cons
                  1. OQJ5PV: largest by far list I’ve heard of :OQJ5PV
                    1. OQJ5UQ: qty 459 now, was 437 on OC1HJF
                  2. OQJ5OM: both displays & sorts by latest ‘Stars Name License Language ▾ Created Updated’
                  3. OQJ5QX: lacks fast test deployment such as OQJ5K9
                2. OC1HJF: I ref’d #1 now by from OC1H6T :OC1HJF
              3. OQJ61Y: list :OQJ61Y
                1. OC1JFJ: also gives some relevant tech background :OC1JFJ
                2. OQJ5EZ: notable pros thru cons
                  1. OQJ5FA: sponsored by ‘Netlify :OC1J5J
                    1. OQJ5K9: indeed many leading entries have ‘Deploy to Netlify’ such as allowing a ‘site in 1 min.’ setup with GitHub & Netlify :OQJ5K9
                      1. OQJ9H2: qty (by count ‘div class=”deploy”’ in ‘view-source: now 12
                      2. OQJ5MP: –seems a great way to very fast try any one of the (these) leading site generators
                  2. OQJ5ZK: displays info such of entry ‘Jekyll 29782 ‘difference since last week’ 57; 6631 ‘difference since last week’ 14; 129 ‘difference since last week’ 8; A simple, blog-aware, static site generator. ;Language:Ruby ;Templates:Liquid ;License:MIT’ :OQJ5ZK
                    1. OQJ6BO: qty (by auto-counting in‘h4 class=”title“’ in http://view-source: 182 (147~ as of OC1G3X), so not as many as OQJ5PV :OQJ6BO
                3. OQJMTE: entries using a given ‘template language :OQJ6L6’ now :OQJMTE (of total ‘182 .. :OQJ6BO’) –so reference ‘StaticGen entries using :OQJMTE
                4. OQJDIF: search by language
                  1. OQJDIK: of CoffeeScript done now :OQJDIK –qty 4
                  2. OQJDIY: of JavaScript done now :OQJDIY –qty 58
                    1. OQJD2K: entry ‘Templates:Ghost’ should instead have value ‘HBS aka Handlebars template language :OQJA1W’ –bug :OQJD2K
                    2. OQJKU9: entry ‘Templates:false’ should likely instead have a real value or ‘none’. –bug
                    3. OQJL4F: entry ‘Templates:Markdown, EJS’ and others which have ‘Markdown’ as a template should not as ‘Markdown :OQJF2O’ doesn’t do templating at least not in the 1st 2 of these examples. :OQJL4F
                    4. OQJMNZ: entry ‘Templates:Comments’ value is wrong and should be say ‘‘TODO’’ –bug
                    5. entry
                  3. OQKK45: of ejscript done now :OQKK45 –qty 1
                    1. OQKK5P: also this language is missing from the pull-down –bug
                5. OC1G3X: I ref’d #1 now by OC14H8 :OC1G3X
              4. OQIW0Y: in alphabetical order
                1. OQIWST: 100s not listed here as too many
                2. OQIW1I: Jekyll :OQIW1I
                  1. OC10HY: entry
                  2. OQJ0BQ: entry with Likes 44 (so #2) of 116(Ghost) :OQJ0BQ
                  3. OC1KAQ: ‘As long as you are not using custom generators or converters with Jekyll everything is good. If you do however you’ll quickly notice that GitHub disabled custom Ruby code to keep everything secure. [so you may need to go to another service, as S3…]’ says review/how-to on 2012.02
                  4. OQJ4RM: notable pros thru cons
                    1. OQJ4T1: ~#1 most popular top site generator
                    2. OQJ4U3: in Ruby not JavaScript
                    3. OQJ4TL: favors Markdown
                  5. OQIW4U: I ref’d #1 at ‘site generator :OC10HT’ by OQIW8M
                3. OQKRHL: (static site generator) grunt-flats :OQKRHL
                  1. OQKRTC: npm
                  2. OQKRJD: entry :OQKRJD
                    1. OQKS9I: has ‘Templates:Hogan.js’ which should have value say OQKSBS –bug :OQKS9I
                    2. OQKSKY: description is missing {‘similar to’ as noted at OQKQPL plus especially where it gets this info} –bugs
                  3. OQKSBS: template language: ‘Mustache extended by grunt-flats template language :OQJM3B’ per its OQKS4K :OQKSBS
                    1. OQKRMA: including uses ‘compiler Hogan(Hogan.js) :OQKR45
                    2. OQKT5O: so alternative possibility ‘Grunt Edition: The Grunt wrapper around Pattern Lab Node Core’ quoting
                  4. OQKRIQ: I ref #1 now by OQJM16
                4. OQIWP3: Hugo (generator) :OQIWP3
                  1. OQIWHL: make
                  2. OQIWOT: search
                  3. OQIY3Q: source has ‘Stars 17278’
                  4. OQJ09G: has Likes 17 (so #5) of 114(Blogger -which is really a different category)
                  5. OQIWBQ: I ref’d #1 yesterday by OQIWQ9
                  6. OQIXAJ: notable pros thru cons
                    1. OQJ015: written foremost out of frustration from extensive use of WordPress :OQJ015 per
                    2. OQIXCS: by comparison ‘I looked at the existing static site generators like Jekyll, Middleman and Nanoc. All had complicated installation dependencies and took far longer to render my blog with its hundreds of posts than I felt was acceptable. I wanted a framework to be able to give me rapid feedback while making changes to the templates, and the 5+-minute render times were just too slow. In general, they were also very blog minded and didn’t have the ability to provide other content types and flexible URLs.’ quoting
                    3. OQIY0S: appears to be full-featured
                    4. OQIY0F: ‘Support for other languages’ (besides Markdown) where only the code mentions html, per
                    5. OQIXT9: foremost markdown instead of HTML per
                  7. OQIWQF: by site generator
                    1. OQIWQ9: instance of ‘Hugo (generator) :OQIWP3’: make :OQIWQ9 –from 2 of OQHNCW
          3. OC1I4S: model/use
            1. OC0M0X: to have a site for coordinating the materials of a video or similar production :OC0M0X
              1. OC0OUK: some exciting attributes: :OC0OUK
                1. OC0RNS: I’ve never heard this done before, even after quick search
                  1. OC11NC: –didn’t spot in nor
                2. OC0RO5: due to the problem being solved, it’s naturally a bit involved
              2. OC0NL7: notable pros thru cons
                1. OC1C7M: enabling async coordination, even with 0 planning meetings
                2. OC0P5Y: makes collecting & managing & following-up-on feedback very easy & organized
                3. OC0P6Z: {continually, meaning every time a site republish}, gives the big picture, plus all details to the degree interested, to everyone –even to the world if open-source,
                4. OC0NOO: should handle production sizes up to medium if not large, maybe a small Hollywood production
                5. OC0NUD: routine use ‘is very fast if not max-fast :OC0NUX
                6. OC0NPF: once a good example has been created, to create another is ‘fast .. :OC0NRI
                7. OC0NLH: entirely electronic & published, including nothing lost in non-posted messages/talk.
                8. OC0RDN: ‘effectively holds & manages all materials to be shared else sharable :OC0M58
                9. OC0NN3: and 100% versioned –effectively 0 history lost, plus diffable
                10. OC0O1D: maximally easy for ordinary collaborators: don’t have to have any special training and no tools besides a web browser & {a ‘Disqus :OC1KMG’ login: Disqus, FB, Google, or Twitter}
                11. OC0O4D: {the few repo editors: OC0M82},
                  1. OC0OBB: have a low bar for what has to be learned & done: just ‘do this simple routine :OC0N49
                  2. OC0O88: use their familiar scriptwriting, storyboarding, and video editing, web page editing, and other normal tools just as they normally do with almost no exception besides a better organization.
                  3. OC0O7T: need to know git commands (besides push) if doing advanced stuff as diffing or maybe searching non-script file history.
                12. OC0OOL: if open-source production, people just self-finding the site (as by web search) or just random invite can immediately become collaborators, too.
                13. OC0OZ0: due to OC0OUK including a very unique use of GitHub, so GitHub staff are likely to be very happy about it possibly even
                  1. OC0P1G: willing to dedicate some staff hours to help
                  2. OC0P2R: bring brownie points to me the inventor/designer plus those building it plus the first crews using it
                14. OC2N2W: — mixed
                  1. OC2N2S: see ‘(generated static site) notable pros thru cons –partially unified :OC2IPV
                15. OC1CBU: not yet designed for more than 1 coordinator/web master
                  1. OC2OE9: but scalable to more with significant additional complexity; more at OC2MG9
                16. OC0RHD: does not yet include diffs between script versions and other site content changes
                17. OC0RI8: diffs between any 2 (non-adjacent) revisions (of script or other pages) is not possible else (practical due to costly) due to static site generation.
                18. OC0OW4: due to OC0OUK, not yet a sure bet.
                19. OC0OWN: due to OC0OUK and my never having made GitHub Pages before, probably a few days of work to get the 1st one working.
              3. OC0M4K: definition
                1. OC0M9U: the repo :OC0M9U
                  1. OC0NPT: is started by forking a similar recent repo then deleting its content it just as a template.
                    1. OC0NRI: fast: probably ~1hr. :OC0NRI
                  2. OC0M58: effectively holds & manages all materials to be shared else sharable :OC0M58
                    1. OC0ZY8: well “except” for some or all large files, as per limits ‘file & repo size :OC0PRO
                      1. OC0ZRZ: For each such large file, instead stored here would be a link to it, ideally an unchanging version ideally via Git LFS, else to a link to the current version.
                      2. OC0XEI: Heed possible problems ‘storing on… :OC0R58
                  3. OC0MAR: is ‘GitHub repository :OC07J2’ which, say on commit, produces ‘the main site :OC0MBI
                  4. OC0N32: these (source files)
                    1. OC0M82: the writer & director & similar edit :OC0M82
                      1. OC0N49: specifically do this simple routine :OC0N49
                        1. OC0NUX: which is very fast if not max-fast :OC0NUX
                        2. OC0N59: done say 2x per week (can be more or less as needed)
                        3. OC0N5G: of, in order

                          1. OC0N6E: review comment updates, where for each, do in order :OC0N6E
                            1. OC0N73: accordingly update corresponding issues and/or source files
                            2. OC0N93: reply back on the comment a link to, & ideally note of, the work done
                          2. OC0N5P: if issues used, review issue updates and for each, do same as {for comments :OC0N6E}
                          3. OC0NCP: do any remaining updates to source
                          4. OC0ND4: save sources then do a ‘make’, which is in order:
                            1. OC0NE1: do any exports, as exporting the script to HTML & PDF
                            2. OC0NEE: run ‘site generation software :OC0MCQ
                            3. OC0NH4: do git push (so publishing the new version of the site)
                          5. OC0NIW: email &SMS actors & crew the link(s) to the updates
                        4. OC0OIT: note for non-script, one will usually be updating and sometimes copying files that ‘use site generation software :OC0MCQ
                    2. OC0N3I: nobody else typically deals with
                2. OC0MBI: the main site :OC0MBI
                  1. OC0MC8: uses ‘(static) host :OC1I8B
                  2. OC0MCQ: uses site generation software :OC0MCQ
                    1. OC0NFG: as Jekyll or better
                    2. OC0MIR: to
                      1. OC0MJE: add to every web page
                        1. OC0MJQ: Discus or equivalent
                        2. OC0MK3: heading, navigation, categories if needed, and similar usual web page stuff
                      2. OC0NG3: create a site index page
                  3. OC0MPM: has content
                    1. OC0MWN: a main page with links to
                      1. OC0MYB: script revisions
                        1. OC0MEG: where, for each revision of the script,
                          1. OC0MFH: a subsection containing
                            1. OC0MFV: a main page with summary plus links to details including
                              1. OC0MGO: the script rendered as
                                1. OC0MMU: linked HTML pages
                                2. OC0MN3: a .pdf file if desired
                      2. OC0MON: a page detailing involved people (including cast & crew) & the role(s) of each
                      3. OC88NW: (a page of) the equipment
                      4. OC0MSS: a calendar via 1 or more of:
                        1. OC0MTK: Google Calendar
                        2. OC0MUB: for every event, else those that need it, a web page
                      5. OC0ZPO: a page linking to the video (or other resultant product) at various stages of editing, from raw to draft & release edits
                        1. OC0RAL: as far here storing this material, that is :OC0M58
              4. OC0M25: my idea on 2016.08.15MonPst21 as a solution for Lucy in her reporting troubles using email to get feedback & coordinating video production for her {3 wishes via a smartphone app} story
        3. OC1I8B: (static website) hosting :OC1I8B
          1. OQIY9L: any general purpose web host will work but hosting…
          2. OQIYAI: specialized for static websites
            1. OQIYAW: have more support & less-cost than for general (dynamic as node or PHP) hosting
            2. OQIYCV: lists 11 which are mostly specialized for static. :OQIYCV
            3. OQIP9S: via Git hosting :OQIP9S
              1. OQIOYV:
              2. OQIPB9: from most preferred roughly
                1. OC1IA5: ‘(GitHub) Pages :OAOUJI
                2. OQISMJ: :OQISMJ
                  1. OQISWW: notable pros thru cons
                    1. OQISWS: ~15 plugs to extend the generic static site :OQISWS
                    2. OQIT3T: npm based it appears
                    3. OQITAJ: ‘Use your own domain name’ and all other (generally lesser) top features costs $15/mo per
                  2. OQISLA: I ref #1 now by OQISDT
                3. OC1J5J: Netlify :OC1J5J
                  1. OC1J5T: Google entry,3,
                  2. OQISAX: entry Likes 1 (so #7) of 7(GitHub Pages)
                  3. OQIQ9H: notable pros thru cons
                    1. OQIQC9: compared to ‘(GitHub) Pages :OAOUJI’,
                      1. OQIQAV: seemingly all features of including
                        1. OQIQB1: ‘Continuous Deployment’ at via at least GitHub per
                      2. OQIQCO: at no cost, also ‘Let’s Encrypt TLS Certificates; Custom redirect rules; Hooks & Notifications’
                      3. OQIQIG: more features if open-source project or at cost of $9 to $1000/mo per
                    2. OQIQMY: npm based it appears per
                  4. OC1JGU: I ref’d #1 ~10min ago by OC1JFJ
                4. OC1ICX: ‘GitLab Pages :OC14GW
            4. OC1I8S: if not better classified, instance, from most preferred –roughly
              1. OQIPCS: ‘via Git hosting :OQIP9S
              2. OC1JLG: S3 hosting of static site
                1. OC1JML: search
                2. OC1KGU: upload site automatically
                  1. OC1KGO: -looks good on quick look: –I ref’d #1 now via search find 2
                3. OC1JLN: I ref’d #1 now by OC1JFJ
              3. OQIOZL: Dropbox page hosting
                1. OQIP6L: ref #1 ~5hrs ago by
              4. OC1JUF: Google Drive (site hosting)
                1. OC1JUW: ending operation 2016.08
                2. OC1JVP: further JotHere details link TBA here
      3. OC1H4S: dynamic :OC1H4S
        1. OC1H89: entry
        2. OC1MAJ: forum
          1. OC1MAX: instance
            1. OC1MB9: Discourse
              1. OC1MDL: entry
              2. OC1MY3: entry –Likes currently 49 so 4 of ~40
              3. OC1MDV: I ref’d #1 by investigation of ‘Cloud9 IDE :/5565#O9QG43’ (which uses it)
            2. OC1MHD: more TBA here as need
  3. OQHDU9: feature beyond basic static
    1. OQHE4A: can be done by a 1 or more of, from most preferred roughly:
      1. OQHE5W: external web service :OQHE5W
        1. OQHDVH: is especially key for ‘static (site) :OC1H5A’ due to OQHE6R
      2. OQHE55: yourself/own site
        1. OQHE6R: requires using a sufficient ‘dynamic (site) :OC1H4S’ site as ‘static (site) :OC1H5A’ is not powerful enough :OQHE6R
    2. OQHDWQ: for ability…
      1. OC1JPJ: page comments
        1. OC1JQ3: includes ‘page comments :OC1JON’ –so see that, too.
        2. OC1JON: ‘external web service :OQHE5W’ :OC1JON
          1. OC1JRP: provider
            1. OC1KPZ: entry :OC1KPZ
            2. OC1NXC: Google trends rankings
              1. OC1NXM: top,Livefyre,IntenseDebate (ending with 92+3+1)
              2. OC1O1T: matches too much other stuff:
              3. OC1NZN: so low that ‘doesn’t have enough data to show’,talkatv,HashOver
            3. OC1JS2: instance, from most preferred –constructing
              1. OC1KMG: Disqus :OC1KMG
                1. OC1KMM: Google entry
                2. OQHLZ3: popularity
                  1. OC1KMV: more than any other competitor, I see it used on the websites I visit, including, KPCC.Org, and many more.
                  2. OQHLYY: only recommendation of OQHLW2
                3. OC1N15: entry –Likes currently 76 so #1 of ~30
              2. OC1LCL: IntenseDebate
                1. OC1LEA: generic site install
                2. OC1LIF: notable pros thru cons
                  1. OC1LIP: sync with WordPress comments (when on a WP site)
                3. OC1LDX: I ref’d #1 now by OC1KPZ
              3. OC1LES: LiveFyre
                1. OC1LGR: notable pros thru cons
                  1. OC1LH4: IMHO their main website is unreadable due to so much marketing glitz
                2. OC1LGF: I ref’d #1 now by OC1KPZ
              4. OC1LKS: Facebook Comments Plugin
                1. OC1NHC: probably -Likes now 4 so ~12 of ~40
                2. OC1LPQ: notable pros thru cons
                  1. OC1LQ5: nearing as popular as ‘Disqus :OC1KMG
                  2. OC1LRM: killer: requires FB login and shares data with FB
                3. OC1LLR: I ref’d #1 by seeing on other pages as just now here
      2. OQHEFT: (web) forms
        1. OQHEGN: ‘external web service :OQHE5W
          1. OQHM1D: model else make, from most preferred — constructing
          2. OQHM28: model/make in alphabetical order
            1. OQHM2U: Wufoo :OQHM2U
              1. OQHM67: Google entry & search
              2. OQHMQV: entry with Likes 14 (so #4) of 54
              3. OQHMUY: notable pros thru cons
                1. OQHMWL: only named recommendation by Pinegrow per OQHLW2
                2. OQHMWV: on quick look, possibly pricey.
              4. OQHM3N: I ref #1 by OQHLW2 at time of parent
          3. OQHEHO: I ref #1 by OQHLW2 at time of parent
      3. OQHMZG: link management including categories & other back-links
        1. OQHN0I: –my own terminology now
        2. OQI1HG: note functionally categories/tags/keywords are essentially ‘(intra) search :OQI0TM’ for explicitly indexed words :OQI1HG
          1. OQIWEB: so ‘post category’ ‘taxonomy N0C3Y3’
        3. OQHN0W: ‘external web service :OQHE5W
          1. OQHNDP: instance JotHere homebrew
            1. OQHZIG: notable pros thru cons
              1. OQHZME: enables multiple readily unlimited websites, even static ones, to have key features
                1. OQI0M1: seen before on only better single usually-dynamic sites (such as MediaWiki) but even there never to this high level
                2. OQI0LO: of
                  1. OQHZNN: correct links to all locations participating in the service, by basically allowing replacement usual URLs to a type of URI.
                    1. OQI0Q0: even for location within the page
                  2. OQHZPQ: to further organize their content, back-links and categories
                    1. OQHZWY: even if the site is static
                    2. OQHZWJ: indeed ones which are also top in that:
                      1. OQI09W: an author is a proper category
                      2. OQI024: for at least categories, can be much richer/better as
                        1. OQHZUB: can be an arbitrary DAG
                      3. OQI03A: can & normally do combine efforts from all participating sites by both
                        1. OQI077: being collectively developed by each wiki style
                          1. OQI0ID: something never formally done before for categories
                        2. OQHZZR: combine content from all participating pages (at least by default)
                      4. OQI0HN: turns a link destination (so back-links) into another category so potentially merges the concepts
            2. OQHNDZ: definition
              1. OQHNJX: for multiple websites, even/especially static ones,
              2. OQHNEA: provides {link finding so broken link correction} + backlinks including categories organized in a DAG including authors or other people
              3. OQHNJ7: by every page needing its services for
                1. OQHNMR: augmenting the page with such functionality then includes JavaScript which
                  1. OQHZL4: ensures
                    1. OQHOFI: this
                      1. OQHNTW: the links from the page go the proper destination, be it a category definition & listing or other link destination including commonly to an anchor within a page
                      2. OQHNV7: the destination of the page itself plus each of the anchors within it are augmented with a likely-expanding properties section where, for the links to there, giving the individual and ideally count of the links to here.
                    2. OQHOFY: by loading into the page the latest full index if it’s small else by using a fancier technique as from most preferred roughly
                      1. OQHOND: looking up the appropriate index sub-file using a URL which is generated by starting with the prefix of what’s needing to be looked up
                        1. OQHOV1: thus taking advantage of the auto-scaling of a good static website
                      2. OQHOMK: consulting a traditional database accessed at single location
                    3. OQHYYG: where in the case of back-link especially category definitions, to detail & organize all that, requires its own page-else-write-up
                      1. OQHZ1G: likely-locally-composed (so by the JavaScript) from compact data delivered by the server
                        1. OQHZ95: where summaries of each link of data gotten form opening the link {also coming from the server instead of being retrieved by the client}
                          1. OQHZDL: is likely a the way to go as…
                          2. OQHZAK: pros thru cons
                            1. OQHZA0: notably faster for the client
                            2. OQHZB6: readily could contain outdated info
                              1. OQHZCE: which if a problem the client could subsequently update
                      2. OQHZEY: which the client (js) could ideally also dynamically resort & search per user criteria
                      3. OQHZIR: which could contain embedded topical ads to pay for the service
                  2. OQHZLJ: possibly inserts an ad on this page to help pay for the service
                2. OQHO0G: tracking destinations of & within it, whenever that page changes then submitting it for re-indexing.
                  1. OQHO2H: which works by removing all previous index entries to that page then reindexing the page
                    1. OQHO4K: where {if the index doesn’t map {URL (of page not location) to all index entries for it} as that is only needed on reindexing}, then the removal would take {linear time, notably to search for all references to the page within the index} so this can be optimized by removing as many as possible pages at once before adding them}
            3. OQHN1I: –my own idea as of this morn so 2017.05.24WedPst09~ :OQHN1I
          2. OQHOL1: other instance: never heard of any
          3. OQHNCW: search :OQHNCW
          4. OQHOJ2: OQHN1I applies
      4. OQI0TM: (intra) search :OQI0TM
        1. OQI1OD: note functional similarity with categories/tags/keywords per :OQI1HG
        2. OQI0U3: ‘external web service :OQHE5W
          1. OQI0V5: make+model alphabetical:
            1. OQISYN: Aerobatic keyword-search
              1. OQISYT: make
              2. OQISZ1: I ref #1 now by OQISWS
            2. OQI0VK: Google Custom Search
              1. OQI0YT: entry
            3. OQI198: Google Site Search
              1. OQI1DW: discontinued as ‘no new licenses for Site Search would be sold after April 1, 2017’ quoting OQI19H
              2. OQI194: entry
                1. OQI19H: currently a broken redirect to paragraph ‘Google Search Appliance’ :OQI19H
      5. OQJMGR: payment collecting/gateway / PayPal augmenter
        1. OQATMQ: ‘external web service :OQHE5W
          1. OQATMQ: comparison
          2. OQATNH: in alphabetical order by model
            1. OQATOQ: similar looking _
              1. OQATNR: Paddle :OQATNR
                1. OQAU8C: looks possibly useful to SimulSquad membership plans
              2. OQATO4: SendOwl :OQATO4
  4. OPK9VF: (website) ‘archive :OQSELJ’ :OPK9VF :OPK9VF

    1. OPK9VZ: service, from most notable
      1. OPK9WD: instance Archive.Org
        1. ORG358: aka The Internet Archive
        2. OPKA5C: search & entry
        3. ORG35G: entry
        4. OPKA5F: popularity
          1. OPKA5Q: very likely #1
          2. OPKA61: every ~3 weeks is mentioned on TRMS as their favorite
        5. OPKA7C: saving a new version of a page
          1. OPKA81: 1st version (so not archived before)
            1. ORR5Z4: via entering the URL into field ‘WaybackMachine’ (at top)
              1. ORR5ZG: is the only method I know of
              2. ORR5ZY: returns 1 of, from most common currently
                1. ORR69K: a URL as*/ (as happens now) which says ‘Hrm. \ Wayback Machine doesn’t have that page archived. Want to search for all archived pages under ?’ but gives no offer to save. :ORR69K
                  1. ORR6CW: I 1st noticed at :ORK86C then at ORR69K, so this seems to be the new norm alarmingly. :ORR6CW
                  2. ORR74B: workaround ORR74B
                    1. ORR76O: definition: do ‘workaround OPKATH
                    2. ORR7A9: optimized ORR7A9
                      1. ORR7BJ: definition: in the returned URL, replace the ‘/web/*/’ with ‘/save/’
                      2. ORR7MZ: uses: see from links to here as 1st use ORR7HL
                2. OPKA8H: a URL as (as happens now) (aside: ‘that URL, so including its ‘2’, is correct almost certainly :ORR63D’) which says ‘Hrm. \ Wayback Machine doesn’t have that page archived. \..\ This page is available on the web! \ Help make the Wayback Machine more complete! [<a href=”″>Save this url in the Wayback Machine</a>]’ :OPKA8H
                  1. ORR88W: aside: I’ve now unlinked that save URL here so it won’t get opened as that then causes that page to get saved so this prompt to disappear
                  2. OPKABN: -and by opening that last URL, the page gets archived.
                  3. ORR7UU: I saw this as the behavior until ‘the new norm alarmingly. :ORR6CW
                  4. ORR63D: footnote: I now notice the ‘2’ that UR would seem to be a typo compared to the URL returned by ORR69K (which instead has ‘*’) but the URL was added here by copy-and-paste so unlikely it’s a typo, moreover that URL as-is now still offers that same response so it, so that URL, so including its ‘2’, is correct almost certainly :ORR63D
                3. ORR6UD: a URL {of form Archive.Org but I didn’t note but likely same as one of the other return patterns} but with content ‘502 Bad Gateway’
                  1. ORGF1K: –has so far been very rare.
                  2. ORGF1A: 1st occurrence now ORGF7B as return ‘<body bgcolor=”white”><h1>502 Bad Gateway</h1><p>The proxy server received an invalid response from an upstream server. Sorry for the inconvenience.<br>Please report this message and include the following information to us.<br>Thank you very much!</p><table><tbody><tr><td>URL:</td><td></td></tr><tr><td>Server:</td><td></td></tr><tr><td>Date:</td><td>2017/06/12 21:45:21</td></tr></tbody></table><hr>Powered by Tengine/2.1.0 </body>’
                  3. ORGFBX: a refresh (at least 1) seems to solve this.
            2. ORR7XZ: via when viewing a page archived with Archive.Org, on that, clicking/exploring/opening a link which hadn’t yet been archived

              1. ORR82N: which gives responses 1 of, from most common
                1. ORR89Z: same save option as OPKA8H
                  1. ORR7ZZ: which I 1st write about now at/for ORR7PJ
          2. OPKACT: additional versions
            1. OPKADJ: presumably to save permanent archive space, these do not get made until 1 of:
              1. OPKAEL: Archive.Org decides to rescan the page
                1. OPKAFL: notable pros thru cons
                  1. OPKAFW: appears fully complete, at least per example ‘OLNJWD: indeed’ shows apparently {Archive.Org self-decision} archived from this page every ‘member’ group page even those not automatically displayed w/o clicking ~‘display more’ so {many: ~50}!
                  2. OPKAKM: routinely doesn’t happen soon enough
                    1. OPKAXR: so use say ‘workaround OPKATH
                    2. OPKAYC: such as
                      1. OPKAL5: for an event page, at the end else during else just before the event, so to capture all the latest plans & progress for the event before much of this could get overwritten or deleted as the event this then over
                        1. OPKAP4: as to likely be overwritten by the next-event in the series :OPKAP4
                          1. OPKB3Q: (instead of using a new URL) –a bad but still very common website practice
                      2. OPKAYQ: terms of service that have been updated and now are in use before Archive.Org has made a permanent copy
                2. OPKAQE: a user explicitly requests a resave
                  1. OPKA7L: without a login (and to a possibly a special account)
                    1. OPKARD: Archive.Org makes tries to make this impossible
                      1. OPKASK: probably so unknown users can’t waste unlimited space needlessly re-archiving the same page
                      2. OPKATH: but workaround OPKATH

                        1. OPKATR: which is: the user simply fabricates then opens the necessary ‘‘.. Save this url in the Wayback Machine’ :OPKA8H’ URL, so a URL of form[URL to save even again]
                          1. OPKBWP: trick :OPKBWP: this can be handily realized by replacing say ‘web/20160818113153’ with ‘save’ (then opening) the URL of an outdated page such as :OPKBWP
                          2. OSDIOO: sometimes this replies with ‘<html><head></head><body class=” hasGoogleVoiceExt”><h1>503 Service Unavailable</h1>No server is available to handle this request.</body></html>’
                            1. OSDIOO: but after a few refresh(es), it works
                              1. ORG5XT: after ~3 where I1st saw this at ORG5U9
                              2. OSDIS9: after 1 where I now saw at OSDE9B
                          3. ORGFK8: sometimes it replies with ‘Bummer. This url is not available on the live web or can not be archived.’ as 1st noted at ORGFHD ; 4 refreshes did NOT change this :ORGFK8
                            1. so then tried
                        2. OPKB0S: found by me 2016~ by just guessing it
      2. OPK9Z0: instance
      3. OPK9XY: instance
        1. OPK9XP: article ‘url_archive_MAXUKI: a Google Drive folder for community-archiving of content of URLs especially web pages
    2. OPKA0Y: need
      1. OPKA0U: required within ‘‘core legal contract/agreement terms & forms {for varied extensions by linking-to-here} ’NUPAPBf’