Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move documentation repo into component-library monorepo as package #1219

Closed
6 tasks
bkjohnson opened this issue Sep 22, 2022 · 2 comments
Closed
6 tasks

Move documentation repo into component-library monorepo as package #1219

bkjohnson opened this issue Sep 22, 2022 · 2 comments

Comments

@bkjohnson
Copy link
Contributor

Description

In an effort to consolidate to a single repo, we should move the Jekyll/npm package vets-design-system-documentation into the component-library repo as a package.

Tasks

  • Create a new documentation package in component-library repo
  • Move src and config files into new package
  • Move deploy Github action file into component-library root .github directory
    • This should be updated to only deploy to dev until we can confirm that things still work
  • Update links to point to new location
  • Update design-system-documentation README file to point to new location

Acceptance Criteria

  • documentation repo lives as a package in the DST monorepo
@humancompanion-usds
Copy link
Collaborator

I see now that this is related to #1220. Why do we need a single repo? Don't we push and publish components and documentation for them on different timelines? Is the goal to unify that?

@caw310
Copy link
Contributor

caw310 commented Sep 18, 2024

Closing as this is old and the VADS components have been updated so this should no longer be an issue. If there is still an issue with the new components, file a new bug.

@caw310 caw310 closed this as completed Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants