#Coding Classes For Children

[codeyoung1]

Top-Rated Coding Courses for Kids

Best online coding classes for kids Our curated selection offers engaging and interactive learning experiences. Help your child develop essential coding skills in a fun and educational environment. Choose from a variety of courses tailored to different ages and experience levels. Enroll today and watch your child thrive with our top-rated online coding programs designed specifically for kids.

[wasabikitcat]

community college is so funny because half of the teachers are like "For this class you need to use lockdown browser for all quizzes and tests. You need to buy this 70 dollar textbook, and all papers turned in must be in APA format with a title page even if they're only 500 words long. I will not accept late assignments. Also you have a minimum of 4 assignments a week." and the other half are like "you don't need proctoring for the final exam I trust you. here's a download link to a pirated copy of the textbook. as long as your writing is coherent and demonstrates an understanding of the material I literally could not care less what format you use. I can't figure out how canvas works so I'm not giving you due dates, just make sure it's turned in before the grading period ends. your only weekly assignment is a forum post with a minimum of 100 words."

[cmescapade]

i wanna say i got back on my sims kick but it was from playing sims 4 multiplayer with my friend

...

my only screenshots are not sfw

[mariocki]

"We should stop thinking in terms of 'compensatory education' but consider, instead, most seriously and systematically the conditions and contexts of the educational environment.

The very form our research takes tends to confirm the beliefs underlying the organization, transmission and evaluation of knowledge by the school. Research proceeds by assessing the criteria of attainment that schools hold, and then measures the competence of different social groups in reaching these criteria. We take one group of children, whom we know beforehand possess attributes favourable to school achievement; and a second group of children, whom we know beforehand lack these attributes. Then we evaluate one group in terms of what it lacks when compared with another. In this way research unwittingly underscores the notion of deficit and confirms the status quo of a given organization, transmission and, in particular, evaluation of knowledge. Research very rarely challenges or exposes the social assumptions underlying what counts as valid knowledge, or what counts as a valid realization of that knowledge."

- Basil Bernstein, Education Cannot Compensate for Society, in Education for Democracy (2nd ed., 1972)

[magdaclaire]

re: the american education system showing high school children their "dead" peers in an effort to lessen teenage drunk driving after prom,

the suing part is one hundred percent true but several parents (including my mom <3) threatened to personally beat the ass of the principal at the time

[curiosity-killed]

despite the fact that, for at least 14 years, my Notable Dance Ability™ (to the point that every single new teacher and friend AND the artistic director I last auditioned for have to comment on it and/or make me demonstrate) is That Girl Can Jump, I've never thought much about being naturally good at it aside from joking about my thighs but now I'm trying to figure out how to teach kids the progression from like baby jumps to fun jumps and my brain is just like well. you just. you Just Do It. that is All.

[digitalteacherhydposts]

Download Digital Teacher Brochures

Digital teacher brochures: download our econtent brochures for state (Telangana & Andhra Pradesh) and CBSE board syllabus & English language lab.

Read More at: https://www.digitalteacher.in/download-brochure

#eLearning #DigiClass #SmartClassSolution #SmartClassroom #DigitalClassroom #SmartClass #Software #Technology #Education #OnlineEducation #EducationTechnology #DigitalTeacher #DigitalEducation

[mathslear]

How to shape kids’ future with AI and Machine Learning?

What is Artificial Intelligence?

Artificial Intelligence (AI) is the science of making the computer learn and make decisions as humans do. AI is basically helping the computer to acquire intelligence similar to humans.

 Dive into the captivating world of AI and Machine Learning with our specialised course designed for kids. BYITC offers an exciting introduction to the fundamentals of AI, making it accessible and engaging for young learners. Children will explore how AI technologies such as voice recognition, machine learning, and robotics are shaping our world, fostering a deep understanding of how these tools work.

Back to School! Book Your Free Trial Today!

👉 https://supermathsapp.com/home/register

Structured to inspire curiosity and creativity, the course encourages kids to think critically about the role of AI in society and its potential for the future. Our goal is to empower kids with the skills and confidence to become not just consumers of technology but innovators and creators, ready to contribute to the AI-driven future. BYITC also conducts AI workshops from time to time so as to make introduce to the fundamentals and help them with their queries.

How did our recent AI and Machine Learning workshop help kids?

BYITC Coding AI workshop was a vibrant, energy-filled day from start to finish. We kicked off with a simple yet engaging introduction to AI and Machine Learning. Using examples from everyday life, we helped the kids understand how AI is used in things like video games, online searches, and even smart toys.

Next, we dove into Scratch, the visual programming language that’s both fun and intuitive for young learners. After a brief overview of Scratch’s interface and capabilities, the kids were introduced to the machine learning extension. The excitement was palpable as they realised they could train a machine learning model themselves!

Reflections and Future Plans: Reflecting on the success of this AI workshop, we are filled with positivity and excitement for the future. The engagement and enthusiasm of theparticipants confirmed our belief that children are more than ready to tackle complex concepts like AI and Machine Learning.

Our students are already having fun learning AI and Machine Learning with lots of interesting projects. Give your child a head start on the future by teaching them AI and Machine Learning today at BYITC and Book a FREE trial class today.

Originally Published at: https://supermaths.co.uk/how-to-shape-kids-future-with-ai-and-machine-learning/

[jcmarchi]

CSS Selectors

New Post has been published on https://thedigitalinsider.com/css-selectors/

CSS Selectors

Overview

CSS is really good at many things, but it’s really, really good at two specific things: selecting elements and styling them. That’s the raison d’être for CSS and why it’s a core web language. In this guide, we will cover the different ways to select elements — because the styles we write are pretty much useless without the ability to select which elements to apply them to.

The source of truth for CSS selectors is documented in the Selectors Module Level 4 specification. With one exception (which we’ll get to), all of the selectors covered here are well-covered by browsers across the board, and most certainly by all modern browsers.

In addition to selectors, this guide also looks at CSS combinators. If selectors identify what we are selecting, you might think of combinators as how the styles are applied. Combinators are like additional instructions we give CSS to select a very particular element on the page, not totally unlike the way we can use filters in search engines to find the exact result we want.

Quick reference

Common Selectors

/* Universal */ * box-sizing: border-box; /* Type or Tag */ p margin-block: 1.5rem; /* Classname */ .class text-decoration: underline; /* ID */ #id font-family: monospace; /* Relational */ li:has(a) display: flex;

Common Combinators

/* Descendant */ header h1 /* Selects all Heading 1 elements in a Header element. */ /* Child */ header > h1 /* Selects all Heading 1 elements that are children of Header elements. */ /* General sibling */ h1 ~ p /* Selects a Paragraph as long as it follows a Heading 1. */ /* Adjacent sibling */ h1 + p /* Selects a Paragraph if it immediately follows a Heading 1 */ /* Chained */ h1, p /* Selects both elements. */

General Selectors

When we talk about CSS selectors, we’re talking about the first part of a CSS ruleset:

/* CSS Ruleset */ selector /* Style rule */ property: value;

See that selector? That can be as simple as the HTML tag we want to select. For example, let’s select all <article> elements on a given page.

/* Select all <article> elements... */ article /* ... and apply this background-color on them */ background-color: hsl(25 100% 50%);

That’s the general process of selecting elements to apply styles to them. Selecting an element by its HTML tag is merely one selector type of several. Let’s see what those are in the following section.

Element selectors

Element selectors are exactly the type of selector we looked at in that last example: Select the element’s HTML tag and start styling!

That’s great and all, but consider this: Do you actually want to select all of the <article> elements on the page? That’s what we’re doing when we select an element by its tag — any and all HTML elements matching that tag get the styles. The following demo selects all <article> elements on the page, then applies a white (#fff) background to them. Notice how all three articles get the white background even though we only wrote one selector.

I’ve tried to make it so the relevant for code for this and other demos in this guide is provided at the top of the CSS tab. Anything in a @layer can be ignored. And if you’re new to @layer, you can learn all about it in our CSS Cascade Layers guide.

But maybe what we actually want is for the first element to have a different background — maybe it’s a featured piece of content and we need to make it stand out from the other articles. That requires us to be more specific in the type of selector we use to apply the styles.

Let’s turn our attention to other selector types that allow us to be more specific about what we’re selecting.

ID selectors

ID selectors are one way we can select one element without selecting another of the same element type. Let’s say we were to update the HTML in our <article> example so that the first article is “tagged” with an ID:

<article id="featured"> <!-- Article 1 --> </article> <article> <!-- Article 2 --> </article> <article> <!-- Article 3 --> </article>

Now we can use that ID to differentiate that first article from the others and apply styles specifically to it. We prepend a hashtag character (#) to the ID name when writing our CSS selector to properly select it.

/* Selects all <article> elements */ article background: #fff; /* Selects any element with id="featured" */ #featured background: hsl(35 100% 90%); border-color: hsl(35 100% 50%);

There we go, that makes the first article pop a little more than the others!

Before you go running out and adding IDs all over your HTML, be aware that IDs are considered a heavy-handed approach to selecting. IDs are so specific, that it is tough to override them with other styles in your CSS. IDs have so much specificity power than any selector trying to override it needs at least an ID as well. Once you’ve reached near the top of the ladder of this specificity war, it tends to lead to using !important rules and such that are in turn nearly impossible to override.

Let’s rearrange our CSS from that last example to see that in action:

/* Selects any element with id="featured" */ #featured background: hsl(35 100% 90%); border-color: hsl(35 100% 50%); /* Selects all <article> elements */ article background: #fff;

The ID selector now comes before the element selector. According to how the CSS Cascade determines styles, you might expect that the article elements all get a white background since that ruleset comes after the ID selector ruleset. But that’s not what happens.

So, you see how IDs might be a little too “specific” when it comes to selecting elements because it affects the order in which the CSS Cascade applies styles and that makes styles more difficult to manage and maintain.

The other reason to avoid IDs as selectors? We’re technically only allowed to use an ID once on a page, per ID. In other words, we can have one element with #featured but not two. That severely limits what we’re able to style if we need to extend those styles to other elements — not even getting into the difficulty of overriding the ID’s styles.

A better use case for IDs is for selecting items in JavaScript — not only does that prevent the sort of style conflict we saw above, but it helps maintain a separation of concerns between what we select in CSS for styling versus what we select in JavaScript for interaction.

Another thing about ID selectors: The ID establishes what we call an “anchor” which is a fancy term for saying we can link directly to an element on the page. For example, if we have an article with an ID assigned to it:

<article id="featured">...</article>

…then we can create a link to it like this:

<a href="featured">Jump to article below ⬇️</a> <!-- muuuuuuch further down the page. --> <article id="featured">...</article>

Clicking the link will navigate you to the element as though the link is anchored to that element. Try doing exactly that in the following demo:

This little HTML goodie opens up some pretty darn interesting possibilities when we sprinkle in a little CSS. Here are a few articles to explore those possibilities.

Class selectors

Class selectors might be the most commonly used type of CSS selector you will see around the web. Classes are ideal because they are slightly more specific than element selectors but without the heavy-handedness of IDs. You can read a deep explanation of how the CSS Cascade determines specificity, but the following is an abbreviated illustration focusing specifically (get it?!) on the selector types we’ve looked at so far.

That’s what makes class selectors so popular — they’re only slightly more specific than elements, but keep specificity low enough to be manageable if we need to override the styles in one ruleset with styles in another.

The only difference when writing a class is that we prepend a period (.) in front of the class name instead of the hashtag (#).

/* Selects all <article> elements */ article background: #fff; /* Selects any element with class="featured" */ .featured background: hsl(35 100% 90%); border-color: hsl(35 100% 50%);

Here’s how our <article> example shapes up when we swap out #featured with .featured.

Same result, better specificity. And, yes, we can absolutely combine different selector types on the same element:

<article id="someID" class="featured">...</article>

Do you see all of the possibilities we have to select an <article>? We can select it by:

Its element type (article)

Its ID (#someID)

Its class (.featured)

The following articles will give you some clever ideas for using class selectors in CSS.

But we have even more ways to select elements like this, so let’s continue.

Attribute selectors

ID and class selectors technically fall into this attribute selectors category. We call them “attributes” because they are present in the HTML and give more context about the element. All of the following are attributes in HTML:

<!-- ID, Class, Data Attribute --> <article id="#id" class=".class" data-attribute="attribute"> </article> <!-- href, Title, Target --> <a href="https://css-tricks.com" title="Visit CSS-Tricks" target="_blank"></a> <!-- src, Width, Height, Loading --> <img src="star.svg" width="250" height="250" loading="laxy" > <!-- Type, ID, Name, Checked --> <input type="checkbox" id="consent" name="consent" checked /> <!-- Class, Role, Aria Label --> <div class="buttons" role="tablist" aria-label="Tab Buttons">

Anything with an equals sign (=) followed by a value in that example code is an attribute. So, we can technically style all links with an href attribute equal to https://css-tricks.com:

a[href="https://css-tricks.com"] color: orangered;

Notice the syntax? We’re using square brackets ([]) to select an attribute instead of a period or hashtag as we do with classes and IDs, respectively.

The equals sign used in attributes suggests that there’s more we can do to select elements besides matching something that’s exactly equal to the value. That is indeed the case. For example, we can make sure that the matching selector is capitalized or not. A good use for that could be selecting elements with the href attribute as long as they do not contain uppercase letters:

/* Case sensitive */ a[href*='css-tricks' s]

The s in there tells CSS that we only want to select a link with an href attribute that does not contain uppercase letters.

<!-- 👎 No match --> <a href="https://CSS-Tricks.com">...</a> <!-- 👍 Match! --> <a href="https://css-tricks.com">...</a>

If case sensitivity isn’t a big deal, we can tell CSS that as well:

/* Case insensitive */ a[href*='css-tricks' i]

Now, either one of the link examples will match regardless of there being upper- or lowercase letters in the href attribute.

<!-- 👍 I match! --> <a href="https://CSS-Tricks.com">...</a> <!-- 👍 I match too! --> <a href="https://css-tricks.com">...</a>

There are many, many different types of HTML attributes. Be sure to check out our Data Attributes guide for a complete rundown of not only [data-attribute] but how they relate to other attributes and how to style them with CSS.

Universal selector

CSS-Tricks has a special relationship with the Universal Selector — it’s our logo!

That’s right, the asterisk symbol (*) is a selector all unto itself whose purpose is to select all the things. Quite literally, we can select everything on a page — every single element — with that one little asterisk. Note I said every single element, so this won’t pick up things like IDs, classes, or even pseudo-elements. It’s the element selector for selecting all elements.

/* Select ALL THE THINGS! 💥 */ * /* Styles */

Or, we can use it with another selector type to select everything inside a specific element.

/* Select everything in an <article> */ article * /* Styles */

That is a handy way to select everything in an <article>, even in the future if you decide to add other elements inside that element to the HTML. The times you’ll see the Universal Selector used most is to set border-sizing on all elements across the board, including all elements and pseudo-elements.

*, *::before, *::after box-sizing: border-box;

There’s a good reason this snippet of CSS winds up in so many stylesheets, which you can read all about in the following articles.

Sometimes the Universal Selector is implied. For example, when using a pseudo selector at the start of a new selector. These are selecting exactly the same:

*:has(article) :has(article)

Pseudo-selectors

Pseudo-selectors are for selecting pseudo-elements, just as element selectors are for selecting elements. And a pseudo-element is just like an element, but it doesn’t actually show up in the HTML. If pseudo-elements are new to you, we have a quick explainer you can reference.

Every element has a ::before and ::after pseudo-element attached to it even though we can’t see it in the HTML.

<div class="container"> <!-- ::before psuedo-element here --> <div>Item</div> <div>Item</div> <div>Item</div> <!-- ::after psuedo-element here --> </div>

These are super handy because they’re additional ways we can hook into an element an apply additional styles without adding more markup to the HTML. Keep things as clean as possible, right?!

We know that ::before and ::after are pseudo-elements because they are preceded by a pair of colons (::). That’s how we select them, too!

.container::before /* Styles */

The ::before and ::after pseudo-elements can also be written with a single colon — i.e., :before and :after — but it’s still more common to see a double colon because it helps distinguish pseudo-elements from pseudo-classes.

But there’s a catch when using pseudo-selectors: they require the content property. That’s because pseudos aren’t “real” elements but ones that do not exist as far as HTML is concerned. That means they need content that can be displayed… even if it’s empty content:

.container::before content: "";

Of course, if we were to supply words in the content property, those would be displayed on the page.

Article

on

Feb 4, 2022

Meet the Pseudo Class Selectors

Video

on

Feb 25, 2015

#94: Intro to Pseudo Elements

▶ Running Time: 18:37

Article

on

Aug 29, 2018

::before vs :before

Article

on

Sep 21, 2021

7 Practical Uses for the ::before and ::after Pseudo-Elements in CSS

Article

on

Aug 3, 2021

Use Cases for Multiple Pseudo Elements

Article

on

Aug 19, 2021

A Whole Bunch of Amazing Stuff Pseudo Elements Can Do

Article

on

Jul 9, 2019

A Little Reminder That Pseudo Elements are Children, Kinda.

Article

on

Dec 14, 2020

One Invalid Pseudo Selector Equals an Entire Ignored Selector

Article

on

Sep 27, 2021

CSS Pseudo Commas

Article

on

Apr 16, 2013

List of Pseudo-Elements to Style Form Controls

Article

on

Oct 24, 2020

Animating the `content` Property

Article

on

May 31, 2017

Animating Single Div Art

Article

on

Jun 5, 2020

Text Wrapping & Inline Pseudo Elements

Article

on

Jul 25, 2011

3D Cube with One Element

Complex selectors

Complex selectors may need a little marketing help because “complex” is an awfully scary term to come across when you’re in the beginning stages of learning this stuff. While selectors can indeed become complex and messy, the general idea is super straightforward: we can combine multiple selectors in the same ruleset.

Let’s look at three different routes we have for writing these “not-so-complex” complex selectors.

Listing selectors

First off, it’s possible to combine selectors so that they share the same set of styles. All we do is separate each selector with a comma.

.selector-1, .selector-2, .selector-3 /* We share these styles! 🤗 */

You’ll see this often when styling headings — which tend to share the same general styling except, perhaps, for font-size.

h1, h2, h3, h4, h5, h6 color: hsl(25 80% 15%); font-family: "Poppins", system-ui;

Adding a line break between selectors can make things more legible. You can probably imagine how complex and messy this might get. Here’s one, for example:

section h1, section h2, section h3, section h4, section h5, section h6, article h1, article h2, article h3, article h4, article h5, article h6, aside h1, aside h2, aside h3, aside h4, aside h5, aside h6, nav h1, nav h2, nav h3, nav h4, nav h5, nav h6 color: #BADA55;

Ummmm, okay. No one wants this in their stylesheet. It’s tough to tell what exactly is being selected, right?

The good news is that we have modern ways of combining these selectors more efficiently, such as the :is() pseudo selector. In this example, notice that we’re technically selecting all of the same elements. If we were to take out the four section, article, aside, and nav element selectors and left the descendants in place, we’d have this:

h1, h2, h3, h4, h5, h6, h1, h2, h3, h4, h5, h6, h1, h2, h3, h4, h5, h6, h1, h2, h3, h4, h5, h6, color: #BADA55;

The only difference is which element those headings are scoped to. This is where :is() comes in handy because we can match those four elements like this:

:is(section, article, aside, nav) color: #BADA55;

That will apply color to the elements themselves, but what we want is to apply it to the headings. Instead of listing those out for each heading, we can reach for :is() again to select them in one fell swoop:

/* Matches any of the following headings scoped to any of the following elements. */ :is(section, article, aside, nav) :is(h1, h2, h3, h4, h5, h6) color: #BADA55;

While we’re talking about :is() it’s worth noting that we have the :where() pseudo selector as well and that it does the exact same thing as :is(). The difference? The specificity of :is() will equal the specificity of the most specific element in the list. Meanwhile, :where() maintains zero specificity. So, if you want a complex selector like this that’s easier to override, go with :where() instead.

Almanac

on

Dec 2, 2022

:is

:is(ul, ol) li color: #f8a100;

Almanac

on

Jul 14, 2021

:where

main :where(h1, h2, h3) color: #f8a100;

Article

on

Apr 1, 2021

:where() has a cool specificity trick, too.

Article

on

Jun 10, 2020

CSS :is() and :where() are coming to browsers

Article

on

Apr 15, 2021

Platform News: Prefers Contrast, MathML, :is(), and CSS Background Initial Values

Article

on

Jul 12, 2021

Using the Specificity of :where() as a CSS Reset

Nesting selectors

That last example showing how :is() can be used to write more efficient complex selectors is good, but we can do even better now that CSS nesting is a widely supported feature.

This browser support data is from Caniuse, which has more detail. A number indicates that browser supports the feature at that version and up.

Desktop

Chrome Firefox IE Edge Safari 120 117 No 120 17.2

Mobile / Tablet

Android Chrome Android Firefox Android iOS Safari 126 127 126 17.2

CSS nesting allows us to better see the relationship between selectors. You know how we can clearly see the relationship between elements in HTML when we indent descendant elements?

<!-- Parent --> <article> <!-- Child --> <img src="" alt="..."> <!-- Child --> <div class="article-content"> <!-- Grandchild --> <h2>Title</h2> <!-- Grandchild --> <p>Article content.</p> </div> </article>

CSS nesting is a similar way that we can format CSS rulesets. We start with a parent ruleset and then embed descendant rulesets inside. So, if we were to select the <h2> element in that last HTML example, we might write a descendant selector like this:

article h2 /* Styles */

With nesting:

article /* Article styles */ h2 /* Heading 2 styles */

You probably noticed that we can technically go one level deeper since the heading is contained in another .article-content element:

article /* Article styles */ .article-content /* Container styles */ h2 /* Heading 2 styles */

So, all said and done, selecting the heading with nesting is the equivalent of writing a descendant selector in a flat structure:

article .article-content h2 /* Heading 2 styles */

You might be wondering how the heck it’s possible to write a chained selector in a nesting format. I mean, we could easily nest a chained selector inside another selector:

article /* Article styles */ h2.article-content /* Heading 2 styles */

But it’s not like we can re-declare the article element selector as a nested selector:

article /* Article styles */ /* Nope! 👎 */ article.article-element /* Container styles */ /* Nope! 👎 */ h2.article-content /* Heading 2 styles */

Even if we could do that, it sort of defeats the purpose of a neatly organized nest that shows the relationships between selectors. Instead, we can use the ampersand (&) symbol to represent the selector that we’re nesting into. We call this the nesting selector.

article &.article-content /* Equates to: article.article-content */

Compounding selectors

We’ve talked quite a bit about the Cascade and how it determines which styles to apply to matching selectors using a specificity score. We saw earlier how an element selector is less specific than a class selector, which is less specific than an ID selector, and so on.

article /* Specificity: 0, 0, 1 */ .featured /* Specificity: 0, 1, 0 */ #featured /* Specificity: 1, 0, 0 */

Well, we can increase specificity by chaining — or “compounding” — selectors together. This way, we give our selector a higher priority when it comes to evaluating two or more matching styles. Again, overriding ID selectors is incredibly difficult so we’ll work with the element and class selectors to illustrate chained selectors.

We can chain our article element selector with our .featured class selector to generate a higher specificity score.

article /* Specificity: 0, 0, 1 */ .featured /* Specificity: 0, 1, 0 */ articie.featured /* Specificity: 0, 1, 1 */

This new compound selector is more specific (and powerful!) than the other two individual selectors. Notice in the following demo how the compound selector comes before the two individual selectors in the CSS yet still beats them when the Cascade evaluates their specificity scores.

Interestingly, we can use “fake” classes in chained selectors as a strategy for managing specificity. Take this real-life example:

.wp-block-theme-button .button:not(.specificity):not(.extra-specificity)

Whoa, right? There’s a lot going on there. But the idea is this: the .specificity and .extra-specificity class selectors are only there to bump up the specificity of the .wp-block-theme .button descendant selector. Let’s compare the specificity score with and without those artificial classes (that are :not() included in the match).

.wp-block-theme-button .button /* Specificity: 0, 2, 0 */ .wp-block-theme-button .button:not(.specificity) /* Specificity: 0, 3, 0 */ .wp-block-theme-button .button:not(.specificity):not(.extra-specificity /* Specificity: 0, 4, 0 */

Interesting! I’m not sure if I would use this in my own CSS but it is a less heavy-handed approach than resorting to the !important keyword, which is just as tough to override as an ID selector.

Combinators

If selectors are “what” we select in CSS, then you might think of CSS combinators as “how” we select them. they’re used to write selectors that combine other selectors in order to target elements. Inception!

The name “combinator” is excellent because it accurately conveys the many different ways we’re able to combine selectors. Why would we need to combine selectors? As we discussed earlier with Chained Selectors, there are two common situations where we’d want to do that:

When we want to increase the specificity of what is selected.

When we want to select an element based on a condition.

Let’s go over the many types of combinators that are available in CSS to account for those two situations in addition to chained selectors.

Descendant combinator

We call it a “descendant” combinator because we use it to select elements inside other elements, sorta like this:

/* Selects all elements in .parent with .child class */ .parent .child

…which would select all of the elements with the .child class in the following HTML example:

<div class="parent"> <div class="child"></div> <div class="child"></div> <div class="friend"></div> <div class="child"></div> <div class="child"></div> </div>

See that element with the .friend classname? That’s the only element inside of the .parent element that is not selected with the .parent .child descendant combinator since it does not match .child even though it is also a descendant of the .parent element.

Child combinator

A child combinator is really just an offshoot of the descendant combinator, only it is more specific than the descendant combinator because it only selects direct children of an element, rather than any descendant.

Let’s revise the last HTML example we looked at by introducing a descendant element that goes deeper into the family tree, like a .grandchild:

<div class="parent"> <div class="child"></div> <div class="child"> <div class="grandchild"></div> </div> <div class="child"></div> <div class="child"></div> </div>

So, what we have is a .parent to four .child elements, one of which contains a .grandchild element inside of it.

Maybe we want to select the .child element without inadvertently selecting the second .child element’s .grandchild. That’s what a child combinator can do. All of the following child combinators would accomplish the same thing:

/* Select only the "direct" children of .parent */ .parent > .child .parent > div .parent > *

See how we’re combining different selector types to make a selection? We’re combinating, dangit! We’re just doing it in slightly different ways based on the type of child selector we’re combining.

/* Select only the "direct" children of .parent */ .parent > #child { /* direct child with #child ID */ .parent > .child /* direct child with .child class */ .parent > div /* direct child div elements */ .parent > * /* all direct child elements */

It’s pretty darn neat that we not only have a way to select only the direct children of an element, but be more or less specific about it based on the type of selector. For example, the ID selector is more specific than the class selector, which is more specific than the element selector, and so on.

General sibling combinator

If two elements share the same parent element, that makes them siblings like brother and sister. We saw an example of this in passing when discussing the descendant combinator. Let’s revise the class names from that example to make the sibling relationship a little clearer:

<div class="parent"> <div class="brother"></div> <div class="sister"></div> </div>

This is how we can select the .sister element as long as it is preceded by a sibling with class .brother.

/* Select .sister only if follows .brother */ .brother ~ .sister

The Tilda symbol (~) is what tells us this is a sibling combinator.

It doesn’t matter if a .sister comes immediately after a .brother or not — as long as a .sister comes after a brother and they share the same parent element, it will be selected. Let’s see a more complicated HTML example:

<main class="parent"> <!-- .sister immediately after .brother --> <div class="brother"></div> <div class="sister"></div> <!-- .sister immediately after .brother --> <div class="brother"></div> <div class="sister"></div> <!-- .sister immediately after .sister --> <div class="sister"></div> <!-- .cousin immediately after .brother --> <div class="brother"></div> <div class="cousin"> <!-- .sister contained in a .cousin --> <div class="sister"></div> </div> </main>

The sibling combinator we wrote only selects the first three .sister elements because they are the only ones that come after a .brother element and share the same parent — even in the case of the third .sister which comes after another sister! The fourth .sister is contained inside of a .cousin, which prevents it from matching the selector.

Let’s see this in context. So, we can select all of the elements with an element selector since each element in the HTML is a div:

From there, we can select just the brothers with a class selector to give them a different background color:

We can also use a class selector to set a different background color on all of the elements with a .sister class:

And, finally, we can use a general sibling combinator to select only sisters that are directly after a brother.

Did you notice how the last .sister element’s background color remained green while the others became purple? That’s because it’s the only .sister in the bunch that does not share the same .parent as a .brother element.

Adjacent combinator

Believe it or not, we can get even more specific about what elements we select with an adjacent combinator. The general sibling selector we just looked at will select all of the .sister elements on the page as long as it shares the same parent as .brother and comes after the .brother.

What makes an adjacent combinator different is that it selects any element immediately following another. Remember how the last .sister didn’t match because it is contained in a different parent element (i.e., .cousin)? Well, we can indeed select it by itself using an adjacent combinator:

/* Select .sister only if directly follows .brother */ .brother + .sister

Notice what happens when we add that to our last example:

The first two .sister elements changed color! That’s because they are the only sisters that come immediately after a .brother. The third .sister comes immediately after another .sister and the fourth one is contained in a .cousin which prevents both of them from matching the selection.

Learn more about CSS selectors

Table of contents

References

The vast majority of what you’re reading here is information pulled from articles we’ve published on CSS-Tricks and those are linked up throughout the guide. In addition to those articles, the following resources were super helpful for putting this guide together.

[ai-robotics-classes-singapore]

Empowering Young Minds: NYRA Academy's Innovative Approach to Kids' Coding Education

In today's rapidly evolving digital landscape, the ability to code has become a fundamental skill for success. Recognizing the importance of nurturing this skill from a young age, NYRA Academy proudly offers a diverse range of coding and robotics programs tailored specifically for children and youths.

At NYRA Academy, we understand that traditional coding courses may not always capture the attention and imagination of young learners. That's why we've developed engaging and interactive Kids Coding Courses designed to make learning fun and accessible for all skill levels. From Scratch Programming for Kids to Children's Robotics Classes, our programs cater to the diverse interests and learning styles of our students.

Our commitment to providing quality youth coding education is evident in our Scratch Coding Certificate program. Upon completion, students receive a tangible recognition of their achievements, motivating them to further explore the exciting world of coding. With a focus on hands-on learning and creative problem-solving, our Kid-Friendly Coding Training ensures that every child feels empowered to unleash their potential in the digital realm.

One of the highlights of our curriculum is our Junior Robotics Workshops, where young enthusiasts delve into the fascinating realm of robotics, learning to build and program their own robots. Through interactive projects and collaborative activities, students develop critical thinking and teamwork skills essential for success in today's tech-driven world.

Programming with Scratch for Children opens the door to endless possibilities as kids learn to create interactive stories, animations, and games. Our expert instructors guide students through every step of the process, fostering a passion for coding that extends beyond the classroom.

For those interested in exploring the creative side of coding, our courses in Animation and Game Design for Kids provide a platform for budding artists and storytellers to bring their ideas to life. Through hands-on projects, students learn the fundamentals of design and animation, gaining valuable skills that can be applied across various digital platforms.

NYRA Academy also offers Coding Short Courses specifically tailored for students aged 9 to 15, providing a comprehensive introduction to coding concepts in a condensed format. Whether your child is just beginning their coding journey or looking to expand their skills, our Beginner Coding Lessons for Youngsters provide a supportive and nurturing environment for growth and exploration.

At NYRA Academy, we believe that every child has the potential to become a coding champion. With our innovative approach to kids' coding education, we strive to inspire the next generation of digital innovators, equipping them with the skills and confidence to thrive in an ever-changing world. Join us on this exciting journey of discovery and creativity at NYRA Academy today!

[ot3]

If you don't know this already, please try and internalize it: the idea that people join the US military primarily because they are young people at a disadvantage in life coerced into believing it is the most accessible path to upward mobility is not true.

if you're parroting this talking point, you are doing propaganda for the US military and you just need to stop saying it. here's an article from the Military Times that breaks the finding of various studies like this one from 2020 and this one from 2018 that analyze motivations for joining the military and popular conceptions of motivations for joining the military. Here's a pretty important excerpt:

Further, they hypothesized that some of this possible misconception about poorer Americans joining the military was a geographical issue. While the Defense Department tracks the zip codes of recruits ― and historically, many of them come from more rural areas in the southeast ― it doesn’t track their incomes or their parents’ incomes, which leads to assumptions that the poorer their communities, the poorer the recruits. [...] Using Bureau of Labor Statistics data from 1997 to 2008, they found that the services have recruited primarily from the middle class, America’s largest socio-economic demographic. “We show that recent recruits tend to have higher than average socioeconomic background: they disproportionally come from the middle of the family income, family wealth, and cognitive skill distributions, with both tails under-represented,” they found.

Here's from the army times:

Surveyed troops said these were the top five reasons for staying in the Army. The percentages indicate how many troops felt the factors were “extremely important” to them:

- Opportunity to serve my country — 53.5% - How well my retirement pay or benefits will meet my future needs — 45.1% - Opportunities to lead or train soldiers — 43.5% - My sense of purpose — 38.1% -How well my pay or benefits meet my present needs — 37%

Also mentioned in other sources but here from the NY times in 2020 as well, army enlistment is becoming increasingly skewed towards being the children of people who have previously served.

The main predictors are not based on class or race. Army data show service spread mostly evenly through middle-class and “downscale” groups. Youth unemployment turns out not to be the prime factor.

'Joining the army to lift yourself out of poverty' is not the reality for military service, it is the narrative used by the military in it's marketing and recruitment. if you go around repeating it i hope for your sake you're at least on their payroll! if you're going to bootlick don't do it for free!

[workcoderight]

We at Code Right aspire to instill the 21st century skills of Programming and Computational Thinking within the young minds through our fun and intriguing curriculum. Children will be introduced to another fascinating dimension of technology empowering them to become the ‘architects‘ of the digital era.

Programming has become an essential skill for grown-ups and children alike. Coding is a creative process to instruct a computer on how to perform a task. Coding for kids at early as age 5 helps kids refine their design, logic, and problem-solving abilities. At Code Right, coding for kids is a typical unplugged gamified coding activity class with an edge of drag and drop platforms.

Coding for kids at early as age 5 helps kids refine their design, logic, and problem-solving abilities. At Code Right, coding for kids is a typical unplugged gamified coding activity class with an edge of drag and drop platforms.

[suzannahnatters]

all RIGHT:

Why You're Writing Medieval (and Medieval-Coded) Women Wrong: A RANT

(Or, For the Love of God, People, Stop Pretending Victorian Style Gender Roles Applied to All of History)

This is a problem I see alllll over the place - I'll be reading a medieval-coded book and the women will be told they aren't allowed to fight or learn or work, that they are only supposed to get married, keep house and have babies, &c &c.

If I point this out ppl will be like "yes but there was misogyny back then! women were treated terribly!" and OK. Stop right there.

By & large, what we as a culture think of as misogyny & patriarchy is the expression prevalent in Victorian times - not medieval. (And NO, this is not me blaming Victorians for their theme park version of "medieval history". This is me blaming 21st century people for being ignorant & refusing to do their homework).

Yes, there was misogyny in medieval times, but 1) in many ways it was actually markedly less severe than Victorian misogyny, tyvm - and 2) it was of a quite different type. (Disclaimer: I am speaking specifically of Frankish, Western European medieval women rather than those in other parts of the world. This applies to a lesser extent in Byzantium and I am still learning about women in the medieval Islamic world.)

So, here are the 2 vital things to remember about women when writing medieval or medieval-coded societies

FIRST. Where in Victorian times the primary axes of prejudice were gender and race - so that a male labourer had more rights than a female of the higher classes, and a middle class white man would be treated with more respect than an African or Indian dignitary - In medieval times, the primary axis of prejudice was, overwhelmingly, class. Thus, Frankish crusader knights arguably felt more solidarity with their Muslim opponents of knightly status, than they did their own peasants. Faith and age were also medieval axes of prejudice - children and young people were exploited ruthlessly, sent into war or marriage at 15 (boys) or 12 (girls). Gender was less important.

What this meant was that a medieval woman could expect - indeed demand - to be treated more or less the same way the men of her class were. Where no ancient legal obstacle existed, such as Salic law, a king's daughter could and did expect to rule, even after marriage.

Women of the knightly class could & did arm & fight - something that required a MASSIVE outlay of money, which was obviously at their discretion & disposal. See: Sichelgaita, Isabel de Conches, the unnamed women fighting in armour as knights during the Third Crusade, as recorded by Muslim chroniclers.

Tolkien's Eowyn is a great example of this medieval attitude to class trumping race: complaining that she's being told not to fight, she stresses her class: "I am of the house of Eorl & not a serving woman". She claims her rights, not as a woman, but as a member of the warrior class and the ruling family. Similarly in Renaissance Venice a doge protested the practice which saw 80% of noble women locked into convents for life: if these had been men they would have been "born to command & govern the world". Their class ought to have exempted them from discrimination on the basis of sex.

So, tip #1 for writing medieval women: remember that their class always outweighed their gender. They might be subordinate to the men within their own class, but not to those below.

SECOND. Whereas Victorians saw women's highest calling as marriage & children - the "angel in the house" ennobling & improving their men on a spiritual but rarely practical level - Medievals by contrast prized virginity/celibacy above marriage, seeing it as a way for women to transcend their sex. Often as nuns, saints, mystics; sometimes as warriors, queens, & ladies; always as businesswomen & merchants, women could & did forge their own paths in life

When Elizabeth I claimed to have "the heart & stomach of a king" & adopted the persona of the virgin queen, this was the norm she appealed to. Women could do things; they just had to prove they were Not Like Other Girls. By Elizabeth's time things were already changing: it was the Reformation that switched the ideal to marriage, & the Enlightenment that divorced femininity from reason, aggression & public life.

For more on this topic, read Katherine Hager's article "Endowed With Manly Courage: Medieval Perceptions of Women in Combat" on women who transcended gender to occupy a liminal space as warrior/virgin/saint.

So, tip #2: remember that for medieval women, wife and mother wasn't the ideal, virgin saint was the ideal. By proving yourself "not like other girls" you could gain significant autonomy & freedom.

Finally a bonus tip: if writing about medieval women, be sure to read writing on women's issues from the time so as to understand the terms in which these women spoke about & defended their ambitions. Start with Christine de Pisan.

I learned all this doing the reading for WATCHERS OF OUTREMER, my series of historical fantasy novels set in the medieval crusader states, which were dominated by strong medieval women! Book 5, THE HOUSE OF MOURNING (forthcoming 2023) will focus, to a greater extent than any other novel I've ever yet read or written, on the experience of women during the crusades - as warriors, captives, and political leaders. I can't wait to share it with you all!

[thecodingtrail]

What is The Coding Trail (TCT)?

The Coding Trail is a coding platform for children aged 6 to 16. Parents are provided with a single platform with a variety of multiple Coding courses with different age levels that cater to the child's tech development.

[simplestudentplanning]

100 Things To Do Instead Of Doom-Scrolling Through Social Media

Read a book.

Write in a journal.

Learn to cook a new recipe.

Practice a musical instrument.

Start a DIY project.

Draw or paint.

Learn a new language.

Do a puzzle.

Exercise or do yoga.

Listen to a podcast.

Watch a documentary.

Play a board game.

Try a new workout routine.

Meditate.

Start a garden.

Plan a future trip.

Volunteer online.

Write a letter to a friend or family member.

Learn to knit or crochet.

Take online courses.

Practice photography.

Organize your closet.

Play video games.

Learn a magic trick.

Write a short story.

Create a vision board.

Make a playlist of your favorite songs.

Try a new hairstyle.

Experiment with makeup.

Learn to juggle.

Play a card game.

Do a home workout challenge.

Explore virtual museums or art galleries.

Do a digital detox day.

Learn calligraphy.

Rearrange your furniture.

Create a scrapbook.

Learn to play chess.

Write and perform a song.

Practice mindfulness.

Learn origami.

Plan a themed dinner night.

Do a home spa day.

Learn to code.

Play a musical instrument.

Build a blanket fort.

Take online dance lessons.

Research and try a new type of tea.

Learn about astronomy and stargaze.

Try a new board game.

Create a podcast.

Learn to solve a Rubik's Cube.

Start a blog.

Make homemade candles.

Research your family tree.

Practice a new type of art (e.g., watercolor, sculpture).

Learn to speed-read.

Write a poem.

Make a list of personal goals.

Learn to play a new card game.

Create a budget.

Build a puzzle or Lego set.

Learn to identify constellations.

Try a new fitness class online.

Make homemade pizza.

Experiment with DIY face masks.

Learn about a historical event.

Create a bucket list.

Learn to tie different knots.

Try a new type of workout (e.g., Pilates, kickboxing).

Create digital art.

Plan a themed movie marathon.

Learn to juggle.

Explore a new genre of music.

Write a letter to your future self.

Take up a new hobby (e.g., birdwatching, geocaching).

Research and try a new type of cuisine.

Make homemade ice cream.

Practice deep breathing exercises.

Create a photo album.

Try a new type of dance.

Write and perform a short play.

Learn to play a new board game.

Take a virtual tour of a historical site.

Make a time capsule.

Learn about different types of architecture.

Plan a virtual game night with friends.

Write and illustrate a children's book.

Try a new form of exercise (e.g., HIIT, Zumba).

Learn about different types of plants.

Create a DIY home decor project.

Plan a themed picnic at home.

Research and try a new type of dessert.

Practice positive affirmations.

Try a new type of puzzle (e.g., crosswords, Sudoku).

Learn about different types of birds.

Experiment with DIY skincare products.

Take up a new form of art (e.g., pottery, glassblowing).

Create a list of things you're grateful for.

Learn about a new culture.

[packsvlog]

𓈒ㅤׂㅤ ✎ ° 𝐖𝐇𝐄𝐍 𝐈 𝐊𝐈𝐒𝐒𝐄𝐃 𝐓𝐇𝐄 𝐓𝐄𝐀𝐂𝐇𝐄𝐑 ! ࣪₊ 𐙚

✶ 𝐬𝐮𝐦𝐦𝐚𝐫𝐲: being a kindergarten teacher is something you excel at, you even have two students you treat as if they were your own. not that they mind your endless devotion, much less do their dad, 𝐧𝐚𝐧𝐚𝐦𝐢 𝐤𝐞𝐧𝐭𝐨, if you could spare some attention to him as well.

✶ 𝐚. 𝐧𝐨𝐭𝐞: papamin!!!!!!! honestly i love papamin so much, i wish i could make that man a daddy. while on the topic, nanami is girl dad code, but for the plot he is sukuna’s and yuuji’s dad. also i loved writing sukuna as a baby, he is such a menace, he definitely was that kid who bite everyone. just posting this because i can’t wait till i post the series i’m making, i had to do something before. divider by: @cafekitsune

✶ 𝐬𝐲𝐥𝐥𝐚𝐛𝐮𝐬: pure fluff / ooc!sukuna / reader has no gender / no curse!au / modern!au / mention of death and grief (minor character)

✶ 𝐰𝐨𝐫𝐝 𝐜𝐨𝐮𝐧𝐭: 3.7k

Yuuji thinks you are his princess, and you let him play with the wood horses and gallops around your desk, sometimes you even play pretend with him, accepting the roses he plucks from the school’s garden and sharing your sandwiches with him. He loves you very dearly, it’s not a secret he keeps that you are his favorite teacher, but it is yours that he is one of your favorites as well.

Now Sukuna, his twin brother, is a whole story. The two and a half years old siblings can be perceived as the perfect opposites, because Yuuji is adorable and expressive in good ways, and Sukuna tries to bite your ankles whenever you move near him sitting on the floor. His sharp teeth are always on showcase by his little smirk, he is a menace.

You know Sukuna might sometimes dislike you, not because you have done him terrible wrong, au contrarie, you have been a good teacher, a good human! He tries to grab your hair with his tiny fists and you put him in your lap quickly, staring at him with a cute smile, he thinks you are encouraging him to leave you bald but he ends up not caring anymore, and decides to snuggle against you and sleep. Only to wake up later with a bite on your wrist.

It’s love for your profession and for the children that you don’t report any of this to the superiors or his parent, you think hopefully that you can change his ways, make him better. It does work, credits be given, he used to be worse! He used to bite the other students, now his teeth are all over your and, unfortunately, his twin.

It’s something you try your best to control, gods be good, Yuuji only whines before slapping his brother’s head, and then Sukuna cries and comes to you. You open your arms and again, he is biting you.

“Ow, Kuna!” You move his head away from your skin. “What do you eat to have such sharp teeth, hm?”

He doesn’t answer you, his big eyes are filled with tears and he is wiggling towards any skin of yours to sink his canines.

“C’mere.” You grab him and adjust the baby in your hips, before moving towards the box filled with toys and grabbing a plastic one, you take it to the class bathroom and wash it, while Sukuna sits on the balcony, staring at you with his sad puppy eyes. “You are so cute, y’know that, right?” He nods, which takes you by surprise. “You can not keep biting me anymore, Sukuna, you get this?”

As expected, Sukuna doesn’t answer this time. He only gets what he wants.

“But let’s make a deal, you don’t bite me or Yuuji, you bite this whenever you feel like it, hm?”

Sukuna is not supposed to be with pacifiers anymore, something requested by his parent and passed to you through your boss. So it’s a little secret to let him have the blue whale in his mouth, he bites the thing so deeply that by the end of the week, you have to change it for a red rubber duck.

It’s keeps going like this for a couple more days until you notice the progress being made, Sukuna always has the toy by his gripping hands or in his pockets, and whenever he falls to the ground or gets pushed by a classmate, his little eyebrows crunch into an angry face. You think he is going to jump the kid or run at you and be a little vampire, but instead he grabs his toy and starts to violently munch on it.

It’s adorable, it makes you want to eat him.

But you noticed, obviously you did, how Sukuna has anger issues, and being a baby he has no idea how to control the anger but to externalize it with violence, and you gave him a escape plan. Now, he isn’t so angry anymore, sometimes he just squeezes the little toy, he also doesn’t spend his time with only you or his brother, he makes some new friends such as little Uraume, who follows Sukuna around and both keep sharing their lunches.

You do find one more problem arising, anytime Ijichi, who you learn is their butler, comes to pick the boys, Sukuna cries desperate for having to return his toy. You tried to let him have but the man refuses and your superior reprimanded you once, after catching you trying to give it. The next day, you notice quickly that Yuuji and Sukuna both have little red teeth marks on their arms.

You sigh desperate.

After class is over, few days later, Ijichi is late for the pickup, so you sat both Sukuna (sucking his little toy) and Yuuji (talking your ear off) down. They stop what both were doing and stare at you, one with pure sparkling eyes and the other with a raising eyebrow. You laugh at that.

“My darling cherubs, we need to talk.” You sit on the floor. “Kuna, you are not allowed to keep biting your brother, you know that. And you can’t bite him as well, Yuuji. You have to go to your papa, okay?”

The little one nods at you.

“Sukuna, honey, you can’t bring the duck home, we tried. But you can find another one to bite, hm?” He doesn’t answer, of course, he is two years he is not going on a quest for a rubber toy. “I’ll talk to Ijichi-san, for you, okay buddy?”

It takes you by surprise when Sukuna gets up and moves to sit on your lap, snuggling his face to your chest. When your arms go to close, Yuuji follows his twin and sits on you as well.

“Thank you, sensei.” Kuna’s little voice melts your heart even more, you hug them back instantly.

“I’ll do anything for the both of you.”

You don’t notice the presence behind you, or the fact that it’s been there since you sat down, and payed attention to everything you said, but mostly by how Sukuna went for you instantly and thanked you. The little bundle of angriness has his eyes closed, but his brother stares behind your shoulder and gasp, wiggling out of your touch and running towards the door.

“PAPA!” Yuuji screams making your heart jump. You turn back, staring at the scene. A tall blonde man, with formal clothes, kneels to the floor before opening his arms and grabbing Yuuji on his arms, kissing the pink hair of his baby.

You have heard the gossips towards the twins’s father, how exceptionally good looking he is, most charming and polite man anyone has ever seen or meet. And that he is single.

Of course, because of Ijichi being the one to bring and get the boys and the first teacher-parents’s meeting of the year being in just a few weeks, you haven’t met the man yet, but he here is, Nanami Kento, in all his glory.

You get up with Sukuna at the same time Nanami get up with Yuuji, and you notice right away that in his other hand he holds a bouquet of purple tulips.

“Look, Kuna, your papa is here.” You bounce the sleepy head on your lap, he opens his eyes before smiling a bit, and closing it again. “I think he got pretty tired after the playground today.” You laugh quietly before staring at the man, his eyes on his baby, a small smile on his face as well.

“Pleasure to meet you, Y/n-sensei.” It’s the first thing he says to you, his voice shaking your smile for a bit. “I’m sorry about being so late, the driver got busy with some stuff, so I had to come. I got you this, for the inconvenience.” He presents you the flowers, in your mind, he was going on a date, never in millions thoughts you would expect this.

“Oh, oh! Thank you, they are beautiful.” With your spare hand, you grab the flowers and smell them, smiling sweetly.

“I told papa you like those, sensei.” Yuuji says, with his eyes closed and large smile.

“Thank you, Yuuji, my charming knight.” You put the flowers on your desk before giving a pat to his head. “And thank you again, Mr. Nanami.”

“Again, I’m very sorry. But now, I think it’s time we go, right boys? Your sensei deserves to rest after the two of you.” Nanami grabs Sukuna from your arms, the boy open his eyes again for a second before falling into slumber. You help the male grabbing the twins backpacks and both of you move towards the parking lot.

When Nanami puts the babies in their seats, he turns to you grabbing the bags.

“Thank you for being their teacher, is not an easy job, but they both really like you.”

“It’s my pleasure, really. Sukuna and Yuuji make this job really worth it.” You answer sincerely, the door to the car is closed and the boys can’t hear you.

“I heard what you said to them, about the bites. I’ll get the toys for Sukuna, thank you for caring for him.“ Before Nanami gets into his car, he stops and turns back at you. “Would you need a ride? After all we did kept you here for longer than anticipated.”

You stare at the sky, dark clouds already reaching the sunset orange and pink, even the moon hangs more brightly than ever. You are inclined to accept, but you hold yourself.

“I would, any other day, but there is so much I have to do in the classroom and to grade the kid’s exercises, but thank you for the offer, Mr. Nanami.” You both exchange a smile before you wave at the awake Yuuji, staring at you by the window.

The next day and the others after, surprising everyone, Nanami is the one picking his sons up. His back is always tainted with the sunset from the corridor’s widows whenever he stays at the door, and a dozens of mothers and staff keep staring at him, searching for any opening to create a conversation. You are putting Yuuji’s bear beanie on, when you hear your boss asking Nanami for coffee with the excuse of talking about the boys, you laugh silently before grabbing the twins’s hands and moving towards their dad, giving an scape for him to move away from the woman.

“No need for the coffee ‘date’, the parents reunion with the teachers is this saturday, we all can talk there.” You say a bit loud, enough to send the message across, and all those people ready to jump at the blonde male move away.

“Thank you.” He whispers before grabbing the boys in his arms. “No ride today?”

Every once in a while, after the first time meeting Nanami, he has been asking you if you need a ride, and with a strength you don’t know where came from, you refuse nicely. It’s not that you don’t want, would be stupid to, it’s more for the fact that he is dreamily, you wouldn’t be any better than those who salivate at the sight of him. You could be worse.

“Not today, Mr. Nanami, these two made a mess in the bathroom, although I think Sukuna has a talent for arts, he painted the walls really well.”

“God, you’re joking.” You sign no with your head and the man sighs. “I’ll ask for the price of repair, please don’t worry about it, it’s my kids, I’ll fix it.”

“No need! Seriously, I believe just water and soap and it’ll be fine.” You grab Sukuna’s cheeks and he hides his face in his dad’s chest. “But if not, it’ll be a cute memory in the future, when they move classes or school.”

“I’m not going anywhere.” Yuuji squirms. “We’re staying with you forever, right Papa?”

Oh.

“C’mon, buddy, time to go home.” Nanami laughs his answer, and you move with them, holding their backpacks. It’s a little ritual now, you could say.

You wave them goodbye and return home that day with a slight tremble in your fingers, after this year most likely you wouldn’t see them ever again, and that fact made you terribly sad. You would miss pealing the fruits for Yuuji and being gifted half of it, would miss even the mark bites of Sukuna little mouth, even though he hadn’t been a menace in a long time now.

Admitting, you would miss Nanami and his lovely smile, the way he would ask you for a ride anytime. You should accept it, you know, but could you move on from this little crush you’ve been harboring, if you are meant to never see him again? Doubt it, no one can get over the Nanami Kento.

You sleep with those thoughts, these little moments you had with him and the sweet and gentle and chaotic memories you had with the twins. It’s a bittersweet feeling teachers have, you should be used to it by now, dealing with the fact that the babies don’t stay babies forever, only in your heart and memories. But there is something in that little family that shakes your core, that moves your mind and warms your heart, something that scares you.

Saturday comes but your anxiety stays. You decorate your classroom with a large table filled with charcuterie boards and juices, there is also paintings of the kids hanging by the walls, presents to give to their parents. All of them are on the corridor, you call for one couple after the other, for the intimacy of talking about their children.

You notice how each kid can resemble their parents in a comical and adorable way. Megumi, for example, who has his mom messy hair but his dad scowl, Nobara is energetic like her mom, and sensitive like her daddy who cries when gifted her painting.

You also see how they can be with their babies. Toge’s parents who are elated with your hand signs, and how you explain that you learned it in two months for the boy and has been using and teaching it in your class, for the other students to communicate with the him. Maki’s and Mai’s parents are stiff and bored, and you take notice of that to pay more attention to the girls, help if needed anything.

You do your job perfectly, but your eyes always go searching for a blonde man whenever you go call the next parents. He is not there yet, and you wonder if he won’t come. Maybe job related, maybe he forgot, you try to not be sad.

When you are taking Nanako’s and Mimiko’s fathers to the door, waving them goodbye, you catch sight of a man with beige suit and blue shirt, in his hands another bouquet of purple tulips.

“I told you we should have given something.” Mr. Geto whispers while staring at Nanami.

“Love, that’s not a ‘Thank you for being my kid’s teacher’ bouquet.” Mr. Satoru answers with a smirk your way.

“I miss when you would give me flowers.” Geto answers, his voice low because they are already by the end of the corridor.

“Huh? I gave your flowers last week?!”

Nanami and you are staring at the couple, until their figures disappear and both of you stare at each-other, smiling fondly at first and then laughing a second later.

“I’m guessing these are for me?” You ask when you move inside the classroom, Nanami following behind. You turn to him, and he nods, giving you the bouquet, perfumed perfectly. “Thank you.”

“I’m sorry I was late, the boys wanted to come as well but I had to keep them occupied and tired.” You nod laughing, before pointing at the table in front of your desk, putting your flowers there, he sits and you move towards the wall, grabbing two drawings.

“These are for you.” You sit by his side instead of in front of the man and give him the papers, he has a sweet smile while admiring the drawings. “I asked the class to draw their family, hasn’t had the time to check yet, but I hope it’s better than the one I saw earlier: the girl draw only her sister and their cats.”

“It’s perfect, don’t worry.” Nanami has his eyes on both drawings, side by side. You can tell which is which by the colors and traces, but none other, the art is basically the same. “This is Ijichi in the car, how cute.” Nanami points at the figure in a black suit driving a car besides the house in both paintings. You stares confused at the fifth stick person, besides Nanami and the twins. “Is that…?”

“I think so…” Your hands move to your mouth, hiding your growing smile when you notice characteristics in it that resembles you, specially a rubber duck in your hands, in Sukuna’s drawing. “I’m flattered they consider me family.”

“They are not wrong.” Nanami stares at you now. “That day we meet, you were helping them with one thing I had no idea how.” He moves the drawing to your desk. “I’m not their biological father, don’t know if you know that.” You don’t, so you keep yourself quiet and let him speak. “I was their godfather, been friends with their dad ever since we were little. Itadori Jin, great guy, that’s where they inherited that beautiful pink hair.” Nanami has a sad smile in his lips that break your heart. “He and his wife died in a car crash, first date since the birth of the babies, just two months old. Their grandfather was adamant on keeping them, but he realized he needed my help, so he let me adopt them officially.”

He sighs before grabbing his thighs.

“Recently I told them about their parents, that’s why Sukuna started the biting, his sorrow is physically showing. I tried to help but didn’t knew how, but you did, you handled it better than I could.”

“You are still a great father, they might not have come from you, but they are yours. And you did helped them, Sukuna might have received some slaps from Yuuji, but Yuu always hugged him whenever it became too much, and he listened to me instead of throwing a tantrum.” You hold his arm for a second before removing your hand. “You are raising them very well, Mr. Nanami, it’s not easy to be a parent, but you are doing fine.”

“Thank you, and please call me Kento.” It’s not professional, but you nod.

“Okay… Kento.” You whisper his name like a secret, and you wonder if you feel right, but it tastes like honey in your tongue. It’s just a second of both of you staring at each-other for his eyes to move to your lips. You should move back, but you don’t, nor you can. Instead, your eyes go to his pink lips as well. “We should wrap this up, it’s late, right?”

“Yeah, we should.” But none of you move, eyes moving to eyes and lips, over and over, you wet your lips, he groans and lunges at you. You accept him easily, moving your hands to circle his broad shoulders and touch his neck, while his large hands take your waist.

You shouldn’t be doing this, but it feels wrong to not be doing it. So you allow yourself to be kissed hungrily by Kento.

There is three knocks on the door before you both jump apart, your boss, the principal, makes her way in, eyes shinning at seeing Nanami.

“Mr. Nanami, so good to see you here! Would you like to come and have that coffee we were taking about some days ago?”

Kento looks at you, his hair is a little messy and his mouth is red, he looks even more ravishing than before. You cough awkward, grabbing your flowers, bag and the twins’s drawing before moving to his side.

“I’m so sorry, Principal, but Mr. Nanami is giving me a ride home.” The man has his hands on your back in an instant, moving both of you out of the class. “I see you monday.”

The two of you leave the baffled woman behind, Nanami has an eternal perfect smile charming his face, making you want to kiss him even more. Which you do, when he closes the door he opened for you, and enters the car you kiss him, when you both stop at a red light you kiss him. And when he let you at your house, his hands again in your back, he kisses you.

You are too tempted to bring him inside, even more to have your way with him, but he beats you to it, asking you to go out with him the next day.

It’s just the beginning of your blooming relationship, flowers every week, restaurant dates, kisses at every opportunity. You both keep yourselves occupied and yet reserved. He gives you rides home after most staff and students are gone, the boys happily talking with you all the way to your house, and he leaves you at your door with a peck the babies don’t see.

It’s at your last day of the year, all your students glued to you, crying red faces you promise them to always be there when needed, giving the parents your personal number, they happily accept it. Yuuji and Sukuna are the most devasted, their little hands keep you from moving far away from them, and when Nanami comes to pick them up, Sukuna cries together with his brother, taking you by surprise.

You tell them bye and run to your apartment, where you prepare a whole meal and dress nicely, soon you hear the door knocking. When you open, it takes three stunned seconds before two little babies are running to your arms, screaming happily to see you.

“Now it’s a good time to say, Y/n is staying in our lives.” Nanami says while hugging you, both boys in your arms holding you as well.

“Forever?” Sukuna asks, Yuuji stares at you waiting for the answer.

“Yes, my cherubs, forever.”