{"action":"created","issue":{"url":"https://api.github.com/repos/WheatonCS/Lexos/issues/388","repository_url":"https://api.github.com/repos/WheatonCS/Lexos","labels_url":"https://api.github.com/repos/WheatonCS/Lexos/issues/388/labels{/name}","comments_url":"https://api.github.com/repos/WheatonCS/Lexos/issues/388/comments","events_url":"https://api.github.com/repos/WheatonCS/Lexos/issues/388/events","html_url":"https://github.com/WheatonCS/Lexos/issues/388","id":162336937,"number":388,"title":"UI ordering to help user (cf RWA)","user":{"login":"mleblanc321","id":1066011,"avatar_url":"https://avatars.githubusercontent.com/u/1066011?v=3","gravatar_id":"","url":"https://api.github.com/users/mleblanc321","html_url":"https://github.com/mleblanc321","followers_url":"https://api.github.com/users/mleblanc321/followers","following_url":"https://api.github.com/users/mleblanc321/following{/other_user}","gists_url":"https://api.github.com/users/mleblanc321/gists{/gist_id}","starred_url":"https://api.github.com/users/mleblanc321/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mleblanc321/subscriptions","organizations_url":"https://api.github.com/users/mleblanc321/orgs","repos_url":"https://api.github.com/users/mleblanc321/repos","events_url":"https://api.github.com/users/mleblanc321/events{/privacy}","received_events_url":"https://api.github.com/users/mleblanc321/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/WheatonCS/Lexos/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-06-26T17:08:42Z","updated_at":"2016-06-26T17:44:56Z","closed_at":null,"body":"Scott reordered the UI in Rolling Window (RWA) 1 -> 2 -> 3 etc.  (i like it and i think new users will too)\r\n\r\nwhile writing up scrubber (for ITM) i want to write about topics in the order that Lexos runs them, but of course, our UI does not presently reflect this;\r\n\r\nso, Scrubber (and other pages) would benefit in a like fasion?\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/WheatonCS/Lexos/issues/comments/228612999","html_url":"https://github.com/WheatonCS/Lexos/issues/388#issuecomment-228612999","issue_url":"https://api.github.com/repos/WheatonCS/Lexos/issues/388","id":228612999,"user":{"login":"scottkleinman","id":1125917,"avatar_url":"https://avatars.githubusercontent.com/u/1125917?v=3","gravatar_id":"","url":"https://api.github.com/users/scottkleinman","html_url":"https://github.com/scottkleinman","followers_url":"https://api.github.com/users/scottkleinman/followers","following_url":"https://api.github.com/users/scottkleinman/following{/other_user}","gists_url":"https://api.github.com/users/scottkleinman/gists{/gist_id}","starred_url":"https://api.github.com/users/scottkleinman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/scottkleinman/subscriptions","organizations_url":"https://api.github.com/users/scottkleinman/orgs","repos_url":"https://api.github.com/users/scottkleinman/repos","events_url":"https://api.github.com/users/scottkleinman/events{/privacy}","received_events_url":"https://api.github.com/users/scottkleinman/received_events","type":"User","site_admin":false},"created_at":"2016-06-26T17:44:56Z","updated_at":"2016-06-26T17:44:56Z","body":"Scalar is meant to present content in a non-linear fashion, so it stores pages as nodes that can be linked to or embedded in other nodes. An example might be a page containing a video in the middle of some textual discussion. You could simply make the video part of the page node and be done, but what if you also wanted to embed the video in Lexos? For this, it would make sense to make the video its own node and then embed it separately in both your Scalar page and Lexos. Otherwise, Lexos would have to display the entire page, both text and video. Likewise, if you intend the content of a page to be displayed within Lexos, that might prompt you to write a short version and then write a longer version for reading as part of the Scalar book. My last point is about navigation within Scalar. Scalar uses the page title to construct its navigation links. That might cause you to come up with a page title that makes sense as a navigational link, but it might not make sense when taken out of that context and displayed in Lexos. Of course, down the line, we might add flags in Lexos to hide or replace the page title, but they're not there yet. "}}
{"actor":{"display_login":"scottkleinman"}}