Starting something new

@mrmnmly
@mrmnmly
Jul 20, 2017 · 3 min read

For the last couple weeks I was pretty silent on social media — mostly because I was focused on work at my new workplace — Influenster — I work there remotely based on NYC timezone which was a pretty huge change for my (and my family) lifestyle.

After setting most new stuff in my life on the right direction I’ve decided to start build something new in my spare time.

As some of You might already know I was already developing my own framework (Rakun.js) and static site generator (Inku.js) — here’s the current status of them:

Current state of Rakun.js development

The main reason behind Rakun.js creation was the feeling of absence a straightforward and intuitive front-end framework on the market. Oh, how wrong I was! Everything changed for me when I’ve took a look at Vue.js framework. It looked for me like a better, more mature concept of Rakun.js. It feels like someone read in my mind, took best features for a framework, added some more fantastic ideas and voila — here’s Vue.js :)

Currently it’s my frond-end framework of choice and I’ve decided to stop working on Rakun.js at the moment.

But who knows, maybe at some point I’ll feel bad for a direction which Vue.js team will take and I’ll come back to developing it.

Current state of Inku.js development

Inku.js is after first iteration of its development. I was pretty satisfied of it for a while, but it was something like a year ago. In the meantime I’ve prepared new design of its interface and started testing some new features independently of its core. Thanks to such approach, I’ve noticed some weak points of creating static site generator and decided to create something different.

Something different (a.k.a. the main topic of this article)

Sometimes testing stuff separately rather than adding it incrementally to existing project pays off. I’ve found that I won’t be in the end satisfied with static site generation tool so I’ve decided to create a API-based app, which will be easily extendable with new features. I’ll also provide an admin panel, based on Vue.js / Nuxt.js (not decided yet) which will be able to run as a separate thread on the server. Why create this separately? Because maybe someone will want to create own dashboard using own set of tools, based on provided API.

In addtion, I know that’s good to be pragmatic, but I plan to use a Node.js for a backend engine in this project. I know that this may not be a best choice as a solution for such task but:

  • I love JavaScript, I really do,
  • I want to gain more experience on working with Express.js (or Hapi.js, haven’t tried it yet but I also consider using it),
  • I want to do this for fun, and programming with these tools is fun (at least for me ;) )
Even when You use right tool for the job You can use it wrong.

I also plan to document the whole process, step-by-step, each commit day here, on medium (till I won’t complete it and move everything on my own platform ;) ) — so if You’re curious — feel free to follow me on Medium.

Stay tuned — first article about the process will be published soon.

Best,

— ł.

This is the last post as @lukaszkups — for now I’m switching on all my social media to new account username: @mrmnmly — You can find me also on twitter, github and instagram.

)
@mrmnmly

Written by

@mrmnmly

Just another front-end developer. And tech writer. And a bit of an AFOL. And a geek maybe.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade