fix: explora sequence

Author: sosumit001

app/explora/exploras/webassembly-tutorial/ch02-setting-developement-enviroment.mdx

@@ -1,5 +1,5 @@
 ---
-title: Setting Up Development Environment"
+title: Setting Up Development Environment
 publishedAt: "2025-07-03"
 summary: "Set up a robust Emscripten SDK and compiler toolchain step-by-step. Build and debug your first WebAssembly module without hassle or guesswork."
 image: "/images/javascript-frameworks.png"

app/explora/exploras/webassembly-tutorial/ch03-wasm-module.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Your First WebAssembly Module"
+title: Your First WebAssembly Module
 publishedAt: "2025-07-03"
 summary: "Build your first real WebAssembly module: compile C++ to wasm, avoid common pitfalls, and unlock blazing web app speed—step-by-step guide!"
 image: "/images/javascript-frameworks.png"

app/explora/exploras/webassembly-tutorial/ch04-js-wasm-integration.mdx

@@ -1,5 +1,5 @@
 ---
-title: "The Hidden Friction (and Big Rewards) of JS-WASM Integration"
+title: The Hidden Friction (and Big Rewards) of JS-WASM Integration
 publishedAt: "2025-07-03"
 summary: "The secrets of JavaScript and WebAssembly integration: efficient module loading, data marshaling, async patterns, and advanced interop tips for high-performance apps."
 image: "/images/javascript-frameworks.png"

app/explora/exploras/webassembly-tutorial/ch05-wasm-memory.mdx

@@ -1,5 +1,5 @@
 ---
-title: Out of Memory—and Out of Luck? WebAssembly Memory Management"
+title: Out of Memory—and Out of Luck? WebAssembly Memory Management
 publishedAt: "2025-07-03"
 summary: "WebAssembly-powered web app—once sleek and fast—starts misbehaving. Unexpected crashes, weird visual glitches, maybe even a cryptic “out of memory” error haunting your console. You scramble to debug, but nothing jumps out."
 image: "/images/javascript-frameworks.png"

app/explora/exploras/webassembly-tutorial/ch06-js-wasm-data-marshaling.mdx

@@ -1,5 +1,5 @@
 ---
-title: WebAssembly Advanced Data Types & Structures: Strings, Arrays, and the Serialization Nightmare"
+title: WebAssembly Advanced Data Types & Structures: Strings, Arrays, and the Serialization Nightmare
 publishedAt: "2025-07-03"
 summary: "Master passing complex data between JS and WebAssembly: strings, arrays, structs, and tips to avoid bugs and unlock blazing web app speed."
 image: "/images/javascript-frameworks.png"

app/explora/exploras/webassembly-tutorial/overview.mdx

@@ -1,23 +1,19 @@
 ---
-title: Learn WebAssembly: From Basics to Real-World Applications"
+title: Learn WebAssembly: From Basics to Real-World Applications
 publishedAt: "2025-07-03"
 summary: "Start from the fundamentals and progress through hands-on modules, JavaScript integration, memory management, advanced data handling, performance optimization, threading, and real-world projects."
 image: "/images/javascript-frameworks.png"
 ---
 
-Start with this: **WebAssembly is not another scripting language**. It’s a _portable, low-level bytecode_—think of it as a set of instructions so close to a computer’s native language that it can run at near-machine speeds. But unlike machine code, Wasm is designed to be safe, sandboxed, and universally compatible across browsers.
+**WebAssembly is not another scripting language**. It’s a _portable, low-level bytecode_—think of it as a set of instructions so close to a computer’s native language that it can run at near-machine speeds. But unlike machine code, Wasm is designed to be safe, sandboxed, and universally compatible across browsers.
 
 When you write code in languages like C, C++, or Rust, you can compile it into WebAssembly rather than to an operating system’s machine code. The output? A compact binary file (the `.wasm` file) that browsers can load and run alongside—or even instead of—JavaScript.
 
 But here’s the kicker: you don’t have to abandon JavaScript. WebAssembly is designed to complement it. They interact through a well-defined bridge, letting you delegate your web app’s heavy lifting to Wasm, while using JavaScript for DOM manipulation and higher-level orchestration.
 
-**Key Takeaway:**
-
-WebAssembly is a common binary format for running high-performance code, written in many languages, safely and efficiently _inside your browser_.
-
 ---
 
-## Why WebAssembly? Beyond the Buzz—The Real Performance Edge
+## Why WebAssembly?
 
 Let’s be honest. You’re probably thinking: _Is Wasm just hype? Can it really outperform JavaScript by that much?_ Here’s what most blogs gloss over:
 
@@ -76,7 +72,7 @@ Let’s break it down, step by step, minus the jargon.
 
 ---
 
-## Browser Support: No More "Coming Soon"
+## Browser Support
 
 This isn’t a science experiment or some “works in Chrome, but not Safari” scenario. As of now:
 
@@ -105,25 +101,7 @@ Devtools in every browser let you inspect Wasm modules, step through source maps
 
 The Wasm runtime is vigorously sandboxed, with no arbitrary disk or network access outside of what your JS environment gives it. Security researchers praise Wasm for “default safe-by-design”—a rarity in the web world.
 
----
-
-## Quickfire FAQ: Debunking Big Misconceptions
-
-**Q: Is Wasm only for heavy apps or games?**
-
-A: Nope. Any performance-critical task—or legacy code reuse—can benefit.
-
-**Q: Is learning WebAssembly hard?**
-
-A: If you’re comfortable with basic compilation and JS, you’re halfway there. Toolchains, examples, and docs have improved massively in recent years.
-
-**Q: Can I use Wasm without leaving JavaScript?**
-
-A: Absolutely. Most apps will remain a mix, using Wasm for speed and JS for “glue.”
-
----
-
-## Wrapping Up: Your First Step into WebAssembly
+## Your First Step into WebAssembly
 
 Here’s the bottom line: WebAssembly isn’t a distant future—it’s the quietly thriving power-up already reshaping the web’s limits. It gives you, the developer, a new toolset for building apps previously unthinkable for browsers.
 

app/explora/page.tsx

@@ -10,7 +10,12 @@ export const metadata: Metadata = {
 };
 
 const Page = () => {
-  const explorations = getExplorations();
+  const explorations = getExplorations().sort((a, b) => {
+    if (new Date(a.metadata.publishedAt) > new Date(b.metadata.publishedAt)) {
+      return -1;
+    }
+    return 1;
+  });
 
   return (
     <>