#div by also-web

[beomev]

𝗽𝗵𝗼𝘁𝗼𝘀 𝘆𝗼𝘂'𝘃𝗲 𝘁𝗮𝗸𝗲𝗻 𝗼𝗳 𝘆𝗼𝘂𝗿 𝗯𝗼𝘆𝗳𝗿𝗶𝗲𝗻𝗱, kim woonhak

운학────𝗍𝗁𝖾 𝖽𝖺𝗒 𝗍𝗁𝖺𝗍 𝗂 𝗆𝖾𝗍 𝘆𝗼𝘂, 𝗂 𝗌𝗍𝖺𝗋𝗍𝖾𝖽 𝗱𝗿𝗲𝗮𝗺𝗶𝗻𝗴

𝘄𝗼𝗼𝗻𝗵𝗮𝗸 x reader ⠀⠀⠀⠀─── ⠀⠀⠀⠀𝗴𝗲𝗻𝗿𝗲 fluff, crack ⠀⠀⠀⠀𝗻𝗼𝘁𝗲𝘀 i fear everyone needs a woonhak in their lives ⠀⠀⠀⠀𓂋 ⠀⠀⠀⠀❛ 𝗮𝗿𝗰𝗵𝗶𝘃𝗲

ㅤ⠀ㅤ ིྀㅤtaglist: @daydreamnet @blossomnet @a-dream-bookmark @k-films

ㅤ⠀ㅤㅤ⠀ㅤㅤ⠀ㅤ﹔℘๋࣭ ⭑ send an ask or just comment to get added

[valkierrie]

𝐌𝐲 𝐌𝐚𝐧

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Warning(s): None.

Plot: It's Damon's birthday and Y/N makes him feel special.

Word count: 1.1K

A/N: I'm a little late to the party, but it's a special happy birthday post for Damon.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

As soon as the first sliver of light slipped through the worn-out blue shutters, I was already up.

I did my best to shuffle out of Damon’s grasp. Lifting his hand, which had been draped over my waist in a possessive manner. It was as if holding onto me kept him tied to reality even as he was off in dreamland—like he couldn’t be apart from me.

It was sweet.

Really.

He was the type of lover who’d never keep anything from me, always expressed what was going on in that beautiful mind of his, but it was also the little things that had me weak at the knees. The way his hands would instinctively grasp mine whenever we were out and about; or when his jacket found itself draped over my shoulders if I so much as shivered near him. Small things—and yet, it only made my love for him that much stronger.

I smiled down at his sleeping stature, pressing a soft kiss on his forehead.

He deserved this.

I crept into the kitchen, making sure the wooden floors didn’t creak.

I opened the cabinets, bringing out all the ingredients and materials I needed. Placing a pan on the stove, I turned it on. I whisked the ingredients together until the batter was smooth against the whisk, then poured it into the heated pan. I watched as it sizzled and formed small bubbles. One by one, I flipped them until the buttermilk batter was golden.

The process was repeated until I had four to five hot pancakes on a plate.

Placing the plate of pancakes on a silver tray, I grabbed a glass cup, pouring an orange juice three-fourths of the cup.

I picked up the tray, ready to go back into the bedroom and present Damon with breakfast in bed. In my excitement, I forgot one of the most important parts. Syrup.

I grabbed a bottle of maple syrup from the pantry,  pouring webs of syrups all over the pancakes.

Satisfied, I picked up the tray and left for the bedroom.

Damon was still very much sprawled out on the mattress, snoring without a care in the world. I placed the tray on the nightstand, beside Damon’s side of the bed. I gently shook him awake. 

Damon stirred, omitting a low and tired groan. 

“Damon, c’mon, wake up.”

Damon cracked open an eye and groaned, staring right at me. “What’s the fuss for? S’too early.” he muttered.

“Get up.”

“No. Gimme five minutes—no, an hour.” He turned his head away. 

I shoved him, pinching his arm. 

“Oi!” He gasped, “Alright. Alright, I’m getting up.” He sat up, his bare back pressing against the headboard as he rubbed his face. 

His gaze fell onto the food on the nightstand. “Breakfast in bed? What’s the occasion? You poisoning me?”

I gave him a look.

 Damon recognised the look. It was a very unimpressed look, like disappointment. “Oh, uhm—is today an anniversary?”

“No, Damon.” I rolled my eyes. “It’s your birthday, you div.”

“Ah,” he chuckled. “Sorry, it must’ve slipped my mind.”

I shook my head. Of course that was the case. When it came to me, there was never any forgetting from him—except our anniversary, apparently. But, remembering anything about himself was always a challenge.

I picked up the tray, placing it on his lap. “Eat up.” I kissed his cheek.

“Thanks, darling.” Damon smiled. 

He ate up quickly, but still held space for the flavor, savoring it, whilse humming some bits of Coffee and TV. When he finished eating, he was surprised to find that there were more surprises that laid ahead. 

“Breakfast was the bare minimum,” I told him. “I’ve got more in store for you.”

We found ourselves at an ice ring. Something that seemed like a good idea a few weeks ago, but clearly I hadn’t thought things through. We made it work—which meant clinging on to each other and the glass walls as skaters zoomed past us. 

“Look at us,” Damon said, his arm interlocked with mine as he felt around the glass wall. “Reckon we’re getting better, eh?”

“Right.” I deadpanned. 

We were about to make a full clockwise rotation, when suddenly a small girl zoomed past us, causing me to fall and pulling Damon down with me. 

Damon burst into laughter, properly cackling. It was infectious, and for no particular reason I was laughing too.

The small girl looked back, shooting us a judgemental look. 

Perhaps adults with the mental age of toddlers just didn’t appeal to her.

After embarrassing ourselves some more, Damon and I stopped at a small bakery. A French one. 

“Open wide.” I instructed, pointing a fork-stabbed pain-au-choc at Damon.

“This your master plan to fatten me up?”

“Depends,” I smirked. “Is it working?” 

Damon rolled his eyes, leaning forward to eat the pastry, but before his lips could touch the fork, I swerved it away. Damon raised a brow.

“Is that how we’re gonna play?” He asked.

“No.” I giggled. “I’ll stop.”

I allowed him to take the food from the fork, wiping the remnants of chocolate that had stained the corner of his upper lip.

When the evening rolled around, we were back at our flat and I had one more thing in store for today. 

Damon settled on the sofa, knackered. “One more thing? You’re spoilin’ me.”

I shrugged, leaning back to pull open a drawer. I grabbed a small black box I’d tucked in there weeks in advance. With a smile, I handed it to Damon. “Go ahead, open it.”

Damon did so, finding a bracelet. It was made of a variety of colours and materials, beads all around—-almost like the necklace he had around his neck.

“I wanted to get you one that matched your necklace. And—” I picked the bracelet, holding it up, showing the two dangling letters.

“Our initials?”

I nodded. “You like it?”

Damon grinned as he slipped the bracelet onto his wrist. “I love it.”

“You’re not just saying that, are you?”

“‘Course not,” His smile grew wider, looking at me like he couldn’t quite believe that I was there. “Y’know, you’re pretty amazing.” muttering, almost to himself, but I caught it.

I was taken aback by the comment, I hadn’t done anything extraordinary, and yet—with his head propped up by his hand and a lazy smile on his face, he just casually said that; it was as if there was no thought about it, no question.

He pulled me close, locking his lips onto mine. It moved slowly with fervent and passion. He poured his love into it. With the way he was kissing me, he didn’t need to tell me that he loved me. He was showing it to me.

When we pulled back, that look hadn’t disappeared from his face. We didn’t say anything, simply wrapping his arms around his shoulders and nuzzling close.

[valeriehalla]

mwah mwah mwah mwah mwah I just found your VN and it's so cute and arresting and so full of nonbinary longing I'm absolutely in love already and it's kinda inspiring me to do the scary job of opening up a word doc and try writing some of my own stuff for the first time ever

also wrt aster i love love love love love the idea of being freed from agab. just... can't remember. who cares. no longer having to measure up to a gender metric or constantly minimizing your male shoulders or female hips and worrying about your ratios or presentation - and just relax and enjoy it instead of treating it like a constant chore of maintaining a dozen spinning plates to avoid being "found out". freed from presentation pressure. mwah.

also also as a fellow web developer I'd love to hear more about your stack for ssg - gatsby? svelte? vite? 93 nested imported html docs? one really really big div? I ask because while I don't know if I'll ever have the chops for music production, reading and discovering that inline music player absolutely tickled me, both narratively and as a developer, what a delight, so so so good

My “stack” ... hmmm. “Stack” .................

So, for the main website I just used ��Lektor”, which I picked out of a hat on the basis that it was python-based and could do the one thing I cared about (HTML templating). But the CURSE/KISS/CUTE reader is coded from scratch. It is a single-page app, and it loads and displays story content by grabbing the HTML from a JSON file I call the “story file”. The JSON in turn is created by a parser that I wrote in python that parses a specially-formatted markdown file which I also confusingly call the “story file”. The script format for this latter file is slightly custom but is mostly just “normal markdown but I repurposed code ticks as a macro format”:

The music player is pretty rudimentary and just offloads all the complicated business to howler.js.

It’s a funny patchworked leaning tower of python but it gets it done and gets it done entirely client-side and that means I don’t have to dip even one of my toes into the haunted pool of server-side web development =w=

[jimzittos]

⟡˖͢ ℛise of 방탄! — ํthe event◍*⃝̥

About:

i still can't believe i reached a hundred followers, thank you for supporting me i rlly appreciate you all sm!! <33 i always wanted to host an event and obviously my first event was gonna be bts related hehe. i hope u enjoy!! (pls don't flop this lol)

Instructions:

Make an mb with the theme of a bts album/era 

You can choose the album/era yourself

OR 

If your an indecisive person like me, just dm me a number from 1-10, I'll assign u an album/era ( u don't necessarily have to follow it tho)

U may use any idol/character/celeb in your mb! It doesn't necessarily have to be a bts member. ( its also fine if u don't use an idol/celeb/character )

Rules:

Your mb must be at least 90% made by you, you may use locs or divs made by others but make sure to give them credits

you may take inspo from other mbs but DO NOT plagiarise

only one entry per person (u may change or edit it before the deadline)

Joining:

Comment joining + ur fave bts album/era

Reblog this post and tag 3 or more friends

Tag me in ur mb ( or the comments) so that I won't miss ur entry!

Use the tag "⟡˖͢ ℛise of 방탄! — ํthe event ◍*⃝̥🐋" while posting ur entry (pls copy paste) or else it won't be valid 

Prizes:

1st place : 100 reblogs, 3 custom moodboards, follow back

2nd place : 50 reblogs, 2 custom moodboards, follow back

3rd place: 25 reblogs, 1 custom moodboard, follow back

Notes:

The event ends on August 3 (lmk if u need an extension)

Reblogs will be made on @zitosrbs and pls don't rush me while giving out the prizes.

Take your time and have fun while making ur moodboards!! <33

Moots + fav blogs: 

( sry if i didn't tag you / sry if u didn't want to be tagged)

@kthice . @i-mmaculatus . @jjk7h . @kwwjmn . @cirrose . @ehsuga . @liilithmin . @taevlogg . @kooryiio . @also-web . @c-heriis . @swiftwice . @gigittamic . @aeraras . @aqualogia . @haeheyy . @haenxn . @hanitos . @suzy143 . @daddldee . @jnssite . @swgarish . @cg1rl . @aericita

[izicodes]

Convert HTML to Image: A Step-by-Step Guide ✨

Do you want to turn some HTML code you've made that's on your website and have a way to convert it into an image for you to save?

Well, look no further! I too wanted to do the same thing but funny enough, there weren't any straightforward tutorials out there that could show you how! After hours of searching, I finally discovered the solution~!

This is an old tutorial I made 🐼

💛 Set your environment

Before we dive into the conversion process, I'll assume you already have your HTML code ready. What you want to learn is how to turn it into an image file. You should have a good grasp of HTML and JavaScript. For this tutorial, we'll use the following HTML code example:

We won't include the CSS code, as it doesn't affect this tutorial. The JavaScript file (script.js) at the bottom of the body element is where we'll add the functionality for the conversion.

Your page should resemble the following:

As you can see, the "Click me" button will handle the conversion. We aim to convert everything within the div.info-div into an image.

💛 Using the html2canvas JavaScript Library

The html2canvas library allows you to take screenshots of webpages and target specific elements on a screen. Here are the steps to include the library in your project:

The steps to put the library in your project:

Visit the html2canvas website for more information.

Copy the CDN link from here

and include it in a script tag in your project's head tag in the HTML file:

That's it for including the library on the HTML side. Now, let's move on to the JavaScript code.

💛 JavaScript Functionality

Here's the JavaScript code to handle the conversion:

In this code, I want to turn the whole div.info-div into an image, I put it into a variable in const div = document.querySelector(".info-div");.

I also put the button into a variable in const button = document.querySelector("button");

I added a click event listener to the button so when the user clicks the button, it will follow the code inside of the event listener!

You can find similar code like this in the documentation of the html2canvas library:

What is happening here is:

We add the div (or what the element we want to take an image of) into the html2canvas([element]).then((canvas)

Added the image file type url to a variable = const imageDataURL = canvas.toDataURL("image/png"); - You can replace the png to other image file types such as jpg, jpeg etc

Created an anchor/link tag, added the href attribute to imageDataURL

The download attribute is where we will give the default name to the image file, I added "dog.png"

Perform the click() function to the anchor tag so it starts to download the image we created

And that's it!

💛 The End

And that's it! You've successfully learned how to turn your HTML into an image. It's a great way to save and share your web content in a unique format.

If you have any questions or need further clarification, please comfortable to ask. Enjoy converting your HTML into images! 💖🐼

[deepinthegroves]

🕷 spiderverse dr intro 🕸 ✮⋆˙

the different threads of the spiderweb...

..the spider(man)

..interconnected silk threads

...my family

...my friends

..the hub of the web

note: did this take me days to post? yes. did i finish a day early and wanted to post this on valentine's anyways? yes. sorry everyone, between no motivation and perfectionism (i'm still not satisfied), it took me days to finish this all.

i am also convinced that i didn't cover my entire dr here, but it's a whole other reality – it cannot be summed up completely. do send asks if you're curious about anything else <3

div. credits: @/strangergraphics

[kitkatt0430]

Instead of doing a Six Sentence Sunday today, I think I'll do a short tutorial on copying over fanfic from FFnet to Ao3.

So you've got some old fics on FFnet and you'd like to back them up to Ao3, given the instability of FFnet. And for whatever reason you don't have the original files for the fics, or maybe you have edits to the FFnet versions that you don't want to lose that the OG files don't have. Whatever the reason, you're looking to directly copy over your fic from FFnet to Ao3. And you're looking for a relatively easy way to do so, but Ao3's import functionality doesn't work with FFnet web pages.

Never fear! It's actually a fairly easy process to get your fic copied over from FFnet.

First, head over to FFnet and open up the fic you want to port over to Ao3. You don't need to log in if you don't want to, just so long as the fic in question is yours and you can access the page, then you're good.

In a separate tab, open Ao3 and login, then choose the option for posting a new work.

Now back on the FFnet tab, you should be able to directly copy over the title, summary, fandom, and what little tagging was available on that site onto the relevant Ao3 fields in the tab you have for a new fic. You'll also want to take note of the published date on FFnet and back date the new work in the Ao3 tab.

FFnet may not have a lot of useful tag data, but it's pretty easy to replicate and build off that in Ao3.

Now for the hard part. Which is still pretty easy. Getting the fic body, plus any notes in the fic itself, copied over to FFnet.

While getting around FFnet's lockdown on the text of the fics they host is fairly simple - I'm pretty sure it's entirely css based - you don't really need to do that in order to get the body of your fic copied. And, honestly, even if you do have a work around in place to allow copying of the fic's text... you will probably find the following method a lot easier still.

In the body of the fic, right click the first line of the fic, which should bring up a menu with a bunch of options. On Firefox or Chrome you want the inspect option.

This'll bring up the dev tools with the html inspection tab open and, if you give it a few seconds to load, the specific line you right clicked to inspect should become the visibly selected section of the html.

The selected section of the html should be a paragraph (or <p>) element. You're going to want to right click the div (<div>) element that encapsulates that paragraph and the rest of the paragraphs in the fic body. This'll bring up another browser menu with the option to copy, which will bring up a flyout menu when you select it. From that flyout menu, you want the select the option for Inner HTML.

You have officially copied the html for the fic body. And you can dump that entirely in html format straight into Ao3's html work text editor. Then switch it to rich text for easier editing if you want to fix any spelling, grammar, formatting, or aesthetic issues. I typically try to fix at least the line breaks since it took a long while before FFnet adopted real line breaks and so there are a lot of fics where I have various combinations of dashes, em-dashes, equals signs, and other characters as line breaks. I figure, if I'm bringing the fic to Ao3 then I can try to make it more screen reader friendly in the process.

You can also move fic notes around in order to move pre/post fic notes out of the fic body or basically whatever you want to the fic. Maybe re-read it to determine any additional tagging you want to add now that your fic has access to Ao3's much more robust tagging system.

But that's it. You can hit post and have your fic with all it's original notes, and a back dated post date to reflect when it was actually written, all available on Ao3 now.

It's a pretty quick process, all told, and the only real bottleneck you might encounter is any time spent in re-editing the fic between migrating and posting. Even chaptered fics are fairly easy to migrate with this process, since the bulk of the work in publishing a new chapter is just copying the inner html and then moving any notes to the appropriate location before hitting post.

Anyway, for my fellow fic writers looking to move your old FFnet fics to a more stable archive, I hope this process helps a lot.

[preheville]

hii i was wondering if u had any web resources for building your neocities site? did u use templates? its so pretty... its such big inspo

tysm!! i didn't use templates! just a lot of hard work ^_^ i'm actually putting together a tutorial-ish video rn for how to make your own html/css site so check in on that in a month..

it's been long enough i don't actually remember how i started learning how to code. i think i used w3schools and cobbled this homepage together from that. you pretty much just need to know how to use divs and things fall into place after that. there's also a lot of tutorials already up on youtube :-) the w3schools link is cool because it lists everything you need to learn in ascending order so it's a great place to start! also i do recommend looking at other peoples' codes — obviously not to steal, but because i find that snooping around completed code as a beginner can show you what you'd like to learn and stuff. feel free to reach out if u have any specific questions... :-) my site looks fancy but it's really nothing complicated ^_^ the hardest part of html/css isn't the coding itself, it's the graphic design imo!

[golem-boy]

DevLog 02: I'd Rather Be Writing CSS

Hello again! This month's DevLog post is going to be a lot of fun. I'm going to talk a little about my endeavors with Neocities, writing code, and working with old-school web interaction.

I also wanted to make a note that I'm totally cool with folks reblogging and liking these posts, and you're welcome to snag the rss feed for this tag if you'd like to keep up with it but don't particularly feel like wading through everything else I drop here.

Without further ado--

Lately I've been working on a side project to help a friend out; their Neocities, is--like mine--going to be a place to host a ton of centralized information so they can just hand site links out rather than having to link a whole array of webpages to people in order to share certain stuff. (I totally recommend people do this, btw. Super useful, AND you get to learn html/css, which is great on a site like Tumblr, where you can employ that knowledge and skillset elsewhere!)

Thing is, when I started this, I'd been... a touch rusty on things like... you know, the basics, building from a blank space up into a proper site. One of my problems was accidentally adding a period before the 'body' stylization code in the css document, which, for those wondering, makes the css read it as a 'div' or 'span' tag, rather than a core component of the site. Rookie mistake, but I did manage to figure it out... by making links turn orange on hover!

How, you may ask? It confirmed that the style from the css was successfully applying to the barebones html I'd already written, and gave me a better idea of what exactly was going wrong. Never discount the odd ways of troubleshooting, tbh.

I've also made a huge leap of progress on my own site, specifically the gallery pages, though they are DEFINITELY still works in progress, namely in layout. I've had to expand my understanding a litle and read up on stuff like flex boxes, which I might expand on and cover in my next DevLog as I make more progress.

I also started sketching some ideas with a friend out for a sort of idle colony sim--I don't want to spoil too much, but our shared notes are preeetty exciting so far!

On the topic of games, Garry's Mod is kind of a wreck on linux. I managed to get it going fine with Proton 9.x, which is hilarious--it straight up does not run anymore on the native build. No idea what got broken, but it sure is Something to behold, hah. I have been wading through my subscribed items, trying to update some of the tools and utilities. One of these days I'll get my shit figured out and upload a UT99 playstation-port Xan... I already have a lot of plans for such a thing, of course.

I have been honing my skills with blender, especially rigging, which has been interesting. I definitely GET it, it's just a matter of synthesizing and memorizing parts of the control scheme and especially how to fiddle with things like shapekeys. The perk of ragdoll stuff is you don't need a ton of picky shit... phew! Getting ahead of myself a bit there.

This month has been super busy, and I've been a bit scatterbrained, but here's to another month of progress, eh?

first | archive | next

[pronoun-checks]

Hey there! Wondering if we could get some feminine/neutral V names, with ties to spiders, gods/godesses/mythology of any culture, or the colour blue if possible? Also with "Bad Bitch Vibes" as it's telling me- (These are for a headmate -v-) The names aren't required to start with V btw!! Just a purrefurence!

So there aren't repeats, they already go by Vinny & Vee (And their source name, which we aren't fully comfortable disclosing as it's controversial to some.)

They'd also like xenopronouns with similar themes of mythology, spiders, blue, and the number 8? As well as neopronouns such as xe/xem or ae/aers, stuff like that-

Thank you!

~ 🧭&🕷️, @starry-fieldcollective

Sure thing!

Names:

Venus

Violet

Viola

Vesta

Victoria

Vallonia

Viridian/Viridia

Valkyrie

Valerie

Vachya

Vivienne/Vivian

Viviana

Vesper

Valentina/Val

Vixen/Vix

Vör

Indigo

Iris

Azure/Azura

Pronouns

myth/myths

god/gods

goddess/goddesses

blue/blues

indigo/indigos

ind/indigo/indigos/indigos/indigoself

cyan/cyans

teal/teals

spider/spiders

spi/spider/spiders/spiders/spiderself

8/8s

eight/eights

magic/magics

divine/divines

div/divs

styx/styxes

web/webs

silk/silks

venom/venoms

e/em/eir/eirs/emself

ey/em/eir/eirs/emself

fae/faer/faer/faers/faerself

ze/zem/zir/zirs/zemself

ne/nym/nis/nis/nymself

nymph/nymphs

elf/elfs

ve/vir/vir/virs/virself

xe/xir/xir/xirs/xirself

ae/aem/aer/aers/aemself

dae/daem/daer/daers/daemself

vae/vaer/vaer/vaers/vaerself

[doffy2]

do you have any rules/guidelines you go by when designing and creating a site? i love your web design, the way you combine style with accessibility is very inspiring; i really struggle with that balance

First off: thanks very much for your compliments about my site building. I put a lot of effort into what I create, so it's always nice to hear others enjoy my style or formatting of pages, thanks again.

TL:DR; Start simple and expand when the simple stage is done, don't delete that old half-finished page keep it up somewhere (gives you progressive reference AND a paper trail for growing accessibility wise), and don't be afraid to take inspiration from other sites.

Rambled response under the cut.

I took some time to ruminate on a response here lol. Bounced around some advice or input but ultimately I think starting simple is your best friend in coding.

Starting simply can be useful not even strictly from a site-building perspective, anything from inspiration, to pictures you'll use, to a color palette really. If you start with a bunch of concepts you want to utilize or bring to life your code can wind up very messy very fast, and sometimes you'll start disliking what you're making even if you're nowhere near the end goal you originally had in mind.

I see it a lot from the Neocities sites I follow actually. People start on HUGE webpage ideas, total site overhauls, and burn themselves out when the piece isn't coming to life exactly how they panned it out. I'd recommend even scribbling pencil-sketches for base site layouts, leave the flashy graphics people normally plan around out of it until a later stage in coding, and see how that feels. So many of my pages started as "ghdksdfg.png" from ms paint, seriously. Visualizing your layouts is a lifesaver.

The second point, which I emphasize a lot to people looking to really start up a Neocities or even just get into misc. coding is: keep your old code. Do it. I don't care how messy and shitty and unstable it is- same with keeping old art, you'll notice your progression AND it will be ten thousand times easier to reflect on things like accessibility if you have an old reference point. I've looked back on old code and gone "shit, I forgot (feature)" which more times than not is a QOL (quality of life) implement for the whole page. You're giving yourself a paper trail for improvement AND mistake catching. Big bonus.

Last: everybody has done everything before. Everybody. No matter what your site looks like someone can done that combination of div placements or used that graphic or ETC ETC ETC. Comparison kills. Grab a layout idea you like from some old 2000s cartoon site. See someone use a custom border? Take a look at it and figure out how to do it yourself. Want someone's code for a music player or calendar or gallery? Ask them for it or replicate it. Using inspiration isn't something you should be wary of and sometimes it leads to overthinking in web design.

I could ramble a lot more about design especially in the current Neocities sphere, but I'll try to stick to these 3 points which I think could be helpful.

If you want me to expand on any points or specify anything else let me know. If you also had any further questions I'll try my best to answer them in a more coherent way LOL. I've been on a schoolwork grind, so I hope I'm cohesive enough here.

[code-tryperse]

Just started web development for college and now, I have to ask the question that others before me have also asked...

How the fuck do you center a div?

[sunfoxfic]

i have a question, i'm not sure if anyone has asked this yet but: can you use more than one code, as in two completely different & separate codes, in a single work skin? i found a cool web search css code along with a social media code post & i'd like to use both (maybe more) in a single or multiple chapter(s) of my fic. if it's not possible, would it be best to make those into separate chapters of a series?

Short answer: Yes, but be careful.

Long answer: CSS functions by taking HTML elements (for example, a div container or a paragraph) that have been assigned classes and modifying those elements. The classes are named arbitrarily - you can quite literally name them anything, and so long as it's consistent between the HTML and CSS, it will be read correctly.

So, for example, I might have something that looks like this:

<p class="red">Hello!</p>

And the CSS might look like this:

.red { color: red; }

And that will mean that the final product, the text, will be turned red in color. It could also just as easily look like this:

<p class="dgsakhj">Hello!</p>

and

.dgsakhj { color: red; }

This will look exactly the same.

So. What does this matter?

Well, let's take the CBAU skin I use. I've patched it together using several skins, including an iMessage skin, a Discord skin, and a blog skin.

Say, for example, the iMessage skin and Discord skin both use a class name that's called "message."

That's a problem.

If I have two lines of code in the CSS that look like this:

.message { color: white; background: black; font-family: "fake font"; } ... .message { color: black; background: white; font-family: "fake font 2"; font-weight: bold; }

These are going to conflict. I believe the CSS will default to the first one in this case, so it choose the color/background color/font on the first one, but it will be bold as the second one specifies, so it won't work for either.

Obviously it won't actually look like this; it will be more complicated and have more strange interactions. But the possibility exists.

As always, I do love doing CSS/HTML stuff, so if you have questions just ask. I'm not a master of the craft by any means but I can diagnose issues. If you want to do it yourself, I recommend just putting the CSS into a single work skin and putting the sample HTML into a work and seeing if anything breaks. If it doesn't, you're all good! If it does, you can either try to diagnose the problem itself according to how I explained it here (though I know it's confusing and my explanation probably isn't the best), or you can ask me. Feel free to DM!

[xero-fox]

hi! sorry for the random ask, but I'm sending this to you because of your comment with that PWA guide for Android users from a couple months ago? I followed the instructions and it worked like a charm this entire time, except for just now! I opened up tumblr thru my PWA and lo and behold, tumblr live is back at the top of my dash and I don't know how or why! do you know how to get rid of this new instance?

Sorry for the late response!! Glad to know that guide helped some people (it's here for anyone who hasn't seen it).

If you just want to know the fix then I'll add the line down at the bottom so you can copy/paste, but seeing as you did ask why it came back I'm going to hijack your ask for an educational opportunity.

Webpages are structured using HTML (HyperText Markup Language). Examples of HTML elements are <h1>, used for the main heading of a page, <p>, used for paragraphs, and <div>, used for separating content into sections. A very basic webpage might be written like:

<html> <body> <h1>My Webpage</h1> <p>This is my webpage!</p> <p>This is my very first webpage.</p> <p>I hope you like it :)</p> </body> </html>

A webpage for sure, but a pretty ugly one, and it definitely doesn't have all sorts of cool funtionality like the tumblr site does. To make a webpage do cool stuff, we need to use JavaScript, and to make it look nice, we need to style it using CSS (Cascading Style Sheets).

Let's have a go at some CSS! For example, what if I wanted to make all my paragraphs (the <p> elements) red? Let's see:

p { color: red; }

Awesome! But what if I just wanted, say, my first paragraph to be red? How would I do that? Luckily, in my HTML, I could give that first paragraph an id, and then I could use that id in the CSS, like so:

<p id="subtitle">This is my webpage!</p>

#subtitle { color: red; }

(Using a # symbol in the CSS tells it to look for an element with the id of subtitle).

Ok, but now let's say that I wanted to color my other paragraphs green. I could do something like this:

<p id="para1">This is my very first webpage.</p> <p id="para2">I hope you like it :)</p>

#para1, #para2 { color: green; }

And this would work! But it's pretty bulky to write, and that's only with 2 paragraphs! Imagine if I had 5, or 100!

Luckily, another feature we can use is classes. Classes work a bit like ids, but you can apply them to more than one element, so you can style a bunch of elements at once! Elements can also have more than one class, if they need to. Let's see:

<p class="green">This is my very first webpage.</p> <p class="green">I hope you like it :)</p>

.green { color: green; }

(Using a . symbol in the CSS tells it to look for elements with the class of green).

Ok, this is great and all, but what's it got to do with blocking the Tumblr live stuff? I'm now going to show you the line you need to add to your content blocker to remove the Tumblr Live element:

tumblr.com##.KDMTE.wQ2Ma

It looks a little different, but this is actually using CSS syntax! The first part tells our content blocker which site to apply the rule to, and the ## tells it that we're about to give a styling rule, but look at the bit after:

.KDMTE.wQ2Ma

We know what the .s mean - it's just specifying classes! This line is telling our content blocker to block any elements that have the classes "KDMTE" and "wQ2Ma", which are the classes given to the <div> element that contains all the Tumblr Live stuff.

Cool! But why did these classes change from before? And who calls a class something like "wQ2Ma" anyway????

The answer is that a human didn't name a class "wQ2Ma", a computer did. With large sites like Tumblr, it's very common to design the site using something called a framework. I'm not a professional web developer and have never really used frameworks personally, but the way I understand them is that it provides a kind of interface between the programmer and the low-level HTML code, which can speed up development a lot. However, it does mean that class names get kind of randomly generated, so you end up with stuff like "wQ2Ma". This is also why the class names have changed from before - when the latest update to the user interface was deployed, all of these class names would have been generated again, meaning the old blocking rules wouldn't work anymore.

So there you go! That's why Tumblr Live came back! Here's the line you need to add to your content blocker if you didn't want to read my whole spiel (I don't blame you lol):

tumblr.com##.KDMTE.wQ2Ma

[michainabox]

I got done drawing my Spidersona Spider-Glitch!

I am not a good drawer- please be nice-

Anyways!!

Spider-Glitch, known as Mason Oakridge, is a 22 year old college student studying engineering to follow into their fathers footsteps.

They were bitten by a radioactive spider one faithful night and suddenly developed spider like powers.

Ability to stick to walls

Spider senses

Heighten sense of touch, and hearing

Ability to sense electromagnetic pulses

Ability to absorb static/low electricity (Can’t use it though)

Slightly accelerated healing

The neon red and blue webs, spider symbol, eyes, and soles of their flats glow in the dark. The suit is suppose to protect Mason from high voltage, and from fatal damage.

I hope you enjoy!

Also, the brushes I used from procreate for the pose, and line art come from @di_syukov on instagram. And below is their Gumroad.

[ren-shonen]

Several people asked how to use this userscript on mobile, and also how to modify it for darkmode, so I will do my best to explain!

Installing Userscripts on Mobile

FIRST: Make sure you are using a mobile web browser which supports installing extensions or supports userscripts. I use Firefox for Android, so that's what these directions will be for, but there are a few other options that might work if you are on iOS or elsewhere.

In Firefox for Android, open the options menu > Add-ons, and select the Add-ons Manager. In the list of recommended Add-ons, find Tampermonkey and install/enable it.

Go back to the Add-ons menu and tap Tampermonkey. You can use Tampermonkey's search function to find the userscript, or simply go to the userscript's GreasyFork link and install it from there.

Repeat with any other userscripts you'd like to install! Searching "AO3" on GreasyFork can turn up some fun options, and AO3 themselves link to a few in this guide.

✅ The userscript is now installed! You can go on and use the script on AO3 now as OP described. Everything after this is just optional tweaks, mostly cosmetic.

Further tweaks...

Note: All of the tweaks below also work for desktop.

Optional: Modify AO3 Floating Comment Box for Darkmode

By default, the background of the input text box is white and doesn't change with your browser/phone settings. Fortunately, a quick edit fixes this. (Note: you can also do this same kind of edit if you use this userscript in a computer browser. The code change is the same.)

Open the Tampermonkey add-on and navigate to settings.

Select the Installed Userscripts tag, then tap the "Edit" button on AO3 Floating Comment Box (the little pencil and paper)

This will open the code editor. It might look like a bunch of nonsense unless you're already familiar with JavaScript/userscripts, but don't be intimidated: we're just finding one word and changing it!

At the top of the editor, click Find. Search for white

You will see the following chunk of code:

".float-box": { "min-height": "70%", "max-width": "98%", "background-color": "white" },

replace white with 333 (i.e., changing the color of the background of the text box from white to a dark grey). Make sure you don't accidentally alter any of the punctuation!

-> if you want it to be a different color than the one I picked, you can use an HTML Color Picker or names list to get the hexadecimal code or official name for the color you want. (Don't include the #)

Close the Find dialogue, then at the top, select File > Save. All done!

In your browser, open a works page on AO3 and open the floating comment box to check that the result was what you wanted.

Other Optional Tweaks

---- FOR AUTHORS: Ensure that the script doesn't try to modify the New Works page:

Toward the top of the script, in the header/settings section, immediately below the //include line, add:

// @exclude *://archiveofourown.org/works/new

----- Add the AO3 logo as an icon for the script:

Toward the top of the script, in the header/settings section, immediately above the // @namespace line, add:

// @icon https://archiveofourown.org/favicon.ico

---- Make the text box take up less vertical room on your screen:

under const allStyles, in the float-div section, change "height = 30%" to "height = 20%"

(you can also play around with these numbers to tweak it to your preferences)

Mentions for the folks who @-ed me: @inahc3 @harleyqueerner @sunset-diamond @fuctacles

Hope this helps!

(edited for clarity 2023-11-03)

In the spirit of encouraging people to comment on fanfics while also making it easier to do so, I feel obliged to share a browser extension for ao3 that has quite literally revolutionized the comment game for me.

I present to you: the floating ao3 comment box!

From what I've seen, a big problem for many people is that once you reach the comments at the bottom of a fic, your memory of it miraculously disappears. Anything you wanted to say is stuck ten paragraphs ago, and you barely remember what you thought while reading. This fixes that!

I'll give a little explanation on the features and how it works, but if you want to skip all that, here's the link.

The extension is visible as a small blue box in the upper left corner.

(Side note: The green colouring is not from the extension, that's me.)

If you click on it, you open a comment box window at the bottom of your screen but not at the bottom of the fic. I opened my own fic for demonstrative purposes.

The website also gives explanations on how exactly it functions, but I'll summarize regardless.

insert selection -> if you highlight a sentence in the fic it will be added in italics to the comment box

add to comment box -> once you're done writing your comment, you click this button and the entire thing will automatically copied to the ao3 comment box

delete -> self explanatory

on mulitchapter fics, you will be given the option to either add the comment to just the current chapter or the entire fic

The best part? You can simply close the window the same way you opened it and your progress will automatically be saved. So you can open it, comment on a paragraph, and then close it and keep reading without having the box in your face.

Comments are what keep writers going, and as both a writer and a reader, I think it's such an easy way of showing support and enthusiasm.