Forem: Othmane N.

Instantly Convert Figma Designs into Elementor Templates with AI

Othmane N. — Fri, 20 Jun 2025 17:13:43 +0000

🎉 Introducing Figmentor AI – Instantly Convert Figma Designs into Elementor Templates with AI

Stop wasting hours rebuilding your Figma designs in Elementor. Figmentor AI does it for you — automatically.

Hey Devs, Designers, and Builders,

If you've ever had to take a design from Figma and rebuild it manually in Elementor, you know how painful and repetitive it can be.

As a solo founder building websites for clients and agencies, I kept running into this same wall:
✅ Design done.
❌ Now rebuild it block-by-block in Elementor — again and again.

So I built something to fix that.

🚀 Meet Figmentor AI

Figmentor AI is a new tool that uses AI to turn Figma designs into ready-to-import Elementor templates — in seconds.

It's powered by our first AI model, Minimal, which detects layout structure and converts your design into clean Elementor JSON blocks.

No manual exporting.
No rebuilding sections.
No plugin hacks or workarounds.

Just drop your Figma file → get a fully structured Elementor layout.

🧠 Why Figmentor AI Exists

The gap between design and website is full of friction:

Designers want to move fast and stay creative
Developers are overloaded with repeated layout work
Freelancers and agencies lose time on manual conversion
Clients expect pixel-perfect implementation

Figmentor AI exists to eliminate that gap.
It gives you a fast, clean, and automated way to bridge the handoff between design and development.

✨ What Figmentor AI Can Do

Converts Figma files to Elementor-compatible templates
Uses AI to detect layout structure intelligently
Outputs clean, minimal JSON ready to import into WordPress
Designed for freelancers, agencies, and no-code users
Works with any Figma file, no setup needed

🔥 Use Case Scenarios

You’re a freelancer with multiple client projects and need to save time
You run an agency and want to remove dev bottlenecks in your workflow
You’re a designer who doesn’t want to touch Elementor again
You build landing pages fast and want AI to handle structure

🎁 Special Launch Offer

To celebrate the launch, you can try Figmentor AI with 30% OFF using the code:

FIGELAI

Try it here: https://figmentor.io

🧪 What’s Next?

This is just the beginning.

We're building more AI models and smarter layout detection to handle:

More complex sections (hero, testimonials, grids)
Responsive structure
Smart image and text mapping
Native integration with Figma plugin (coming soon)

We believe that AI should be your invisible assistant — and Figmentor AI is our first step in reshaping the way we turn designs into live websites.

💬 Feedback Wanted

We’re looking for:

Honest feedback from devs and designers
Feature ideas for future versions
Beta testers for upcoming integrations

Drop your thoughts in the comments — or message me directly. I'm always happy to connect.

Thanks for reading 🙌
Let’s build smarter, not slower.
— Othmane | https://figmentor.io

Is It Time to Say Goodbye to Node.js? (Deno 2.0 Got This)

Othmane N. — Mon, 14 Oct 2024 23:15:43 +0000

Node.js has been the heavyweight champion of JavaScript runtime environments since its debut in 2009. With a massive ecosystem, millions of npm packages, and widespread use in both startups and enterprises, it's hard to imagine a world without it. But, just when you think Node.js is untouchable, along comes Deno 2.0, knocking on the door with a "Hey, I fixed your problems!" kind of energy.

So, is it really time to say goodbye to Node.js? Well, maybe not yet, but Deno 2.0 has certainly given us some food for thought.

1. Security: No More Wildcard Permissions

One of Node.js’s biggest criticisms is its "all-access pass" to your system. When you run a Node.js script, it has access to your filesystem, environment variables, network, and more—unless you specifically lock it down.

Deno flips this on its head with a secure-by-default approach. By design, Deno asks for permissions before a script can access your files, environment, or make network requests. Want your app to read files? You'll have to pass the --allow-read flag. It’s like the permission model on your phone apps, but for JavaScript.

With this, Deno solves the “security paranoia” that some developers had when running untrusted Node.js modules. No more accidentally giving full access to random packages!

2. Built-in TypeScript: Node.js Still in Denial?

If you’re using Node.js and you want TypeScript (and trust me, you do), you have to set up a toolchain, install a bunch of dependencies, and compile your code before running it. TypeScript is an add-on, not a native feature.

Deno 2.0? TypeScript is baked right in! You can run TypeScript files directly without any extra setup. Just write your code and run it. No more ts-node or compiling hassle. It’s as if Deno is saying, “Hey, we know you’re using TypeScript, so we got you covered.”

3. Goodbye, `node_modules` Bloat

If you've worked with Node.js long enough, you know the pain of the infamous node_modules folder. It's a graveyard of dependencies, nested dependencies, and duplicates that can sometimes grow larger than your actual codebase. It’s one of those “just deal with it” issues that developers have come to accept.

But Deno says, no more! Deno ditches the traditional package manager (goodbye npm, hello URL imports). Instead, dependencies are cached globally and resolved via URLs. It’s a bit like how front-end JavaScript works in the browser. The best part? No node_modules folder eating up your disk space or causing dependency hell.

4. The Standard Library: Finally Some Consensus

Node.js offers great flexibility, but it also leaves you to figure out things like file manipulation or HTTP servers by picking random third-party libraries. Want to manipulate files? Do you choose fs-extra, graceful-fs, or native fs? The abundance of choices can lead to "decision fatigue."

Deno comes with a curated standard library that offers essential functionalities right out of the box—file system, HTTP servers, date manipulation, etc.—without needing to rely on a third-party package. It’s less choice but more consistency.

5. ES Modules by Default: No More Require Drama

Node.js has historically used CommonJS (require/module.exports), but has only recently added experimental support for ES Modules (import/export). This has led to some confusion, friction, and compatibility issues.

Deno? It fully embraces ES Modules from the get-go. No mixing and matching of module systems, no ugly transpiling, no import headaches. With Deno 2.0, JavaScript finally behaves the same way on the server as it does in the browser.

But Wait—Node.js Isn’t Going Anywhere... Yet

While Deno 2.0 fixes some of Node.js’s long-standing issues, it's important to remember that Node.js is massive. With its vast ecosystem, enterprise support, and proven stability, Node.js isn’t just going to vanish overnight. It’s like comparing a classic rock band to an up-and-coming indie artist. Node.js will still be here rocking for a while.

However, Deno is catching up quickly, and for many new projects, its out-of-the-box improvements may make it a more attractive choice. The community and ecosystem still need to grow, but if you’re starting a project today, it’s worth considering whether you want to deal with the baggage of Node.js or enjoy the streamlined simplicity of Deno 2.0.

Conclusion

So, is it time to say goodbye to Node.js? Not quite. But with Deno 2.0, it might be time to consider whether you want to say hello to something better suited for the modern JavaScript/TypeScript world. Deno's got this—and it’s definitely worth paying attention to.

The Challenge of Building Web Applications with Node.js Frameworks

Othmane N. — Thu, 26 Sep 2024 13:01:20 +0000

In the world of Node.js development, there's no shortage of frameworks available for building web applications. From lightweight frameworks like Koa to full-fledged solutions like Express and NestJS, each offers its own benefits. But as a senior developer working on large-scale production applications, I've come across several limitations that persist across these tools:

Boilerplate Code: Even with minimal frameworks, developers still spend too much time setting up basic structure and repeating common patterns.
Scaling Complexity: Scaling applications often means piecing together various plugins, libraries, and middlewares, which results in fragmented solutions.
Performance Bottlenecks: Many frameworks handle small-to-medium-sized applications well, but they tend to slow down as the application grows.
Enterprise Readiness: Most frameworks are either too simple for enterprise-grade applications or require significant modification to be production-ready.

These challenges led me to re-evaluate how we build Node.js applications at scale, particularly using Koa.js, which I’ve been using extensively in large production environments. While Koa provides flexibility, I found myself constantly rewriting common patterns, patching together missing features, and working around scalability limitations.

A New Approach to Node.js Frameworks

To solve these issues, I’ve started developing Mavro, an open-source framework for Node.js, built with TypeScript. Mavro is designed to be:

Minimal, but Powerful: Focus on simplicity without compromising functionality.
Enterprise-Grade: Built with scalability, performance, and security in mind from the start.
Production-Ready: No need to rely on multiple third-party plugins—Mavro comes with the essentials built-in.
Developer-Friendly: Aimed at reducing development time by providing a structure that developers can extend easily without boilerplate.
Inspired by Real-World Experience: Mavro is born out of my day-to-day work on high-performance, large-scale applications, addressing the real needs of developers building for production.

But Why?

As a senior developer, I understand the frustrations of working with frameworks that aren't built with scalability in mind. Mavro aims to bridge that gap. It’s a framework designed by developers, for developers, with the sole purpose of making large-scale production applications easier to develop and maintain.

I’ve incorporated the core concepts that I’ve found necessary in enterprise-level applications, but I’m not doing this alone. Mavro is an open-source project, and I’m calling on developers who face similar frustrations to join me in shaping its future.

The next few months will be critical as we shape Mavro into a production-ready framework. I’m inviting contributors who are passionate about creating a better development experience for Node.js to join me in this effort.

Here’s how you can get involved:

Contribute Code: Whether you’re a seasoned developer or just getting started, your contributions are welcome.
Share Ideas: Bring your experience with other frameworks and suggest improvements.
Collaborate: Work with a community of developers who are solving real-world challenges together.

Join the Mavro Discord community, where we’ll discuss ideas, collaborate on code, and make this framework a reality. Together, we can create an open-source, enterprise-grade framework that’s ready for production in the upcoming months.

Call to Action

This is an opportunity to be part of something that serve the dev's—to contribute to a framework that is set to redefine how we build Node.js applications for scale. If you’ve ever been frustrated with the limitations of existing frameworks, this is your chance to make a real impact.

Let’s build something great, together.

Join the Discord Community