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

Registry feature marketing section #4

Open
fortmarek opened this issue Jan 8, 2025 · 6 comments
Open

Registry feature marketing section #4

fortmarek opened this issue Jan 8, 2025 · 6 comments
Assignees
Labels
p2 Should do

Comments

@fortmarek
Copy link
Member

Our registry feature is important enough that we'd like to highlight that on our landing page.

What we should highlight is:

  • Resolving dependencies with Tuist registry is a lot faster than with the default method
  • The reason why it's faster is that you end up downloading only the source archive of the version you need. In contrast, when you use the default source control-based resolution, you'd need to download the full git history of all packages that you depend on.

@pepicrft @asmitbm do you have some ideas for how we could visualize this?

For more context, read about the registry at our community forum: https://community.tuist.dev/t/tuist-registry-initiative/262?u=marekfort

@fortmarek fortmarek added the p2 Should do label Jan 8, 2025
@pepicrft
Copy link

@pepicrft @asmitbm do you have some ideas for how we could visualize this?

I was thinking we can have the planet earth that shows you trying to pull packages, and then arrows coming from a storage close to your location, as opposed to cloning larger content from further locations. The location can be represented by the source of the arrow, while the size of the download can be represented with text. Something like this:

image

@fortmarek
Copy link
Member Author

I was thinking we can have the planet earth that shows you trying to pull packages, and then arrows coming from a storage close to your location, as opposed to cloning larger content from further locations. The location can be represented by the source of the arrow, while the size of the download can be represented with text. Something like this:

I like that 🙂

@asmitbm
Copy link
Member

asmitbm commented Jan 13, 2025

I will give this a look once I am done resolving the design system issues :))

@fortmarek
Copy link
Member Author

@asmitbm do you think you'll have time to look into this? I think it'd be good if the same illustration that we'll have on the landing page would also accompany the release blog post.

@asmitbm
Copy link
Member

asmitbm commented Jan 20, 2025

@asmitbm do you think you'll have time to look into this? I think it'd be good if the same illustration that we'll have on the landing page would also accompany the release blog post.

Hey Marek,

I’ll be working on this page this week and should have something ready by the end of it. When are we planning to publish the release blog post?

@fortmarek
Copy link
Member Author

When are we planning to publish the release blog post?

The plan is to post it by Wednesday – but no pressure to get it done by then, we can go ahead with the blog post without the image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p2 Should do
Projects
None yet
Development

No branches or pull requests

3 participants