diff options
author | Yorhel <git@yorhel.nl> | 2009-02-12 22:33:11 +0100 |
---|---|---|
committer | Yorhel <git@yorhel.nl> | 2009-02-12 22:33:11 +0100 |
commit | b5e155614c43bf62079ac133e9fa5668a1746446 (patch) | |
tree | 71dba3b3ad5b285016408f3605be51ce57952071 /data/docs | |
parent | 3a79304b128c4343ada136a11b7829b3b6a87e09 (diff) |
Documentation (d4 and d8) changes
With d4 finished, d3 is now the only 'unfinished' doc page
Diffstat (limited to 'data/docs')
-rw-r--r-- | data/docs/4 | 15 | ||||
-rw-r--r-- | data/docs/8 | 19 |
2 files changed, 23 insertions, 11 deletions
diff --git a/data/docs/4 b/data/docs/4 index 71293904..2282bb0d 100644 --- a/data/docs/4 +++ b/data/docs/4 @@ -1,11 +1,15 @@ :TITLE:Adding/Editing a Producer -:INC:notfinished :INC:index :SUB:When to add a producer <p> - <i>TODO</i> + A producer entry should be created when adding a release of a visual novel made by a + producer not yet listed in the database. Producers that don't have any releases listed + in the database may be deleted after a while, so only create an entry if you're going to + link it to a release. For a producer to be listed, they're required to have at least + released one completed product. Which means that for translation projects, only add the + group as a producer when they've actually finished a project. </p> @@ -14,9 +18,12 @@ <dt>Type</dt><dd> The type of producer. </dd><dt>Name (romaji)</dt><dd> - The name of the producer in the Latin alphabet (using Romanisation or translation). + The name of the producer in the Latin alphabet, using <a href="/d5.1">romanisation</a> + in case the original name isn't in the Latin alphabet already. <a href="/d5.2">Capitalization</a> + is also important for this field. </dd><dt>Original name</dt><dd> - If the Name (above) has been Romanised or translated, place the original name here. + If the Name (above) has been romanised, make sure to mention the original (most likely + the Japanese) name here. </dd><dt>Primary language</dt><dd> The language the the producer works in most of the time. By default, it is Japanese. </dd><dt>Website</dt><dd> diff --git a/data/docs/8 b/data/docs/8 index 09f8322d..701f5f70 100644 --- a/data/docs/8 +++ b/data/docs/8 @@ -21,28 +21,30 @@ Feel free to comment about the TODO list and to suggest new features on the <a href="/t/db">discussion board</a> or on <a href="irc://irc.synirc.net/vndb"> IRC</a>. <br /><br /> -<b>Last update: 2008-12-29</b><br /><br /> +<b>Last update: 2009-02-12</b><br /><br /> -:SUB:Next version (2.2) +:SUB:Next version (2.3) <ol> - <li>Custom aditional CSS field to user pages</li> + <li>Catalog numbers for releases (done)</li> + <li>Changing release statusses from VN page using AJAX (done)</li> + <li>Random VN quotes on footer of every page (done)</li> + <li>Platform icons on homepage (done)</li> + <li>Tagging system (...will take a while)</li> </ol> :SUB:(Hopefully) soon <ol> <li>Advanced notification system</li> - <li>Some kind of tagging system (<a href="/t42">t42</a>)</li> - <li>A proper ranking system</li> <li>More VNList filters & stats</li> + <li>Release calendar</li> </ol> :SUB:Later <ol> - <li>Release calendar</li> - <li>Catalog numbers for releases</li> + <li>Filters on /v/* to exclude blacklisted and/or VNs on a users list from the results</li> <li>Producer relations</li> <li><b style="font-weight: normal; text-decoration: line-through">VN Staff and Character database</b><br /> <i>Probably not going to make it into VNDB, unless someone wants to be in charge of this</i></li> @@ -58,6 +60,8 @@ IRC</a>. <li>Automatic uploading of cover images from a URL</li> <li>Scans of the packaging for releases</li> <li>Store which fields have been changed for revisions using one-character-code indicators</li> + <li>Improved platform for fan translations (separated from releases)</li> + <li>'currently down/offline' flag for official website links</li> </ol> @@ -72,5 +76,6 @@ IRC</a>. <li>Let VNDB and Multi communicate via SQL (and use schemas to separate the tables)</li> <li>More secure login system</li> <li>Use PostgreSQL stored procedures to insert revisions (using composite types, arrays, etc as arguments)</li> + <li>Update the users.c_changes column on hiding/unhiding an item</li> </ol> |