Actions

Work Header

Rating:
Archive Warning:
Category:
Fandom:
Additional Tags:
Language:
English
Series:
Part 1 of Repository: A Collection of Work Skins and Guides
Collections:
Fanfiction Reference Works, A Guide to Coding and Fanworks, HTML Ao3 Help, HTML & CSS stuffs, Ao3 Tutorials, Ao3 Skins, AO3 Social Media AU Work Skins
Stats:
Published:
2020-01-23
Updated:
2020-01-24
Words:
6,494
Chapters:
12/?
Comments:
96
Kudos:
735
Bookmarks:
885
Hits:
35,912

Repository: Work Skins

Summary:

Primarily just where I share work skin code and discuss ways to improve the Ao3 experience, including:
- Twitter and Instagram like posts
- Non iOS messaging systems
- Avatar and image formatting for script formats.
- Search engine interfaces
- Documentation on AO3 Site Skins

Notes:

This isn't a new fic. This is just my test bed where I attempt to experiment with work skins.

(See the end of the work for other works inspired by this one.)

Chapter 1: An Introduction

Summary:

[This post is under construction]

Notes:

A bit late to post since the publishing of this guide, but I might as well do it for documentation's sake.

Chapter Text

These work skins are made firstly, to help make your fics as pretty as you desire them to be. Who doesn't want some cool Tweets in your fics, or a convincing Google search bar?

Why all the emphasis on highlighted text?

The major design principle of the code I share here is to make user-friendly, native HTML/CSS code that can be used in AO3. It is incredibly easy to simply paste a screenshot of a tweet or instagram post and call it a day, but I don't believe this would be helpful to the preservation of fics. As of now, AO3 doesn't host images on its own and requires users to host such content on their own. If the content host shuts down before AO3 does, the image will no longer be accessed and is at the mercy of the Wayback Machine. Additionally, some readers might not be able to read off of an image and will have greater difficulty understanding the story if they miss out on possibly valuable text, and images in a lossy format (like .jpeg) will degrade over the time.

For images and illustrations, this may not be significant for a medium that's heavy on text, but if you used those images to depict social media posts or anything text heavy, a broken link is a major problem. These work skins may require some work to configure, but using text and some fancy formatting could be better in the long run. Even if you lose the user images and the photos, you can still preserve the text and allow some more accessibility while still maintaining your immersive, stylish experience.

Some ground rules, policies, yada yada

I don't think much needs to be said here, but you are free to make modifications to the code shared here. For troubleshooting, please be as detailed as possible about what the problem is when you post your comments. The ideal situation is to actually share the code, so like, directly pasting code for us to see or a codepen link can be most useful.