📦 Breaking out the components into a separate npm package

[jeoffreyfischer]

Description

I want to break out new components into a separate NPM package.

Tasks

• Create the new NPM package structure.
• Refactor components into the package, ensuring separation of concerns.
• Update imports in the main project to use the new package.
• Set up CI/CD pipeline for the package.
• Write or update documentation for the package.
• Test the integration of the package with the main project.

Acceptance Criteria

• A new NPM package is created and published under the organization's registry.
• Components are refactored out of the main project into the new package, maintaining full functionality.
• Documentation for the new package includes:
  • Installation instructions
  • Usage examples for each component
  • Versioning guidelines
• The main project is updated to consume the new NPM package instead of the local components.
• CI/CD pipeline is set up for the new package to handle:
  • Linting
  • Publishing to the registry

[isaaclombardssw]

Update – I've created the repo and based it off this package... https://github.com/pcode-at/tinacms-seo.

[Calinator444]

I've created a repo for building the component library using rollup based on the files @isaaclombardssw provided me with while working on this.

My plan is to get the components working in a state where I can easily import, customize and use them in the Tina starter repo and then publish the package to NPM.

There's still some work that needs to be done because the components don't work very well as standalone components. We also need to make a decision as to whether we should take an opinionated or unopinionated approach to schema management as this will affect developers implement contextual editing.

https://github.com/Calinator444/ssw-consulting-component-lib

Todo: Configure

• Breadcrumbs
• Carousel
• Color Selector
• Image and text block
• Ripple button
• logo carousel

[Calinator444]

TODO: add custom prefixes to custom tail classes