search

jywarren / plots2

The Public Lab website!
http://publiclab.org
GNU General Public License v3.0
17 stars 2 forks source link

tabbed organization of tool and place pages, or better display of research notes #101

Closed jywarren closed 11 years ago

jywarren commented 11 years ago

This could be a way to display notes for a given tag inline on any wiki page, or it could be a way to organize the whole page into tabs.

ebarry commented 11 years ago

Tabbed organization on tool pages would be a real help for clearly presenting 1) the current state of development and current capabilities, 2) the materials list needed to assemble this tool, and 3) speculative directions awaiting further hacking.

jywarren commented 11 years ago

An introduction tab might be a great first tab, so that'd be 4 tabs. What would the tabs be named? And how would your #3 be elaborated; would people list things as on a wiki page, or what?

I think we need an example page to explore how this would work.

On Mon, Apr 15, 2013 at 4:03 PM, Liz Barry notifications@github.com wrote:

Tabbed organization on tool pages would be a real help for clearly presenting 1) the current state of development and current capabilities, 2) the materials list needed to assemble this tool, and 3) speculative directions awaiting further hacking.

— Reply to this email directly or view it on GitHubhttps://github.com/jywarren/plots2/issues/101#issuecomment-16408034 .

ebarry commented 11 years ago

Yes, an "intro tab" would be critical to clearly link the "problem statement" to the tool design.

THe goal of Tab 4 would be to clearly communicate to a technical audience -- so what would make that successful? the "next frontiers" could be a simple list (bulleted ideas or steps), or could be presented in a table format prompting people to put in "attributes" of the new features they wish existed.

jywarren commented 11 years ago

we had talked about having a kind of "problem statement" or "needs statement" -- a research note tagged "proposal" or something which would get listed (kind of like event research notes) on a tool page. People could propose something and refine it based on comments, and the list could be ranked by likes -- so if you agree that the problem should be solved, you "like" it. Once it's solved, you tag it "solved" and it drops from the list. That could be interesting...

On Tue, Apr 16, 2013 at 11:38 AM, Liz Barry notifications@github.comwrote:

Yes, an "intro tab" would be critical to clearly link the "problem statement" to the tool design.

THe goal of Tab 4 would be to clearly communicate to a technical audience -- so what would make that successful? the "next frontiers" could be a simple list (bulleted ideas or steps), or could be presented in a table format prompting people to put in "attributes" of the new features they wish existed.

— Reply to this email directly or view it on GitHubhttps://github.com/jywarren/plots2/issues/101#issuecomment-16452047 .

ebarry commented 11 years ago

this could be interesting. Is this kind of functionality, where "likes' or "solved" can adjust it's display order, possible?

On Tue, Apr 16, 2013 at 1:33 PM, Jeffrey Warren notifications@github.comwrote:

we had talked about having a kind of "problem statement" or "needs statement" -- a research note tagged "proposal" or something which would get listed (kind of like event research notes) on a tool page. People could propose something and refine it based on comments, and the list could be ranked by likes -- so if you agree that the problem should be solved, you "like" it. Once it's solved, you tag it "solved" and it drops from the list. That could be interesting...

On Tue, Apr 16, 2013 at 11:38 AM, Liz Barry notifications@github.comwrote:

Yes, an "intro tab" would be critical to clearly link the "problem statement" to the tool design.

THe goal of Tab 4 would be to clearly communicate to a technical audience -- so what would make that successful? the "next frontiers" could be a simple list (bulleted ideas or steps), or could be presented in a table format prompting people to put in "attributes" of the new features they wish existed.

— Reply to this email directly or view it on GitHub< https://github.com/jywarren/plots2/issues/101#issuecomment-16452047> .

— Reply to this email directly or view it on GitHubhttps://github.com/jywarren/plots2/issues/101#issuecomment-16459286 .

@lizbarry http://twitter.com/lizbarry

jywarren commented 11 years ago

absolutely -- that's one of the main reasons we added the "like" system, to sort by popularity. Have you "liked" anything yet?

a "solved" tag would just be another flag just like "event" so that part's easy.

On Tue, Apr 16, 2013 at 1:44 PM, Liz Barry notifications@github.com wrote:

this could be interesting. Is this kind of functionality, where "likes' or "solved" can adjust it's display order, possible?

On Tue, Apr 16, 2013 at 1:33 PM, Jeffrey Warren notifications@github.comwrote:

we had talked about having a kind of "problem statement" or "needs statement" -- a research note tagged "proposal" or something which would get listed (kind of like event research notes) on a tool page. People could propose something and refine it based on comments, and the list could be ranked by likes -- so if you agree that the problem should be solved, you "like" it. Once it's solved, you tag it "solved" and it drops from the list. That could be interesting...

On Tue, Apr 16, 2013 at 11:38 AM, Liz Barry notifications@github.comwrote:

Yes, an "intro tab" would be critical to clearly link the "problem statement" to the tool design.

THe goal of Tab 4 would be to clearly communicate to a technical audience -- so what would make that successful? the "next frontiers" could be a simple list (bulleted ideas or steps), or could be presented in a table format prompting people to put in "attributes" of the new features they wish existed.

— Reply to this email directly or view it on GitHub< https://github.com/jywarren/plots2/issues/101#issuecomment-16452047> .

— Reply to this email directly or view it on GitHub< https://github.com/jywarren/plots2/issues/101#issuecomment-16459286> .

@lizbarry http://twitter.com/lizbarry

— Reply to this email directly or view it on GitHubhttps://github.com/jywarren/plots2/issues/101#issuecomment-16459971 .

jywarren commented 11 years ago

Let's consider:

a) having tabbed:foo display notes/wiki pages for tag foo b) having the wiki page listing sorted descending by popularity, or longer than 10 entries