Chat on framework between Machine and I (plus some input from Brourd and Firedrake):
Machine, mind discussing some ideas I have for the EternaU structure? [6:54 PM]
machinelves: lfp6 what’s on your mind? [6:55 PM]
LFP6: Well, start from the front back, I suppose [6:56 PM]
LFP6: Course listings: Topic (ex. Eterna), topic area (ex. game tips), then course list, which can be filtered based on more specific areas [6:57 PM]
machinelves: please clarify terms “Topic” and “topic area” [6:58 PM]
LFP6: Topic is the most general, then topic area specifies more of the subtopic [6:59 PM]
LFP6: But not as specific, as say, boosting tips [6:59 PM]
machinelves: is this a nested menu? [7:00 PM]
machinelves: i.e. is course list a child of topic area, which itself is a child of topic? [7:00 PM]
LFP6: Here: http://prntscr.com/2thinb [7:01 PM]
machinelves: @lfp6 thanks! in that screenshot, is the 3rd level the ‘topic area’? ( home -> topic -> topic area -> course itself ) [7:05 PM]
LFP6: Yeah [7:05 PM]
LFP6: I forgot to mention home. [7:05 PM]
LFP6: The last one will just be a filter of level 3, as I mentioned [7:05 PM]
machinelves: lfp6 too many nested menus in cascading can be hard to navigate. maybe limit menu to home -> category / topic, and keep sub category / topic area & individual course links embedded in level 2 page [7:09 PM]
LFP6: @Machine: All right, I could live with that… Maybe use tabs, nested filters, or just go with 2 levels of catigorization? [7:11 PM]
machinelves: we want it to not be overwhelming, and while we have a small amount of content, we don’t need deep nesting [7:11 PM]
machinelves: i think one level of menu categorization is good, people are familiar with that layout [7:12 PM]
LFP6: @Machine: All right. [7:12 PM]
machinelves: then once you’re at ‘eterna’ or ‘science’ or ‘cooking’ or whatever, you see a page with subcategories / topic areas & individual course links on same page, or alternatively sub category / topic area section links to pages with individual course links. but we want to minimize total # of clicks to course access [7:14 PM]
LFP6: Yes [7:14 PM]
LFP6: Maybe each course would actually be the class series? [7:14 PM]
machinelves: probably i’d either nest the menu 3 levels with click -> page with course links + click -> made it to course page, or 2 level menu with click -> page with topic are & individual course links + click -> made it to course page [7:15 PM]
machinelves: *area [7:15 PM]
firedrake969: Khan Academy has 5 nested things [7:16 PM]
firedrake969: Well, four. [7:16 PM]
machinelves: khan has a nicer menu [7:16 PM]
firedrake969: Yeah [7:16 PM]
firedrake969: You do topic -> subtopic -> subsubtopic -> vido [7:16 PM]
firedrake969: video* [7:16 PM]
LFP6: Now, as for the course itself, here’s what I’m thinking: Overview/header (title, description, picture, teacher, original class date, link to class series if applicable), then the material (original chat, clean chat, formatted course, video, examples, pictures, code snippets, whatever else) [7:16 PM]
LFP6: However, for the chats/boiled lesson, I think it would be better not to use the current UI/UX. More in the style of this: http://prntscr.com/2thnzu [7:18 PM]
machinelves: ya, all those categories sound good to me [7:18 PM]
LFP6: Easier to read on a light, less busy and flash background [7:18 PM]
machinelves: that depends on the person. i have photosensitivity, the light on dark is easier for me personally. though it is true that light text on dark bkgrd is notoriously fuzzier than dark on light. they just found out it is because our brains perceive light objects as being larger in size! [7:20 PM]
machinelves: i find moving to a different UI palette confusing, i actually would have preferred not changing the wiki to traditional white bkgrd palette myself [7:21 PM]
Brourd: Well, Nando does have a tron version of the wiki [7:22 PM]
machinelves: but i understand your point [7:22 PM]
machinelves: hehe [7:22 PM]
LFP6: @Brourd: Hi [7:22 PM]
Brourd: Lots of Neon, dark blue. Not too bad [7:22 PM]
LFP6: lol [7:22 PM]
Brourd: LFP6: Hello. [7:22 PM]
machinelves: i’ll check it out! i remember he pushed for formatting order in the wiki so we could skin it [7:23 PM]
machinelves: to individual pleasing [7:23 PM]
Brourd: I think the only problem was something to do with the format while editing. [7:23 PM]
machinelves: ya if you specify text size instead of using headers, it breaks CSS of skin [7:24 PM]
Brourd: http://userstyles.org/styles/86678/et… [7:24 PM]
machinelves: tada! thanks brourd! [7:24 PM]
LFP6: So is that good with you machine? [7:28 PM]
machinelves: @lfp6 are you talking about main site design or a weebly instance, btw? [7:28 PM]
LFP6: Main site, was usig Weebly to show you because it’s a visual I already have [7:28 PM]
machinelves: kk thanks for clarification [7:28 PM]
machinelves: yes, great work thinking of content types, we’ll need all these included in the UI, and also good to know what info to start tracking for each class [7:29 PM]
machinelves: i’d add a post to forum of content types for class page & overview [7:30 PM]
firedrake969: Don’t think the EteRNA University should interfere much w/main site [7:31 PM]
LFP6: I think before we can think of content types, we need to figure out what content we have… [7:31 PM]
LFP6: Why not Drake? [7:32 PM]
machinelves: code snippets, screenshots, transcripts… these are content types [7:32 PM]
LFP6: Ooooh [7:32 PM]
LFP6: Yeah [7:32 PM]
firedrake969: The main site’s good as it is [7:32 PM]
firedrake969: and a puzzle menu doesn’t have much to do with a course list [7:32 PM]
LFP6: But what’s wrong with expanion? [7:32 PM]
firedrake969: I never said anything’s wrong with expansion [7:33 PM]
machinelves: the devs will be able to speak to what gets put in a menu and what gets nested in pages [7:33 PM]
firedrake969: Yeah, true [7:33 PM]
LFP6: What did you mean by your comment, Drake? [7:33 PM]
machinelves: topics & topic areas will be developed as we get class content [7:35 PM]
firedrake969: @LF Sorry, I meant the layout [7:37 PM]
firedrake969: Shouldn’t call for a site-wide revamp of layout [7:37 PM]
LFP6: Oh, no! [7:37 PM]
LFP6: Certainly not [7:37 PM]
machinelves: lfp6 i think fire means main site is not going to get an overhaul to look like weebly, that screenshot as you said was just to show me menu nesting [7:37 PM]
firedrake969: I misread the chat, oops [7:38 PM]
firedrake969: sorry [7:38 PM]
LFP6: @Machine: Yeah, I got that [7:38 PM]
LFP6: That’s fine [7:38 PM]