|
|
Post by samjohnsson on Feb 16, 2013 3:06:39 GMT
The next deploy will most likely have a new header. The rest of the pages will still be the same. Go, take a look. |
|
|
|
Post by Wrangler Dash on Feb 21, 2013 4:53:03 GMT
I'm excited about dropdown menus!
Granted, they aren't first on my usability wishlist, but they look like a handy piece of functionality.
|
|
|
|
Post by samjohnsson on Feb 21, 2013 13:37:37 GMT
Now I'm curious - what is first? (and second?)
|
|
|
|
Post by Wrangler Dash on Feb 23, 2013 5:34:54 GMT
In no particular order, things around the top of the list...
-- Mandatory work type categories. Even if any functionality that requires them is a long way off, we want to be able to get there and say "the moment has been prepared for."
-- A useful front page. Prominent display of the latest news posts, maybe a rotating-on-refresh set of "AO3 Tips" answering common Support questions and drawing attention to useful features (like the tag FAQ!), that sort of thing.
-- Clickable "?" popups next to all the tag fields on the Post Work page, giving a little bit of information to head off the most basic errors. Let people know about the availability of "&" tags in the Relationship field, explain in the Fandom field that you tag crossovers by putting in both fandoms separated with commas, and so on.
-- Ability to subscribe to tags and get a customized feed of all the results. A working one. The content of the RSS feeds doesn't always line up with the content of a search (and not in the "it lags because RSS feeds are not instantaneously updated" sense), which is frustrating.
-- Many of the wishes revealed in the tag wrangler survey.
Wrangler ability to manually adjust how series tags are alphabetized used to be on the list, then we actually got it, which was awesome. Same for public tag pages. The batch-wrangling abilities currently being coded look like the answer to another. So I'm still hopeful for the rest of these.
|
|
|
|
Post by samjohnsson on Feb 23, 2013 19:52:36 GMT
* There might have been a mockup coded for work media. Alpha-internal proof-of-concept start-of-argument, but there is at least one coder pounding on it in their copious spare time.
* God in heaven, yes. The 00s called, they want their front page design back. This is a thing I've been muttering for over a year at this point. I do know there's a pull request that will at least pull the main twitter feeds on to that page, and I think pull the news up as well.
* uh, in Default and Reversi, those (?) are there next to the tag fields. And they all contain a link to the tag FAQ, which, as Mei noted, is being reworked. I'm confused.
* Tag feeds
* * Tag feeds only include new posts, not updated chapters, by design - theorycraft says users can then subscribe to the specific work if they decide it doesn't suck.
* * because our feeds don't have authorization (and many readers wouldn't know what to do with it), we can't include the "restricted to archive users" works, which is a whole nother bunch of works not shown, depending on your feed.
* * I would kill for a customized feed that a user can choose what goes in, but scalability is a huge concern for that, since it would add, at this moment, 132,000 feeds to the server demand.
* I will say, some of that survey was enlightening for the committee. Which is very much a good thing.
|
|
|
|
Post by Wrangler Dash on Feb 24, 2013 1:24:02 GMT
* "At least one coder pounding on it"...well, that's better than nothing! I wish it were happening faster, but the question of how coder resources are allocated is a whole other deal (and one I don't know much about beyond hearing secondhand complaints). * See, I had even forgotten they had a Twitter. This would be an important thing to display prominently! * Oh, hey, there they are. Okay, change that to *better* popups. Insert general grumbling about poorly-written AO3 documentation here. * Comparing the Harry Potter feed on DW and the latest works on the tag on AO3. Lack of inclusion for chapter updates explains the things I see missing here. And not including restricted works is understandable. ...though I'm not buying the "individual subscriptions will take care of it!" theory. Think of all the fannish people who won't read WIPs, for whom the post reporting chapter 10/10 would be the one they cared about. Or the people who subscribed to a feed yesterday without backreading the entire tag first, and as a result will never find out about the multichapter fic due to update tomorrow. * I'm glad there's new awareness, and hope good things come of it. |
|
|
|
Post by samjohnsson on Feb 24, 2013 1:42:20 GMT
* The problem is that there's only a few coders who've banged on the code long enough to be familiar enough to bang on the major bits. And at this point, what needs done is all major bits. Work type is pretty damn basic code - if something in that breaks, it'll get ugly. And they really don't have the people to train. (I'm technically a coding volunteer, so I can bang on the Support page when necessary. Ask me offlist some of my feelings as a CodeVol.)
* Twitter
@ao3org for general updates
@ao3_status when you want to want to watch sysadmins panic. (and support-ish questions are answered at both addresses)
@ao3_wranglers ...is fairly self-explanatory.
There's tumblr channels, but buggered if I can ever find them.
* Docs workgroup is hopefully getting a fire lit under them, and Mei's looking for suggestions on the Tags one.
|
|
|
|
Post by Feeding on Feb 26, 2013 9:49:58 GMT
And not including restricted works is understandable. Not really. I can follow my email account I have with my university via feed, so there must be a way to follow a feed restricted to certain user groups. Yes, on FFN I have set the feeds to only serve me complete stories (for certain characters, ratings and word lengths - subscribing to the filtered feeds is so nice). |
|
|
|
Post by samjohnsson on Feb 28, 2013 18:46:06 GMT
And not including restricted works is understandable. Not really. I can follow my email account I have with my university via feed, so there must be a way to follow a feed restricted to certain user groups. What feed reader are you using? Because, yes, the ATOM standard supports authentication, but not all readers do. They actually, because they have relatively few filtering terms, maintain separate feeds. Brokeback Mountain everything v. complete: www.fanfiction.net/atom/l/2267/3/0/0/1/0/0/0/0/0/www.fanfiction.net/atom/l/2267/3/0/0/1/0/0/0/2/0/The web address changes and serves a different .atom file. The AO3 might be able eventually to do similar, but it certainly won't be able to do it for every search variation. |
|
|
|
Post by LesMourne on Jan 13, 2020 10:21:18 GMT
Best Price Cialis 20mg Potenzmittel Kamagra Nebenwirkung <a href=http://cialibuy.com>Cialis</a> Viagra Hausarzt Oder Urologe
|
|
