Documentation

"Nameless" Things: While every Thing clearly must have an OID, for many Things, the concept of Name is (or at least, seems to me to be) unnecessary, and even confusing.

_isNonEmpty doesn't produce expected results with Text: Intuitively, users are going to expect _isEmpty and _isNonEmpty to do appropriate things with Text Properties -- that is, test the string length.

_QLLink linebreak is not obvious:

Collection Reference: It took me way too many clicks to find documentation for Collections. It exists, but only as part of Creating Your Own Spaces. Seems to me that that info belongs in a top-level reference section, perhaps folded in with Types.

Console should have a "help" command: Xavier expected to be able to type "help" at the Console, and get a list of available Commands. That's a totally reasonable instinct, and I suspect most folks used to a CLI will expect it to work.

Documentation / Help should be more discoverable: The "Help" link at the bottom can be challenging to notice.

Documentation for Invitations is now wildly out of date: See the documentation page -- all of the images are now incorrect, and some of the details of the workflow are as well.

Documentation for Pages: When looking at a space, the first visible things are "Pages" and a button "Write a Page". I can't find any documentation on what these are for or how to use them. Either Pages shouldn't be so visible any more, or there needs to be similarly high visibility documentation.

Does Edit Width work on mobile? : In the attached screenshot, all properties have been set to Edit Width 1. They still look awfully wide, though.

Floating point formatting missing from documentation: It should at the very least be mentioned under _divideBy, and probably in the main formatting page as well.

I should be able to define "Help Pages": This is basically an Epic, and should be broken down into stories.

I should be able to get to Querki Help from the Menu Bar: That is, there should be a Help icon in the Menu, and the menu should have Querki Help in it.

I should be able to open/close all Categories in the Documentation by Category page: Request from Eric -- he'd like a way to open all of the categories up, so he can use the browser's find-in-page.

I should be able to plug my Space's Help pages into the Help menu: That is, there should be a straightforward way to code my own Help pages such that they show up in the Help Menu

I should be able to see help side-by-side with Querki: Help should open in a side-panel, rather than a separate tab -- it would be much more usable.

Learning Querki introduces Things and Models too abruptly: From Abby: It dives right into Things and Models and Instances, without a lot of explanation. I speak enough programming to guess at why you're assuming that's readily comprehensible, but I think they all require more explanation and examples, along the lines of "The Thing is the top layer, and here are several examples of Things, and then the Model is the next layer and here are several examples of models..." with each of those getting a page's worth of detailed explanation.

No documentation for the Show Thing Command: Xavier points out that there is no usage documentation for it -- now that the Console is open for general use, all Commands should be documented.

Querki should have a mechanism for contextual help: We need to have some way for users to ask, "What the heck is that?"

Documentation for _greaterThan refers to _lessThan: Probably left over from a cut-n-paste.

Documentation for _instances is broken: Not sure what's going on, but it's showing if errors, so there's probably an edge case I haven't thought of.

Documentation for _join doesn't work: Dumb bug: the URL _join is being used by the join-a-space function. We probably need to rename that page...

Documentation for Types doesn't display properly: Since they don't have a Default View, you just get their raw Properties, rather than a nice-looking display.

Function documentation is messed up: Pointed out by Eric, but I'd vaguely noticed it myself recently.

I should be able to see the system functions, categorized sensibly: The list of functions has gotten too large to easily internalize. They need to be grouped in order to be usable.

The Implementation Functions are currently visible in the alpha list of Functions in Help: My initial attempt to hide them seems to have failed. Why?

There should be a clear link to the Terms of Service: After you agree to the Terms of Service, there is no obvious link to get back to it again. Users should be able to find it.

There's no obvious way to get to the Documentation space.: There's no simple button or action that will take me to the Documentation space.

Types need documentation in Create Property: Users have begun using Types that aren't intended for general use, such as Plain Text Type, too broadly. We need the Create Property pane to show some documentation of what the selected Type is, so they don't go down ratholes by accident.

Width documentation is broken : https://www.querki.net/help/#!How-to-Control-the-Width-of-something-in-my-Text

This page claims to explain how to make columns. But the proposed method doesn't work, not even in the example given!

Wording tweak for _filter doc: The first, bolded line of documentation for _filter is 'Filter out non-matching elements of a collection'. While technically true, this phrasing was really easy for me to mis-parse when skimming, so I ended up with the inverse of what I wanted. Suggest rephrasing, perhaps as 'Remove non-matching elements of a collection'.