Best Practices for Repository Visuals in amrex-Tagged Repositories: Detailed vs. Concise Descriptions/Images

[jmsexton03]

When customizing GitHub repositories tagged with the amrex topic (e.g., listed in the amrex topics page), there is a mix of repositories with existing branding/images and those without. The AMReX project also maintains a centralized gallery for visualizations at amrex-codes.github.io/amrex/gallery.html.

Is it better to:

1. Use banner images and detailed descriptions in individual repositories to enhance their visibility and appeal?
2. Use smaller images or no images and more concise descriptions in repositories to make browsing the topics page easier?

For context, GitHub allows repository owners to customize banner images and social media previews (docs). However, the AMReX community might benefit from a unified strategy to balance discoverability (via rich visuals) and browsing efficiency (via simplicity).

Example Social Media Preview:

Example Template for Social Media Preview:

Are there scenarios where one approach is preferable over the other (e.g., for repositories with existing branding vs. those without)? How does the centralized AMReX gallery complement or compete with these choices?

Thank you!

[WeiqunZhang]

Thanks for bring attention to this. I didn't know about this preview thing. I am going to add one to amrex.

[WeiqunZhang]

I just created an image using gimp. You can see it here. https://github.com/topics/amrex