21 Matching Annotations
  1. Sep 2022
    1. Table help

      πŸ’¬ Help is needed for sure. This is easily one of the most convoluted processes in the campus Guide solution. No fault to this KB for trying.

      I think a typical user would not see some of this content as "tables," so I wonder about restructuring this to go into use cases.

    2. Course List Functionality/Features

      πŸ’¬ Screenshots for how each of these look when implemented in Guide would be very, very helpful.

      These features / options are a sticking point in working with tables in course leaf.

    3. 1c.When all the courses needed are populated, click the green 'OK' button to close the table editor.

      πŸ’¬ Something in here stating that all the options for an row/item in the table will be described later in this article, or in another article - would help here.

    4. Help not included in this document.

      πŸ’¬ Fair enough. This seems to suggest that there is help elsewhere. Is there? I suspect there is not - in which case maybe a statement reading: not typically implemented, consult with guide people for more information around use case and implementation.

    5. The following are used.

      πŸ’¬ A definition of each of the typically used table types could be useful. Some examples would be great. Another architecture for this information might break each type out into a separate article.

    6. Building

      πŸ–‹οΈ~~Building~~ Creating OR Inserting

      πŸ’¬ When and where would you do this? Examples? E.g. Inserting a course list in... IDK where else you would put a course list expect in the requirements tab πŸ˜†.

  2. Jan 2018