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

Concept: modularise and open source site components #1584

Closed
larsyencken opened this issue Aug 10, 2022 · 4 comments
Closed

Concept: modularise and open source site components #1584

larsyencken opened this issue Aug 10, 2022 · 4 comments
Labels

Comments

@larsyencken
Copy link
Contributor

larsyencken commented Aug 10, 2022

High level vision

We want to be able to remix site elements easily to quickly make new pages and new visualisations.

To enable this, we'd like to identify and make modular and consumable elements that are high value for reuse.

Proposed changes

  • Grapher is split out and consumable as an independent open source project, with releases to NPM
  • OWID site is its own private repo
  • (Are there other reusable components that we would want here?)

Sub-issues

@larsyencken
Copy link
Contributor Author

@mathisonian Did you have a specific sense of which components would be most useful to be thinking about here?

@mathisonian
Copy link
Contributor

I think the following would be helpful to start thinking about as independent pieces:

  • grapher
  • front-end component library (buttons, dropdown, images, etc)
  • shared database types / utils
  • baker
  • admin + wordpress (the code for these might be better off separate or together, depending on how coupled they are)

We'd want them each to be independently packaged, versioned, and released. I don't have a strong stance on if its better to break these modules into their own repos or keep them in a monorepo using something like lerna. The monorepo structure is likely nicer to work with.

@larsyencken
Copy link
Contributor Author

Ah, Ierna looks cool! It sounds to me like a monorepo would be best for internal development, provided it's still easy to work on just one project at a time, and the build system is sane. Looks like Ierna and Nx solve the build problem.

@github-actions
Copy link

github-actions bot commented Aug 8, 2023

This issue has had no activity within 10 months. It is considered stale and will be closed in 7 days unless it is worked on or tagged as pinned.

@github-actions github-actions bot added the stale label Aug 8, 2023
@larsyencken larsyencken closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants