Web and app big ideas

Design idea for an Internet-connection-freeing app to help with Internet access problems

Local copies of recently used web files can be downloaded to use if offline, with the app and when offline, using the application's local proxy-ing Domain Name System (DNS - the phonebook of the Internet) server, change results for (human-readable) domains to go to (the resolved IP address of) the application where it responds with cached local copies from its local web server on the device.

↪️ Idea 2

Some sort of app in the browser to make

To make an app running on WebAssembly and JavaScript, to give users "core tools" of computer systems. WebAssembly (.wasm) to be able to use the tool executables. JavaScript (.js) and some HTML to have a Web UI, between that some JavaScript "glue" WebAssembly functions.

To make a 2nd app that's a wiki website of quotations of text, gives users a built-in editor (in WebAssembly) and uses Git to push some commits, to put changes into the website source repository.

↪️ Idea 3

An additional idea

Website page... ➡️ data: URL page 📄 for opening an offline Web Storage resource/page with JavaScript and .shadowRoot host property...

that resource embedded into a shadow Document Object Model tree attached with a "template" element (node) with an attribute, this defined declaratively in the normal HTML DOM tree of the page 📄 -

<div id="shadow-root-parent-host-element">
  <template shadowrootmode="open">
    <span>An element in shadow DOM tree, shadow set to open to display in the browser's visible page.</span>
  </template>
</div>

↪️ (next)

and XMLHttpRequest GET request for page resources to download, for offline Web Storage with the page resources.

Custom HTML elements extend the base built-in elements, typically with a JavaScript class that creates a shadow tree under the host custom element - Mozilla Developer Network's Web Docs page (documentation resource site for web technologies).

↪️ Idea 4

How to have pages in this knowledge & information project placed

  • Not to use Inline Frames to put into the pages/index.xhtml from pages/slides- * .html (.md)... use (expanding downward 👇) navigational lists - like mind-maps - of embedded knowledge, framed (group of slides) pages, the pages listed ⬇️... lists ↕️ next to other lists ↕️, listing the history of pages looked at, watched or used - going left ⬅️ or ➡️ right to navigate the "frames" - like the context of exploring 🗃 where the location 📂 for a file 📄 is.

    • Knowledge framed into page 📄 of slides.
    • Left ⬅️ or ➡️ right - other list of pages.

↪️ (next)

  • Mermaid, a JavaScript-based diagramming and charting tool that uses Markdown-inspired text definitions in knowledge pages (?).

    <pre class="mermaid">
      mindmap
      [...]
    </pre>
    
    <script type="module">
       import mermaid from 'https://cdn.jsdelivr.net/npm/mermaid@11/dist/mermaid.esm.min.mjs';
       let config = {startOnLoad: true, theme: 'neutral', securityLevel: 'antiscript' };
       mermaid.initialize(config);
    </script>
    

    </body>