| # |
Jul 22nd 2009, 00:19 |
pointlessjon |
that's what i was thinking |
| # |
Jul 22nd 2009, 00:19 |
jperras |
yo |
| # |
Jul 22nd 2009, 00:19 |
gwoo |
haa |
| # |
Jul 22nd 2009, 00:19 |
gwoo |
pointlessjon: he probably has some major jetlag |
| # |
Jul 22nd 2009, 00:19 |
pointlessjon |
jperras: yo dawg |
| # |
Jul 21st 2009, 21:20 |
pointlessjon |
!log |
| # |
Jul 21st 2009, 18:43 |
pointlessjon |
we're pretty much on the same page |
| # |
Jul 21st 2009, 18:43 |
ProLoser|Work |
gotta head out for a bit |
| # |
Jul 21st 2009, 18:43 |
ProLoser|Work |
and then you would almost use filters |
| # |
Jul 21st 2009, 18:42 |
ProLoser|Work |
i mean my suggestion almost seems like 2 sets of tags |
| # |
Jul 21st 2009, 18:42 |
ProLoser|Work |
honestly how you categorize can be completely arbitrary |
| # |
Jul 21st 2009, 18:42 |
ProLoser|Work |
that too can make a huge impact |
| # |
Jul 21st 2009, 18:42 |
pointlessjon |
i totally agree, andat the end of the day it's all user interface |
| # |
Jul 21st 2009, 18:42 |
ProLoser|Work |
it's up to you |
| # |
Jul 21st 2009, 18:42 |
ProLoser|Work |
crap i gotta go |
| # |
Jul 21st 2009, 18:42 |
ProLoser|Work |
so i suggested layers to create a degree of abstraction |
| # |
Jul 21st 2009, 18:41 |
ProLoser|Work |
when code/articles/tuts are all on the same topic, i would like to see them close together and easily referenceable |
| # |
Jul 21st 2009, 18:41 |
ProLoser|Work |
in that way i don't think code/articles/tuts/snippets should be the main heirarchy, cuz i don't like that much separation of content |
| # |
Jul 21st 2009, 18:40 |
ProLoser|Work |
or similar alternative hypothesis on the subject |
| # |
Jul 21st 2009, 18:40 |
ProLoser|Work |
i don't like the idea of a working peice of code being all the way in another section from discussion articles that may show what lead up to its creation |
| # |
Jul 21st 2009, 18:40 |
ProLoser|Work |
i just think when i'm looking at code, i can find nearby the relevent documentation on people who use it, examples of how it was used, or alternatives, snippets that led to it |
| # |
Jul 21st 2009, 18:39 |
ProLoser|Work |
but that's not the point i'm emphasizing |
| # |
Jul 21st 2009, 18:39 |
ProLoser|Work |
it's all very github/chaw like |
| # |
Jul 21st 2009, 18:39 |
ProLoser|Work |
it has a team of people working on it, it has an established code section |
| # |
Jul 21st 2009, 18:39 |
ProLoser|Work |
this is an example module |
| # |
Jul 21st 2009, 18:39 |
ProLoser|Work |
i am aiming to become as successful as drupal in this endeavor: http://drupal.org/project/modules?filters=tid:75andsolrsort=sort_title%20asc |
| # |
Jul 21st 2009, 18:38 |
ProLoser|Work |
well |
| # |
Jul 21st 2009, 18:38 |
pointlessjon |
I'm not sure I'm doing this justice -- I'll just have to show you something visually -- and perhaps you could do the same? |
| # |
Jul 21st 2009, 18:37 |
ProLoser|Work |
one-off documents? |
| # |
Jul 21st 2009, 18:37 |
ProLoser|Work |
i was requestion that they establish a form of linking |
| # |
Jul 21st 2009, 18:37 |
pointlessjon |
Articles, such as tools, tutorial, snippets, are more like one-off documents |
| # |
Jul 21st 2009, 18:37 |
ProLoser|Work |
i think that's clear they do not plan to mirror that on bakery 2 |
| # |
Jul 21st 2009, 18:36 |
pointlessjon |
including all those things |
| # |
Jul 21st 2009, 18:36 |
pointlessjon |
as i understand it, code items are becoming almost like github repos or chaw projects |
| # |
Jul 21st 2009, 18:36 |
ProLoser|Work |
so that usecases and documentation can be built up around it |
| # |
Jul 21st 2009, 18:36 |
ProLoser|Work |
i'm saying keep code near it's related articles |
| # |
Jul 21st 2009, 18:35 |
ProLoser|Work |
i'm not saying cause ambiguouty by calling everything code |
| # |
Jul 21st 2009, 18:35 |
ProLoser|Work |
this is an example of how it's used |
| # |
Jul 21st 2009, 18:35 |
ProLoser|Work |
this is the code to use |
| # |
Jul 21st 2009, 18:35 |
pointlessjon |
ah yes, code will have that |
| # |
Jul 21st 2009, 18:35 |
ProLoser|Work |
'this is the tutorial |