Update:Remora Dashboard
What's done
here follows a table. Once we've moved from "interactions" to "pages" we can split stuff up into pages, but we're not there yet.
See also Remora Interactions and Remora Schedule
RC - Radiant Core
| Interaction name | Mockup ? | HTML ? | tests ? | cake ? | l10n ? | visual refresh ? | audit ? | integration ? |
| Major user interactions | ||||||||
| top/home/index | DONE | sancus | sancus | sancus | ||||
| search | DONE | clouserw | clouserw | |||||
| browse | DONE | sancus | sancus | sancus | ||||
| Display Add-on | DONE | DONE | sancus | sancus | ||||
| Forums | DONE | mark | mark | mark | mark | |||
| Minor user interactions | ||||||||
| Register | ||||||||
| Comment | ||||||||
| Review | ||||||||
| Rate | ||||||||
| Subscribe | ||||||||
| Recommendations | ||||||||
| Favorites | ||||||||
| Major developer interactions | ||||||||
| main developer page | N/A | fligtar | fligtar | fligtar | ||||
| Submit new/update | N/A | fligtar | fligtar | fligtar | ||||
| Update metadata | N/A | fligtar | fligtar | fligtar | ||||
| Minor developer interactions | ||||||||
| Statistics | ||||||||
| Feedback | ||||||||
| Major admin interactions | ||||||||
| Admin Review | ||||||||
| Admin Feedback | ||||||||
| Minor admin interactions | ||||||||
| Review add-on history | ||||||||
| Review user history | ||||||||
| Manage user privelages | ||||||||
| Manage add-on blacklist | ||||||||
| Manage categories | ||||||||
| Manage forums | ||||||||
| Manage comments | ||||||||
| Manage reviews | ||||||||
Notes
Mockup
A photoshop mockup of the page. This mostly applies to Radiant Core.
HTML
The page as an HTML layout, this is usually completely static, ie the pages that Radiant Core is giving to us. Not completely necessary if you happen to be doing the page dynamically first.
tests
Tests related to this interaction, any WebTestCases for the page, unit tests for its Controller or Models, etc.
cake
Basically have the page functioning in the cake app - Get the proper data outputting from the database to the page, the mockup formatted as a view, controller functions made, etc.
l10n
no static strings, everything coming from the database, gettext-enabled, etc.
visual refresh
audit
Once html has been written, it needs to be validated and cross-browser compatibility needs to be checked. The site doesn't need to look perfect in IE, but it doesn't want to look horribly ugly either. Maybe that comes under Audit though? Yes it does --sancus. ++linkchecker;
integration
<shaver> means it's checked in, tests are added to the automatically run list, and it's part of the pull on the staging server