cipherlogs/uhugrid

The fast alternative to masonry and mosaic layout.

The motivation

By the end of 2021, I had been bitten by the crypto bug. It lived at the intersection of many of my interests, and also opened the possibility of creating solutions that could wrest sovereignty away from the oligarchy and back to the people.

Only this can make a truly enduring difference in people's lives.

Coupled with the elegance of functional programming languages, it is a match made in tech heaven.

That's exactly my area of interest.

uhugrid's Issues

create items that fit their content size

This feature wasn't a goal of uhugrid, however it would be nice to add an option where the user
can choose if they want to display the whole item content or not.

that's the only advantage of masonry, once this feature is implemented. That advantage will be gone

Enhancement of Uhugrid's Documentation

Hi there! I'm ALIPHATIC. I've been exploring the Uhugrid and noticed a few areas where we could enhance the documentation to make it even more informative and user-friendly.

Here are some suggestions:
Troubleshooting: Address common issues and solutions.
Contributing: Explain how developers can contribute to the project.
Licence: Specify the project's licence to clarify usage rights.
FAQ: Answer frequently asked questions about the app's usage and limitations.

I'd be happy to contribute to drafting or editing these sections to make the documentation more comprehensive and helpful for both users and developers.

I'm open to any feedback or suggestions on how we can improve the documentation together. Thanks for considering these ideas!

Add more ratios that are aesthetic.

Maybe more variants of the golden ratio, and other known ratios

every time the function is trying to decide what sizes to choose from the available free space
make sure to prioritize good aspect ratios first.

Save state, it will help with performance OR change styles directly

It will be better to save the page markup on page load. and use it later to inject only what's needed.
however the page might change dynamically, by other frameworks or scripts.

so instead of injecting the changes, change them directly over properties.

use the word card instead of item

card and cards sounds more natural.

update readme and also the css classes that the library depends on.

.gallery --> .cards__container
.gallery__item --> .card__item

make the classes a bit unique so that they won't easily clash with other libs classes.

Lazy loading

maybe offer some sort of lazy loading

if the item only contains the image, then lazy load it (if the user is okay, settings)
if the item contain other content, load text first then images.