Welcome to the first Celaro Dev Log!

We’re excited to kick off this series, giving you an inside look at the evolution of Celaro as we move toward launch. In these posts, we’ll keep you updated on our latest changes, share insights from our development process, explore our tech stack choices, and much more. Stay tuned for a behind-the-scenes glimpse of our journey!

🗄️ Monorepos

Over the past 2-3 weeks, we've been focused on making significant improvements to the Celaro codebase. About a year ago, we made the decision to transition to a monorepo setup, knowing we wanted to expand the platform with additional repositories over time. For that, we chose NX as our solution for managing the monorepo.

However, we encountered recurring issues whenever we needed to upgrade something, particularly during our recent migration to Payload 3.0 (the CMS behind powering back end). As a result, we decided to switch to Yarn Workspaces instead, and so far, it feels like the right decision. The setup is now more streamlined, aligning with our vision of what a monorepo should be: simple and efficient.

We believe this structure aligns with our vision for the future of Celaro, which includes plans for VS Code extensions, Figma plugins, and much more.

This is the structure that we are now left with:

apps/
  client   // Next.js frontend application
  server   // Node.js server managing sockets and other services
  cms      // Backend powered by Payload CMS

packages/
  integrations  // Central package bundling all integrations
  shared        // Reusable components, utilities, and types
  widgets       // Collection of UI widgets and components

💬 New Feature: Comments for tasks

We're continuously adding new features that we believe are essential for our MVP. Most recently, we've implemented comment functionality for tasks, allowing users to engage in discussions directly within each task. This feature simplifies collaboration and helps maintain focused conversations around specific tasks.

➡️ Next Steps

In the coming weeks, we'll continue building new features as we work toward completing our MVP in the months ahead. Stay tuned for updates on these upcoming changes, where we’ll hopefully dive deeper into the details in our next dev log.