Pricing Blog

Design System based on Spark Core – best practices?

  • obvijes-1412775681380585535

    Obvijes

    10 days ago

    We want to set up our own design system in NC, but we’d like it to be based on Spark Core. The tricky part: as far as I can tell, you can’t include one package inside another.

    Our idea was to have our design system as a package, and then integrate SparkCore into it so we can use it as the foundation. Copying Spark and building on top of it doesn’t feel great — too many components, no way to update later, etc. What we’d really like is a “package-in-package” approach.

    Maybe that’s not how NC is meant to handle dependencies, but for us it would be ideal. What’s the best practice here? Is there another way to build a design system on top of Spark and reuse it across projects?
    👍1
  • Design System based on Spark Core – best practices?
  • lucasg-1412784375447162993

    Lucas G

    10 days ago

    Only option right now is to create a base project that you clone to start new projects from
  • Similar to how some people use Spark One as the starting template
  • obvijes-1412805750610329660

    Obvijes

    10 days ago

    hm ok, not really ideal
  • baba_bambule-1412903696177823876

    BabaBambule

    10 days ago

    Not a perfect solution, but you could clone the spark core package, style it in your design system and use this package then. Would mean you won't get any updates on spark core, but another way to tackle it