Affects Version/s: None
Fix Version/s: 0.9.177
Google Code Issue ID:3999
Originally reported on Google Code with ID 3999
What archive revision are you testing on? (See the version label in
the footer, for example v0.8.13.8.)
If appropriate, enter the URL of a page where the problem can be seen:
http://test.archiveofourown.org/skins/### (skin show)
http://test.archiveofourown.org/skins/###/edit (skin edit)
http://test.archiveofourown.org/skins/new (skin new)
http://test.archiveofourown.org/skins/new?wizard=true (skin new wizard)
What steps will reproduce the problem?
1. Log in
2. Hi, username! > My Dashboard
4. Create Site Skin
5. Fill in a title and some CSS
7. Look for the navigation in hopes of getting back to your skins
9. Look for the navigation in hopes of getting back to your skins
What is the expected output? What do you see instead?
On the skin show page:
- The navigation options used to be positioned on the right, like the rest of our navigation,
and the options were Work Skins, Public Skins, Remove Skin, My Skins, Create Skin.
- The options are currently positioned on the left and they are Revert to Default Skin
and Create Site Skin.
- I'd expect them to be Revert to Default Skin, My Site Skins, My Work Skins, and I'd
expect them to be on the right. I'd also expect them to be at the top of the home header
module, since that's where the actions usually are in such modules, and the icon should be directly after the h2. (See screen shot.)
On the skin edit, skin new, and skin new wizard page:
- The navigation options used to be Work Skins, Public Skins, Remove Skin, My Skins,
Create Skin, Use Wizard Instead?
- The options are currently Revert to Default Skin, Create Site Skin, Write Custom
CSS, Use Wizard.
- I'd expect them to be Revert to Default Skin, Write Custom CSS, Use Wizard, My Site
Skins, My Work Skins.
(Note that Revert to Default only appears if you're using a skin, which is correct.)
Also, on all skin indexes:
- The copy currently says, "A site skin lets you change the way the Archive looks in
your browser, so you can customize your reading experience. You can use work skins
to customize the way your own works are shown to others."
- It's been brought to our attention that this is both fic-centric ("reading experience")
and assumes the user is browsing visually ("looks in your browser" – work skins cannot
have different media types, so "shown" is probably okay), even though we also allow
users to create stylesheets for any media type: http://www.w3.org/TR/CSS21/media.html#media-types
- If you wanted to get ambitious, the My __ Skins indexes should probably be home zones
with spiffy header modules.