Posts by astraea

moon naeun

known by her stage name 'naeun'

21 years old

main dancer and vocalist of girl group '4SEΔSONS'

despite her bright smiles and charisma on the stage, naeun is known as the more introverted, quieter member of the group. she lets the other members do most of the talking but contributes occasionally. she often takes care of the group as one of the more mature members, and is jokingly referred to as the mum of the group. naeun is extremely hardworking and resilient, continually praticing and filling up her individual schedule and rarely letting herself take a break. she takes things very seriously and is often told by the members to lighten up a bit.

the life of an idol didn't always appeal to naeun. however as her friends all were obsessed with k-pop groups she was roped in as well. when she was thirteen she accompanied one of her friends to an audition, where she ended up being scouted as well. she began to love music and dancing, and continued with trainee life until plans for a new girl group arose when she was seventeen. however right before they were about to debut naeun overworked herself and was forced to rest, so she wasn't able to debut. she recovered fairly quickly and at nineteen eventually debuted with three other trainees, including the friend who caused her to become a trainee. their group, 4SEΔSONS, gained quite a lot of attention from debut, being from a well known entertainment company. over the past two years they have steadily been gaining a bigger fanbase and more recognition.

text

on a peaceful spring day on an old, wooden bench sat moon naeun as she nervously waited for her future husband. well, not her actual future husband, but someone who she would pretend to marry for the sake of the reality show aptly named 'we got married'.

with a sigh the female briefly turned on her phone screen to peer at the time for around the thousandth time since sitting down. why did she even agree to this in the first place? the other members would be far more suited to the show, but instead they managed to convince her to give it a shot. naeun wasn't even expecting to actually go on it in the end with the countless other candidates, yet here she was.

but there was no going back now. the articles had been published and the fans were all excited to see a brand new idol couple. without wanting to spoil her partner naeun didn't read any articles and blocked herself from any news of the whole ordeal, so she was completely clueless as to who she would be 'marrying'. her group members seemed to have some idea, however, as they giggled and fangirled and wished her luck when she left their residence earlier this morning. this just left naeun with even more questions. who was it? was it someone she knew? not that she was too close with any male idols other than their sunbaenims in the company's boy group,

what were they like? would she like them... and would they like her? head now overflowing with questions the girl let out an exasperated exclaimation, swinging her legs back and forth. it was okay though; if they didn't work out they would just leave the show and then go back to their respective lives. naeun would just try to be as honest as possible and show a good side of her on camera.

her fingernails gently tapped the phone screen to the rhythm of a song she was humming as she continued to wait. ignoring the cameras surrounding her naeun glanced around to see if he had arrived yet. nope, apparently not... the park was surprisingly quiet with barely any people around; the odd dog walker, a mother with her child, an eldery man taking a stroll. but no sign of another idol who she would be spending the next few weeks with.

// aa hope this is okay asdfgh

o and btw here are some ideas for stuff they'd do:

proposal

wedding preparations

wedding

honeymoon abroad

house hunting

fostering a cat/dog (prolly fostering rather than adopting bc of their busy schedules after they leave the show)

movie night

cooking together

amusement park

day at the beach

they'd prolly have stuff on their schedule as well so days when one of them is away or both of them are or smth. maybe they could also have one day when they're both at the same music show so their group members r like lol hi mr and mrs ahaha and theyre like aguisgus CX

a long overdue guide to the new coding after the update! thought i'd make this since the old guides are mostly outdated now,,, i am by no means an expert on coding p sure i did horribly in my computer science gcse rIP but i have been coding on ff for a while now, so if you need any extra help or have any questions you can just post on this thread or pm me!

so, a lot of people seem to be finding it hard to understand the new coding. however if you understood the old coding then it really isn't too different at all. if you didn't get any of the old coding whatsoever than that's fine too cx

fancyposts are pieces of coding which allow you to essentially customise boxes of text. yup, a fancypost is basically just a customisable box which you can put customisable text in. you place multiple fancyposts together to create a more elaborate looking overall fancypost / posting template (i believe it's more technically accurate to call it a posting template but like the oldie i am i just call them fancyposts oops).

fancypost coding is essentially a combination of bbcode, html and css, these terms probably sound scary but don't worry, you don't need to know too much about them. bbcode is designed specifically for quick and easy formatting for forum posts, such as being able to bold text which you can type out or click on a button to implement, it also uses square brackets ([ and ]). html is extremely similar but uses arrow brackets (< and >) and css is essentially the components that you put inside the html code to customise it. so the bbcode for fancyposts would be [fancypost='coding bits go here']text[/fancypost]

whereas the html would be <div style="css components here">text</div>

so on the surface we type in bbcode and use fancypost tags but the site stores it as html in divider tags (hence why there is an html mode to the editor).

now fancyposts involve visible coding that you'll have to type yourself, rather than just clicking a few buttons to bold or do whatever to your text. when coding fancyposts you'll want to be on the bbcode editor mode of the reply box. the html editor (the one you don't want to be using) will use the typewriter font and it's coding will use arrow brackets (< and >). if you are in this editor you can easily switch back to the other one by clicking on the button on the top left corner of the reply box (it looks like a sheet of paper with </> on it and with it's top right corner folded).

before i begin with the actual coding please note that you should not steal other people's coding. there are plenty of premade template threads where people have spent time and effort making fancyposts that others can freely use. if you use one of these follow the rules posted by the owner on their thread. copying a code is still plagiarism, and though the site no longer views it as a rule break it is still technically illegal and a bad thing to do.

THE BASIC SKELETON

the basic skeleton of a fancypost is

the part that says 'coding components go here' is where the bits that actually customise the box or text goes. when it comes to these they are made of two parts: name:value. the name part will tell you what it does whilst the value is the customisable bit that actually shows. taking background:red for example, the name 'background' tells you that this will affect the background of the fancypost, whilst the value assigned to it, 'red', tells you that the background of the fancypost will be red. these coding components will be listed below in a seperate post.

you also need to seperate each component by using a semicolon (;). so it would be like [fancypost='coding:bit; component:here; etc:andsoon;']

in addition you do not need to list certain compulsary components unlike the previous coding. e.g. you would've had to put things like border:none; background:transparent; in the old coding if you didn't want a background or border, but now you can leave out any unneeded components that you don't want.

the text that you want to put in the box goes in between the two fancypost tags ([fancypost]text goes here[/fancypost]

), though if you do not want text in that box you can omit that and leave it blank.

when coding you must always remember to end your tags. tags are composed of two parts, for example for fancyposts you have [fancypost] which you goes first and then [/fancypost] which goes last. all tags will have their first part in square brackets ([tag]) and their last part in square brackets but with a slash before the word ([/tag]). if you do not end your tags (e.g. you put only [fancypost]text rather than [fancypost]text[/fancypost]) the coding that the tags is supposed to do will not work.

key:

component | code

- extra info/notes

words in CAPS are variables that you need to change depending on what you want (e.g. replacing COLOR with the color you want, NO with the number thickness you want, etc.)

CUSTOMISING THE BOX

background colour | background:#COLOR

- you can use either a named colour (e.g. purple, firebrickred) or a colour code (eg #ffffff, #121212) here

border design | border: NOpx STYLE #COLOR

- the number px is how thick the border is in pixels

- color is the color of the border, and again you can used either a named colour or a colour code

- the style is the style of the border. styles you can use are:

width | width:NOpx

- the width percentage is what percentage of the screen it will take up horizontal wise. because of this fancyposts may look wide on a computer moniter but narrow on a mobile screen. because of this and the inability to use px it is recommended that you use 70% or higher when it comes to the width of your fancypost, so mobile users can read the text as well. if a fancypost is too thin on your mobile screen try turning it landscape so it will widen a bit.

- if you put a fancypost (f2) inside of another fancypost (f1) the percentage width of the second fancypost (f2) will be determined by the width of the 'mother' fancypost (f1) rather than the width of your moniter screen. e.g. the mother fancypost may be 80% in width so takes up 80% of the screen's width, but if you make the second fancypost (f2) 80% it will not be 80% of the width of the screen, but rather 80% of the width of the mother fancypost.

height | height:NOpx

- if you want the fancypost to expand then leave this out and it will automatically expand

- however fancyposts now have a height limit, so even if you leave out the height so the fancypost can expand it will turn into a scrollie when it hits max height

image background | background:url(IMG URL) or background-image:url(IMG URL)

- to get the url of an image, right click on the image and there should be an option to 'copy image address'. click on this and then the url will be copied

- both of these codes work so you can use either

image background size | background-size:NO% or background-size:cover

- this is how enlarged your background image will be in relation to the size of the fancypost

- so if you were to have an image much larger than your fancypost and not set a background size, it would only display the top left segment of the image that is the size of the fancypost

- if you set it to 100% the image will fit into the fancypost. therefore if when scaled down it isn't precisely the size of the fancypost it can repeat itself

- if you set it to <100% it will become smaller than the fancypost and repeat itself

- if you set it to >100% it will become larger than the fancypost. depending on the dimensions of the image and fancypost the image could posibly repeat itself as well

- if you set it to cover rather than a percentage, the image will be scaled down (or up) so at least one of it's dimensions (the width or height) matches one of the dimensions of the fancypost. with cover there will be no repeats of the image

image background position | background-position:POSITION or background:url(IMG URL)POSITION

- the position of the background image is basically which part of the image is displayed centralling in the fancypost

- you can use either code as they both work

- you can specify the position using top, center, bottom and then left, center, right. so if you want the top left corner put top left, or if you want the center right segment put center right

- if you just put top, center or bottom it will do the center of them (so top=top center, center=center center, bottom=bottom center)

centering fancyposts | margin:auto

- centering a fancypost is basically making it go in the center of the page, otherwise it will be on the left of the page

- with the old coding you would put center tags around the fancypost codes but now you need to add margin:auto to the code of the fancypost that you want to center

fancypost opacity | opacity:NO

- the number opacity is how opaque your fancypost (background) is

- it is a number between 0 and 1, the closer the number is to 1 the more opaque it will be

- if you want your fancypost to be fully opaque you can leave this code out

- also you shouldn't set the opacity to 0, since that would make it invisible/transparent

- also note that the opacity will affect both the fancypost (background) and the text in the fancypost

rounding fancypost corners | border-radius:NOpx; or border-radius:NOpx NOpx NOpx NOpx;

- this code rounds the corners of your fancypost

- the first code will round all of the corners equally to what you set it so (e.g. if set to 20px all corners will be rounded to 20px)

- the second code allows you to customise each corner. it goes clockwise in order from the top left corner, so the first number would be for the top left corner, the second number would be for the top right corner, etc.

scrolling | overflow:auto

- with this code the fancypost will automatically become a scrollie if the text exceeds the height set

- however even without it the fancypost will automatically become a scrollie if needed

- unfortunately hidden scrollies no longer work

padding | padding:NOpx

- padding is like extra pixels added to a fancypost (think of it like padding you add to a mattress or something lol)

- all fancyposts' padding is set to 0px by default

- it's useful to add padding to fancyposts with a background and text as adding padding means there is more space between the text and the edge of the fancypost, as shown in the example below

- if you only want to add padding to one side of the fancypost just add -SIDE to the padding part of the code. i.e. padding-top:NOpx, padding-bottom:NOpx, padding-left:NOpx or padding-right:NOpx

margins | margin-SIDE:NOpx

- margins are to do with how close or far your fancypost is to the top, bottom, left or right

- a positive number will push your fancypost in the opposite direction of the margin whereas a negative number will pull whatever's on that margin closer to your fancypost

- for whichever side margin you want to move your fancypost closer to or further away, replace SIDE with the side, so it would be margin-left:NOpx for the left side, margin-right:NOpx for the right side, margin-top:NOpx for the top side and margin-bottom:NOpx for the bottom side

floats | float:POSITION

- floats allow your fancypost to 'float' to the side of another fancypost

- the positions are left or right

- the way to code this is to have a mother fancypost which contains the text. inside the mother fancypost you would put the fancypost that you want to float, then write the text after the float fancypost. remember to close the float fancypost tag inside of the mother fancypost and outside of the text (so it would be [mother fancypost][float fancypost][/float fancypost]text here[/mother fancypost])

fancypost shadow | box-shadow:NO(WIDTH)px NO(HEIGHT)px NO(BLUR)px NO(OPACITY)px #COLOR

- for the NO(WIDTH) a positive number pulls it farther to the right, while a negative pushes it to the left

- for the NO(HEIGHT) a positive number pulls it down, while a negative pushes it up

- the NO(BLUR) affects how soft or hard the shadow is on the edges. the larger the number the softer it is

- the NO(OPACITY) affects the opacity/opaqueness of the shadow. this is a whole number rather than a decimal like the opacity code. the higher the number the more opaque it will be

- for multiple fancypost shadows add a comma and another 'NO(WIDTH)px NO(HEIGHT)px NO(BLUR)px NO(OPACITY)px #COLOR' (so the code for two shadows would be box-shadow:NO(WIDTH)px NO(HEIGHT)px NO(BLUR)px NO(OPACITY)px #COLOR, NO(WIDTH)px NO(HEIGHT)px NO(BLUR)px NO(OPACITY)px #COLOR etc.)

key:

component | code

- extra info/notes

CUSTOMISING THE TEXT

text color | color:#COLOR

- again you can put either a named color or a code here

text font | font-family:FONT

- for multiple worded fonts such as times new roman you can put it like that or condense it into one word (timesnewroman), either way works. though note that some fonts don't work on certain devices, so i'd say to stick to the common ones like verdana, georgia, etc.

text size | font-size:SIZEpt

- you can also use px, which is slightly smaller than pt (e.g. 10px would be a bit smaller than 10pt)

- for some reason ever since the update this hasn't rlly been working?? like it works for some smaller sizes, but not the larger ones. no idea why owo. if it doesn't work just put [size=NUMBER] outside of the fancypost code and around the text itself and it will work ([fancypost][size=NUMBER]text[/size][/fancypost])

text align | text-align:ALIGN

- you can put right, left, center or justify here

spacing between each line | line-height:NO%

- this is basically how much space there is between each line

- the larger the number the more space there is between each line

- though note that with 0% all of the lines will be scrunched up into one line. usually 100% or higher is most readable