Pattern: Multiple fields, or one big field?
1 view
Skip to first unread message
Eliezer Israel
May 15, 2012, 12:49:05 PM5/15/12
to pattern-rep...@googlegroups.com
I'm facing a question here. Whether to expicitly make the input for patterns multiple fields (e.g. context, problem, solution), or leave it as one big field. As one big field, we can still provide on-screen guidance for the user as to what to enter.
A strong reason why I'm asking the question, is that I'm bumping up against the natural limits of wordpress. Of course, everything is possible, but WP just wasn't meant to be a multi-user flexible schema CMS, and the kind of things that I have to do to get it there are rather ugly.
What comes (relatively) easy is title/content, like a post. Not too terrible after that is adding the front end for taxonomy (scale, free tags).
Is that good enough for alpha?
If we need more structure than that, we're going to have to meditate on tooling again, and make a decision. In any case, the alpha may be the "one to throw away" and that would be just fine.
L
A strong reason why I'm asking the question, is that I'm bumping up against the natural limits of wordpress. Of course, everything is possible, but WP just wasn't meant to be a multi-user flexible schema CMS, and the kind of things that I have to do to get it there are rather ugly.
What comes (relatively) easy is title/content, like a post. Not too terrible after that is adding the front end for taxonomy (scale, free tags).
Is that good enough for alpha?
If we need more structure than that, we're going to have to meditate on tooling again, and make a decision. In any case, the alpha may be the "one to throw away" and that would be just fine.
L
Michael Mehaffy
May 15, 2012, 1:14:51 PM5/15/12
to pattern-rep...@googlegroups.com
Lev,
How about going with one big field, parsed into subfields with keyword tags? In effect a kind of script:
e.g.
DISCUSSION: Text here etc.
THEREFORE: Text here etc.
Cheers, m
--
Michael Mehaffy
Michael Mehaffy
Theo Armour
May 15, 2012, 3:10:02 PM5/15/12
to pattern-rep...@googlegroups.com
Lev
>> How about going with one big field,
I agree with Michael.
If you use multiple fields, then you rely on the intelligence of user to put stuff in the right place.
If you have a big text box, then you rely on your intelligence to learn to search and parse the stuff.
I would rather bet on Lev then bet on the user…
Theo
Reply all
Reply to author
Forward
0 new messages