Difference between revisions of "Design"
From Dreamwidth Notes
(adding link to VIV) |
Foxfirefey (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | This is the page for links to documentation on the Dreamwidth design process, from beginning to end. | + | {{Design Links}} This is the page for links to documentation on the Dreamwidth design process, from beginning to end. |
If you're interested in doing feature design (how something should work) for Dreamwidth, you can check out the [http://www.dwscoalition.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=substring&value0-0-0=needs-spec&field0-1-0=flagtypes.name&type0-1-0=substring&value0-1-0=%3F needs-spec:?] flag in the Bugzilla install. If you're interested in doing visual design (how something should look), you can check out the [http://www.dwscoalition.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=substring&value0-0-0=needs-design&field0-1-0=flagtypes.name&type0-1-0=substring&value0-1-0=%3F needs-design:?] flag. With both of these, if there isn't an email address listed next to the flag, it's up for grabs, and can be claimed by anyone. | If you're interested in doing feature design (how something should work) for Dreamwidth, you can check out the [http://www.dwscoalition.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=substring&value0-0-0=needs-spec&field0-1-0=flagtypes.name&type0-1-0=substring&value0-1-0=%3F needs-spec:?] flag in the Bugzilla install. If you're interested in doing visual design (how something should look), you can check out the [http://www.dwscoalition.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=substring&value0-0-0=needs-design&field0-1-0=flagtypes.name&type0-1-0=substring&value0-1-0=%3F needs-design:?] flag. With both of these, if there isn't an email address listed next to the flag, it's up for grabs, and can be claimed by anyone. | ||
You don't need to know how to code in order to do a spec or design mockups; you just need to be willing to take feedback from the community and from DW staff, work in an iterative fashion to incorporate that feedback, and be willing to keep a few basic principles in mind. Mark and Denise are both also very willing to explain what they had in mind, if you're not entirely certain what the purpose for a feature or function is or what it should do. | You don't need to know how to code in order to do a spec or design mockups; you just need to be willing to take feedback from the community and from DW staff, work in an iterative fashion to incorporate that feedback, and be willing to keep a few basic principles in mind. Mark and Denise are both also very willing to explain what they had in mind, if you're not entirely certain what the purpose for a feature or function is or what it should do. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category: Design]] | [[Category: Design]] | ||
Revision as of 01:18, 12 January 2009
Design Pages
This is the page for links to documentation on the Dreamwidth design process, from beginning to end.
If you're interested in doing feature design (how something should work) for Dreamwidth, you can check out the needs-spec:? flag in the Bugzilla install. If you're interested in doing visual design (how something should look), you can check out the needs-design:? flag. With both of these, if there isn't an email address listed next to the flag, it's up for grabs, and can be claimed by anyone.
You don't need to know how to code in order to do a spec or design mockups; you just need to be willing to take feedback from the community and from DW staff, work in an iterative fashion to incorporate that feedback, and be willing to keep a few basic principles in mind. Mark and Denise are both also very willing to explain what they had in mind, if you're not entirely certain what the purpose for a feature or function is or what it should do.
