#cms architecture

[dmsinfosystem]

Learn to build a Headless CMS Architecture by which you can easily start building a modern and scalable content infrastructure today.

[blackwing3w]

[emberfrostlovesloki]

Emily + Poetry

All photo credits at the end

Criminal Minds Characters + Virtues - Emily and Humility

"The greater the artist, the greater the doubt. Perfect confidence is granted to the less talented as a consolation prize" - Robert Hughes

I wish Emily's character had been more fleshed out, especially because of how smart she is. She has such a talent with all of her language skills that are only touched on a few times. Really the whole team is cheated this because Spencer is labeled "Smart Boy Genius" which is deserved, but he's not the only smart one on the team. Emily is a gem, pressed so hard she became a diamond and I adore her for her strength and smarts and how humble she stays the whole show.

Other Virtue Mood Boards: Aaron + Poetry, Rossi + Poetry, Spencer + Poetry, Derek + Poetry, JJ + Poetry

Text Break Banner by @cafekitsune

Want to be added to my tag list? Please check out this post (linked) 

Want to send in a request? Please check out this post, CM Request Post (linked)

Photo Credits

Top: Left (@shakespearesdaughters) Center (@fedyasmoyalyubov) Right (@sitkowski)

Middle: Left (@academic-vampire) Center (@emilyinsuits) Right (@unrealityliminal)

Bottom: Left (@kaijuno) Center (@chainsawjoy) Right (@letsbelonelytogetherr)

[brutallyquiet]

Instagram: brutallystupid

[britonbritonsblog]

Dozens of children go to bed hungry each night, their growth stunted, their learning impaired-all for lack of a basic human need: food

Please donate for children 🙏 http://www.paypal.me/abdallahsalam100/

[manavkapoor]

Why Headless Laravel CMS is Taking Over Traditional Web Development

Hey folks! 🚀 If you’ve been keeping up with web development trends, you’ve probably heard the buzz about headless Laravel CMS. It’s revolutionizing how we build and manage websites, leaving traditional CMS platforms like WordPress and Drupal in the dust. But why? Let’s dive in and explore why businesses and developers are making the switch—spoiler alert: it’s all about flexibility, speed, and scalability!

Understanding Headless Laravel CMS and Its Growing Popularity

A headless CMS isn’t some futuristic tech—it’s a smarter way to manage content. Unlike traditional CMS platforms that bundle the frontend and backend together, a headless CMS decouples them, giving developers the freedom to use any frontend framework while Laravel handles the backend like a pro.

What is a Headless CMS and How Does It Work?

Imagine a restaurant where the kitchen (backend) and dining area (frontend) operate independently. 🍽️ The kitchen prepares the food (content), and the waitstaff (APIs) deliver it to any dining setup—be it a food truck, rooftop café, or home delivery. That’s how a headless CMS works! It stores and manages content, then delivers it via APIs to any device or platform—websites, mobile apps, smartwatches, you name it.

Why Laravel is Perfect for a Headless CMS

Laravel isn’t just another PHP framework—it’s a powerhouse for API-driven development. With built-in support for RESTful and GraphQL APIs, Eloquent ORM for smooth database interactions, and a robust ecosystem, it’s no wonder Laravel is the top pick for headless CMS setups.

Headless Laravel CMS vs. Traditional CMS Solutions

Traditional CMS platforms like WordPress are great for simple websites, but they struggle with scalability and multi-channel content delivery. A headless Laravel CMS, on the other hand, offers:

No frontend restrictions (use React, Vue.js, or even a mobile app).

Better performance (no bloated themes or plugins slowing things down).

Future-proof flexibility (adapt to new tech without overhauling your backend).

Benefits of Using a Headless CMS with Laravel

Enhanced Performance and Scalability

Did you know? Websites using headless CMS architectures load up to 50% faster than traditional setups. 🏎️ By separating the frontend and backend, Laravel ensures your content is delivered lightning-fast, whether you’re serving 100 or 100,000 users.

Multi-Platform Content Delivery

With a headless Laravel CMS, your content isn’t tied to a single website. Publish once, and distribute everywhere—web, mobile apps, IoT devices, even digital billboards! Companies like Netflix and Spotify use headless CMS to deliver seamless experiences across platforms.

Improved Security and Backend Control

Traditional CMS platforms are hacker magnets (looking at you, WordPress plugins!). A headless Laravel CMS reduces vulnerabilities by:

Limiting exposure (no public-facing admin panel).

Using Laravel’s built-in security (CSRF protection, encryption).

Offering granular API access control.

Key Technologies Powering Headless Laravel CMS

RESTful and GraphQL APIs in Laravel CMS

Laravel makes API development a breeze. Whether you prefer REST (simple and structured) or GraphQL (flexible and efficient), Laravel’s got you covered. Fun fact: GraphQL can reduce API payloads by up to 70%, making your apps faster and more efficient.

Integrating Laravel CMS with JavaScript Frontend Frameworks

Pairing Laravel with React, Vue.js, or Next.js is like peanut butter and jelly—perfect together! 🥪 Frontend frameworks handle the UI, while Laravel manages data securely in the background. Many Laravel web development companies leverage this combo for high-performance apps.

Database and Storage Options for Headless Laravel CMS

Laravel plays nice with MySQL, PostgreSQL, MongoDB, and even cloud storage like AWS S3. Need to scale? No problem. Laravel’s database abstraction ensures smooth performance, whether you’re running a blog or a global e-commerce site.

Use Cases and Real-World Applications of Headless Laravel CMS

E-Commerce and Headless Laravel CMS

E-commerce giants love headless CMS for its agility. Imagine updating product listings once and seeing changes reflected instantly on your website, mobile app, and marketplace integrations. Companies like Nike and Adidas use headless setups for seamless shopping experiences.

Content-Heavy Websites and Laravel Headless CMS

News portals and media sites thrive with headless Laravel CMS. Why? Because journalists can publish content via a streamlined backend, while developers use modern frameworks to create dynamic, fast-loading frontends.

API-Driven Web and Mobile Applications

From fitness apps to banking platforms, headless Laravel CMS ensures real-time data sync across devices. No more clunky updates—just smooth, consistent user experiences.

Challenges and Best Practices for Headless Laravel CMS

Managing API Requests Efficiently

Too many API calls can slow things down. Solution? Caching and webhooks. Laravel’s caching mechanisms (Redis, Memcached) and event-driven webhooks keep performance snappy.

Handling SEO in a Headless Laravel CMS Setup

SEO isn’t dead—it’s just different! Use server-side rendering (SSR) with Next.js or Nuxt.js, and leverage Laravel’s meta-tag management tools to keep search engines happy.

Ensuring Smooth Frontend and Backend Communication

Clear API documentation and webhook integrations are key. A well-structured Laravel backend paired with a modular frontend ensures seamless updates and maintenance.

Final Thoughts

Headless Laravel CMS isn’t just a trend—it’s the future. With better performance, unmatched flexibility, and ironclad security, it’s no surprise that Laravel development companies are leading the charge. Whether you’re building an e-commerce platform, a content hub, or a multi-platform app, going headless with Laravel is a game-changer.

Key Takeaways

Headless Laravel CMS = Speed + Flexibility 🚀

API-first architecture = Content everywhere 📱💻

Security and scalability built-in 🔒

Frequently Asked Questions (FAQs)

1. What is the difference between a traditional CMS and a headless CMS?

A traditional CMS (like WordPress) combines the backend (content management) and frontend (display) in one system. A headless CMS decouples them, allowing content to be delivered via APIs to any frontend—websites, apps, or even smart devices. This offers greater flexibility and performance.

2. Why should I use Laravel for a headless CMS?

Laravel’s robust API support, security features, and scalability make it ideal for headless CMS setups. Its ecosystem (including tools like Laravel Sanctum for API auth) simplifies development, making it a top choice for Laravel web development services.

3. Can I integrate Laravel’s headless CMS with React or Vue.js?

Absolutely! Laravel works seamlessly with JavaScript frameworks like React, Vue.js, and Next.js. The backend serves content via APIs, while the frontend framework handles the UI, creating a fast, dynamic user experience.

4. How does a headless CMS improve website performance?

By separating the frontend and backend, a headless CMS reduces server load and eliminates bloated themes/plugins. Content is delivered via optimized APIs, resulting in faster load times and better scalability.

5. Is SEO more challenging in a headless CMS setup?

Not if you do it right! Use server-side rendering (SSR) with frameworks like Next.js, implement proper meta tags, and leverage Laravel’s SEO tools. Many headless CMS sites rank just as well—or better—than traditional ones.

There you have it, folks! 🎉 Headless Laravel CMS is reshaping web development, and now you know why. Ready to make the switch?

[olivergisttv]

Why You Should Use Headless CMS for Speed

Introduction to Headless CMS In a world where users want everything instantly, your website’s speed can literally make or break your business. Ever clicked on a slow-loading page and just bailed? Yep, so has everyone else. That’s why speed isn’t just a perk—it’s a priority. And one of the smartest ways to turbocharge your site’s performance is by switching to a Headless CMS. Let’s dive into how…

[thebatgurrl]

Across the Cedar River we Go

[marketxcel]

Unleashing the Future of E-Commerce: The Rise of Headless Commerce

Dive into the dynamic landscape of E-Commerce with our latest blog. Explore the disruptive potential of Headless Commerce and discover how it's reshaping the online shopping experience, unlocking unprecedented flexibility, and setting the stage for the future of digital retail.

[dmsinfosystem]

Building a Headless CMS Architecture: A Comprehensive Guide

In the ever-evolving world of web development, the Headless CMS architecture has emerged as a popular solution for building websites and applications. In this article, we'll explore what a Headless CMS is, why it's gaining popularity, and how you can build a Headless CMS architecture with a Hook to enhance its functionality.

What is a Headless CMS? 

A headless CMS is a content management system that doesn't control the front-end presentation layer but offers a content repository, API, and backend system for managing content. Unlike traditional CMS systems, a Headless CMS separates content management from content delivery, allowing developers to build custom front-end experiences using the API and tools of their choice.

Why is Headless CMS gaining popularity?

Headless CMS is gaining popularity for several reasons, including:

Flexibility:

With a Headless CMS, developers have complete control over the presentation layer and can use any technology they prefer to build custom front-end experiences. This flexibility allows developers to create unique user experiences and enables faster development times.

Scalability:

Headless CMS is highly scalable and can handle large amounts of content and traffic without affecting performance. The API-driven approach also allows developers to build applications easily scaled horizontally.

Security:

Headless CMS architecture is more secure than traditional CMS systems as it doesn't expose the back-end system to the internet, reducing the risk of attacks and data breaches.

Cost-Effectiveness:

Headless CMS systems can be more cost-effective than traditional CMS systems as they require fewer resources and can be hosted on scalable cloud platforms.

How to Build a Headless CMS Architecture?

Building a Headless CMS architecture can seem daunting, but it can be broken down into several key steps:

Step 1: Choose the Right CMS Platform

The first step in building a Headless CMS architecture is to choose the right CMS platform. There are several popular Headless CMS platforms available, including Strapi, Contentful, and Sanity. Every platform has different benefits and drawbacks, therefore it's important to assess each choice in light of your particular needs.

Step 2: Define Your Content Model

Determining your content model comes after selecting your CMS platform. The types of content you'll be managing, the attributes that make up each content type, and the connections between various content categories are all defined by a content model.

Step 3: Create Your Content

The next thing to do after establishing your content model is to start producing content. This can include text, images, videos, and any other media types you'll be managing in your Headless CMS.

Step 4: Set Up Your API 

The API is the backbone of a Headless CMS architecture and allows developers to access and manipulate content from the CMS. Setting up your API involves configuring your CMS platform to expose your content through a REST or GraphQL API.

Step 5: Build Your Front-End Application

The final step is to create your front-end application after your API is established. This involves using the API to fetch content from the CMS and display it on your website or application. Your front-end application's technology selection is up to you, allowing you to create a unique user experience that suits your unique demands.

Using a Hook to Enhance Your Headless CMS Architecture

While building a Headless CMS architecture is relatively straightforward, you can enhance its functionality using a Hook. A Hook is a piece of code that allows you to modify or extend the behaviour of a CMS platform. Hooks can be used to perform a variety of tasks, including:

Integrating with third-party services: 

Hooks can be used to integrate your Headless CMS with third-party services, such as analytics.

Modifying content:

Before the content is transmitted to the front-end application or saved to the CMS, hooks can be used to change it.

Extending functionality: 

Hooks can be used to extend the functionality of your Headless CMS by adding custom features or integrations.

To use a Hook, you'll need to identify the appropriate Hook point in your CMS platform and write custom code to execute. Hooks can be written in various programming languages, depending on your CMS platform.

Conclusion

Ultimately, creating a headless content management system design offers more flexibility, reliability, safety, and cost-effectiveness than conventional CMS systems. You need to choose the best CMS platform, establish your content model, produce your content, configure your API, and develop your front-end application before you can design a Headless CMS architecture. Using a Hook can also enhance the functionality of your Headless CMS architecture by allowing you to modify content, integrate with third-party services, and extend functionality. You can create a Headless CMS design that satisfies your particular requirements and offers a distinctive user experience by following these directions and using the power of Hooks.

[companyindianwebsite]

What is a Static Site CMS?

Introduction: Content management systems (CMS) are essential tools in the dynamic world of web development because it makes the creation and management of digital content easier. The emergence of Static Site CMS is an interesting development in the CMS space. This thorough guide will explain the idea, advantages, and uses of static site content management systems (CMS) and show how this…

[emberfrostlovesloki]

Rossi + Poetry

All photo credits at the end

Criminal Minds Characters + Virtues - Rossi and Temperance

“It is a queer thing. In a time of great need, when powerful leadership is demanded, the people—confused and excited—hear only the strident voices of the audacious, and refuse to listen to the voice of wisdom which, being wise, is temperate.” - Llyod C. Douglas

I think in modern times we think of temperance as teetotaling, but it's a quality not always about being sober. It is, to me, about moderation. Careful condiseration for oneself and one's friends. Rosse grows in his temperance exponentially in the show. His first episode shows him to be arrogant and reckless with others, but with time, the team becomes his family, he learns to moderate his behavior. I know some people clown on Rossi, but he is one of my favs.

Other Virtue Mood Boards: Aaron + Poetry, Penelope + Poetry, Emily + Poetry, Spencer + Poetry, Derek + Poetry, JJ + Poetry

Text Break Banner @cafekitsune

Top: Left (@kahvedebiyat) Center (@lukwata) Right (@piratecode)

Middle: Left (@sproutandroid) Center (@criminalmindsverse) Right (@aesthetic-otd)

Bottom: Left (@nighttime-moodlight) Center (@neonin3d) Right (@mcpirata)

[gnsparkebursa]

Lake 20 cm Beyaz PVC Süpürgelik

Kalinlik : 25 mm Yükseklik : 20 cm

#lakebeyazpvcsüpürgelik

#beyazlakepvcsüpürgelik

#20cmlakepvcsüpürgelik

#bursaparke

#paradorparke

#beyazlakesüpürgelik

#xlbeyazlakesüpürgelik

#otelrenovasyon

#ofisrenovasyon

#evdekorasyon

#kaferenovasyon

#restaurantrenovasyon

#gnsparke

#extrayükseklakesüpürgelik

#beyazparkesüpürgelik

[lionofchaeronea]

Title: Rouen Cathedral in the Evening Artist: Claude Monet (French, 1840-1926) Date: 1894 Genre: architectural painting Movement: Impressionism Medium: oil on canvas Dimensions: 100.2 cm (39.4 in) high x 65.3 cm (25.7 in) wide Location: Pushkin Museum of Fine Arts, Moscow

[mariasont]

PART I: THE LADY OF SHALOTT

this is what it means to love in verse and violence

part I -> part II -> part III -> part IV -> part V

pairings: spencer reid x fem!reader warnings: dissociation, detachment, depictions of emotional numbness, exploration of unhealthy coping mechanism, obsessive thought patterns, situationship, canon-type cm violence wc: 1.7k

It feels blasphemous somehow, the serenity of your sleep while he quietly burns up in your atmosphere. Spencer watches anyway, the pain like a necessary liturgy, masochism dressed as ritual.

He thinks of Orpheus. The final glimpse. Desire’s ruinous price. You’re a figure behind glass, beautiful in its fragility, and he presses his longing against it like a handprint left on a window. It won’t hold.

It has to be safer like this. It’s the foundational premise, the condition, the contract he obsessively redraws in his head. You and him, whatever this is — it’s not a relationship. It’s too structured, carefully fenced in. No promises or permanence.

His breath briefly fogging your cold glass before inevitably fading away. 

Finite.

But his mind is disloyal to his efforts. It feeds him poetry at midnight, terrible beautiful things about staying, about softness, about wanting. He loathes it. He hates himself more for listening.

Loss is familiar to him. Predictable, even. The reaching, the missing, the grasping for things already halfway gone. Always phantoms. Always slipping. 

Better, then, to keep you preserved in a delicate status, sheltered, just outside the reach of the damage his presence seems destined to inflict. Because love, when it’s real, doesn’t survive contact with his hands. It’s a lesson he’s been forced to memorize in painful repetition.

There had been no reckless start with you. No heat-drunk declarations made in the haze of midnight or slurred confessions coaxed out by a bottle of wine.

Just something quieter. Slower. A gradual arrangement built on the architecture of sidelong glances and the language of proximity. It began in simplicity — how was your weekend? — and ended in confessions neither of you meant to give.

Until one day, without ceremony, vulnerability became habit. And intimacy, the kind that asked for nothing but the immediacy of bodies, was already there, waiting to be noticed.

Spencer understood that what he craved wasn’t emotional attachment. He didn’t pretend it was. It was physical. It was just sex. But not for the sake of lust or conquest or even pleasure. It was about what sex offered. The temporary illusion of closeness, the feeling of another person’s heat echoing back into him. Fingers skimming ribs, palms pressed to hips. It was a language that bypassed explanation.

He didn’t need to be known. He just needed to be felt. Needed the proof of another heartbeat beside his own.

He refocuses on your sleeping face, mouth tense like you’re fighting something behind your eyes. He’s grown disturbingly adept at interpreting your facial expressions, a proficiency he never consciously sought.

Usually, he leaves before these things become clear, out the door by two at the latest. Tonight, however, the neon glare of the clock on your wall — 2:56 — declares a harsh judgment.

Spencer knows, in some detached sense, he’s violating a fundamental rule of your agreement. 

So why isn’t he already halfway across town, cloistered behind familiar walls?

A simultaneous vibration splinters his thoughts. 

You wake with a sharp inhale. Spencer doesn’t flinch.

He reaches his phone first. One look at the screen is enough, but he answers anyway. Prentiss doesn’t waste words. We have a case. Briefing in thirty.

The call clicks off and he glances up — just in time to catch the look on his face. Sleep-blurred, yes, but also uncertain. Your eyes shift to the clock, then to him. Your lips part slightly, like they might form a question, but close again just as fast. 

He doesn’t offer an answer. You don’t demand one.

Neither of you spoke on the car ride over. It wasn’t uncomfortable exactly, just… quiet. Still meandering in that liminal place between sleep and awake, not able or willing to summon the energy for idle conversation. 

You had yawned at least four times in fifteen minutes. Spencer had counted without meaning to. He felt the same, half-aware and craving rest he couldn’t seem to find.

His exhaustion had been more pronounced than ever over the past couple months. At his own apartment, he sleeps. More or less. As well as anyone in his position could hope to. Enough hours, no interruptions outside of case hours.

He doesn’t wake to the sound of shouting or scraping medal anymore. A soft bed. No concrete slab. No cellmate shifting in the dark.

And still, he wakes up like he’s been emptied. Like rest is no longer a cure, just a placeholder.

He hasn’t admitted it out loud, but a theory’s been forming anyway. One that begins and ends with you.

The headaches are back too. He hadn’t missed them. They weren’t like before, thankfully, no blinding spikes of pain, no full-body shutdowns, but steady. Insistent. A dull pressure rooted behind his eyes, quietly leeching whatever thin layer of energy he manages to remain overnight.

Even the lights in the office feel hostile today, too bright and too cold. Fluorescence like a blade.

He blinks against it, resisting the childish urge to cover his face with his hands.

Instead, he squints toward the board. Three victims. All women. Early twenties.

“Three different methods. Drowning, strangulation, stabbing,” Rossi says, tapping the board with two fingers. “No clear pattern.”

Spencer frowns, eyes narrowing. “Unless that is the pattern,” he murmurs.

Emily looks over. “You think he’s varying methods on purpose?”

“It’s possible,” Spencer replies, suppressing a wince as the pressure in his skull pulses again. “Typically, yes, killers rely on routine or repetition. But each of these is too precise. Too controlled. If he were experimenting, we’d see hesitation, evidence of trial and error.”

“Could he be trying to confuse us? Distract us from the real motive?”

“That could be part of it,” he says, “but there could be something else. He could be assigning meaning to each method. A symbolic system. One we haven’t decoded yet.”

“So, he’s playing games,” You say grimly. Spencer almost reaches for you, just to soften the crease in your forehead. He stops himself.

Games. 

It lands wrong. He hopes that’s not what this is. He hopes the unsub isn’t clever, isn’t strategic, isn’t the type to leave messages behind like breadcrumbs, dragging them out just long enough to make it personal.

Spencer desperately needs this case to be clean. Not because simplicity implies ease, nor because brutality is diminished by brevity, but because he doesn’t possess the mental bandwidth to endure another protracted game of psychological chess.

He insists, adamantly, that it’s driven purely by morality, by justice, because every unanswered crime feels like a stain that seeps into his conscience.

But there’s another part of him that wonders if he’s simply worn down by impatience. If he wants this to be over so he can rest. Wants the luxury of collapsing into your warmth again, tucked behind the shield of excuses he’s been recycling since the start.

And yet, he’s not naive enough to believe rest will come after this.

There will be another case. Then another.

A carousel of grief dressed in new faces. He wonders, sometimes, where he’s supposed to draw the line. To quit before the work finishes hollowing him out completely.

Maybe then, he could allow himself to love you without conditions.

You would make a good wife. You would make a devastating home out of someone like him. Maybe there’s a version of this world, some other branch split clean at the moment he walked into the BAU, where you and him are just ordinary, happy, untouched by bureaucracy and regret.

Maybe.

But not here. Here, the air is dry, the grass brittle beneath his boots, and someone else’s ending waits in the dirt.

His attention flicks to a knot of wildflowers half-trampled by the path, their petals bruised beneath morning’s glare. They look like devotion offered too late. A gesture turned grotesque by where it landed.

She’s been placed, not dropped — the victim. That much is clear. Her body rests in the field, arms folded, face angled upward. Her hair spreads around her like a halo, washed-out gold against the soil. Despite the violence that ended her life, her face remains eerily serene. Mouth slightly open, as if paused mid-word.

“It’s strange, right? Like… the way she’s posed. It almost feels like he cared.” You glanced down, eyes catching on the blood-dark hole through her sternum. “Almost.”

His eyes trace the curve of her shoulder, the positioning of her hands.

“There’s a difference between cruelty and care,” he murmurs. “But I think some people forgot where the line is.”

Spencer crouches slowly, joints stiff with the cold. His gloved hands hover just above the victim’s frame, careful not to disturb the scene.

Why the effort? 

The arrangement suggests something close to tenderness, though the context makes that hard to stomach. Reverence and murder rarely coexist comfortably. Maybe it isn’t about the death at all. Maybe it’s about the preservation. An attempt to suspend something fleeting. Youth. Beauty. Innocence. As if holding her like this could capture forever what can’t naturally endure.

“Do you ever think about how we show up after the worst thing someone’s gone through? And then just… leave?”

He stands slowly, spine aching from crouching too long.

Your face tilts toward the wind and sun catches on a smudge near your jaw. His fingers reach for it this time, brushing over it before the texture of the glove registers.

He drops his hand.

“You had something there.” A pause. “And now you probably have something else.”

“It’s fine. I’ve had worse things on my face.”

“I really hope you mean frosting or face paint,” he mutters.

He knows what you meant. Semantics aside, he’d studied the evidence up close.

The joke had bought him time, but not much. You’d asked him something and he dodged it. Clockwork.

“Yeah. I think about it. Feels like patching bullet holes with band-aids,” he says finally. “Better than letting it bleed out though.”

“Sure.”

The word came out thin, like you didn’t really mean it. He didn’t respond — just watched as techs pass by, then started walking.

The drive back was quiet again. You were scrolling through case notes, thumb dragging lethargic circles over the pages, eyes vacant and half-present.

You never played music. He always gripped the wheel like he was expecting something to go wrong. 

Driving made him anxious. Watching you drive made him worse. You hit curbs like they were suggestions and got distracted by things like birds on telephone wires. He’d said once that riding with you felt like tempting fate on purpose. You laughed. 

You asked if he was okay somewhere near the overpass. He said yeah, quietly and kept his eyes on the road, didn’t trust his face not to betray the lie. That was enough of an answer.

The rest of the day bled out without resolution. By evening, you were both too tired to pretend the lack of leads didn’t matter. 

When you asked if he wanted to stay the night, he knew you expected a hesitation. A caveat. Technically, he wasn’t supposed to. It was another rule you both upheld — not overnights during cases. It was too complicated.

But his agreement came fast. He didn’t pause. Didn’t qualify. He should have. But Spencer’s rules bend with you, and lately, they’ve started to fold, orgami-thin and splitting at the creases.

You step back to let him in, barefoot, already half-undressed in the way you usually were after midnight. 

Spencer keeps his eyes open the whole time. It wasn’t necessarily about watching but more so remembering. If this was wrong, he needed to hold onto it tightly enough to justify the transgression.

Your mouth against his, your hands pulling him in, the curve of your throat, the shiver under his palm. All these pieces of proof he’d replay later, alone, dissecting memories in the silence of his apartment.

He’s not sure he’ll ever know what fragments of these stolen moments he’s allowed to believe in. 

He kisses your skin, fooling himself into believing it was sufficient, that passion could remain confined. 

But even tempered glass has its breaking point.

The mirror crack’d from side to side; / ‘The curse is come upon me,’ cried / The Lady of Shalott.

part II