During POC, using wiki-in-iframe might be enough, yet wiki has number of usability issues for our case of “documentation on tips of your fingers”. Here are random notes on dedicated frontend:

HUD visualsation notes:

• Context links scroll from bottom to up, 5 last are shown
• Сontexts are clickable, expandable to corresponding F1Memo
  • keyboard focus is at that F1Memo
  • cursor location is at the same spot the user left it at last edit
  • autosave
• Contexts that have no F1Memo are on the right. Contexts with F1Memo are on the left
• F1Memo screen can be split into two, with “active” on left and “standby” on right
  • Pressing ESC would cause the F1Memo to disappear (and “Close” to become back “Edit”)
  • If the user never opened the F1Memo, then popup is pushed (once)
  • If someone edited the F1Memo, then its link has “new” sign
    • Updated Memo has button “Proofread”. In that mode there is additional column on left that shows diff status. Changed lines have “zoom glass with red question mark inside” mark. As user moves cursor off the changed line, the question mark in zoom glass becomes green V sign, and disappears after a second. If there still are “unreviewed” changes above or below, then on top or bottom of the “diff status” column there appears arrow with smaller “zoom glass with ? mark”. Clicking on these would jump the text, so next changed line is in the middle of text area.
  • Other users, as they get into the context, will see that the Memo was changed, again, with popup (once) and “Proofread” button
  • Memo might be set as “Mandatory to read” or “Proofread ASAP”. In both case it will cause immediate popup for all users
  • Memo path:
    • starts with UNIQUE_ID, that is set by sysadmin?? Issued by whom?

A user might be connected to several F1x sites, with different contexts environments. Fx buttons might open corresponding one handily. Corporate users are likely to require its Memos to be kept on their sites, whereas family Memos are likely to be shared with family members.
Users might want to put general knowledge notes into private f1x site, as their private notes. If cross-site references are allowed, Memos will get cached on foreign site, with ability to fork.

• Site per user or team
• Site might “export” contexts to foreign site or/and allow cross-reference
• Memos sharing between sites might be “disabled” (e.g. not shareable), shared-read, shared-edit (exclusively or collaborately/live)

Static Memos keep human-oriented information. Alive Memos serve as programmable information piece for various parts of system, extending IaC methodology, with Memo documentation advantages. Alive Memos are to bridge human informality to computer-friendly data structures.

• Recipe (changing amount of ingredients or portions recalculates other values automatically. Bonus for separate metric/imperial units switch)
• Reminder to some event (shows remaining time, allows setting timer, send notification)
• Grocery shopping list (allows reset list, add check marks, arrange list according to the chain products placement on shelves)
• F1x query
• Tasks (status, deadline)
• Variables list for argocd-driven farm
• Appointment with time, link to issuer contact Memo, geolocation, buttons to confirm/cancel, additional info
• Files, with Delete, Rename buttons
• Must-read Announcement that requires read confirmation and keeps track on who read it
• a Stock (or some other commodity) price threshold notification
• Photos selection (add/remove photos, by tag, by date, by geolocation)
• Photo (add/edit comment, add/edit tag)
• Movie (add/edit comment, subtitles, audio track)
• Need for transportation from geopoints A to B at certain time (sends broadcasts in two endpoints, shows bus routes, offers to run waze)

• special Alive Memo that has bio, geo, tags regarding the person/site

• Memos might be shared (“sent”) to other users/sites, those notifications are called mEmails
• mEmails can be “broadcast” to users by geolocation or by tags in “profile” memo
• Notifications about these arrive into special “incoming” “Alive Memo” - depending on “relevancy” (known sender, known “spammyness”, urgency, geo-location), out-of-order notification is shown. User then might reference that by-definition foreign Memo somehow.

Use case example:

• Manager wants to have online meeting. He creates alMemo for the meeting with time, zoom link and list of participants and shares it (sends mEmail) to them. Participants get mandatory ASAP notification about changes in “incoming” alMemo (with link to the new alMemo). Then can interact with it and might answer “ok/undefined/unsure/can not present”. The answers are collected by the alMemo and are visible to the owner.