Inspiration

As a software engineer, version control is a core part of the development process. With the advent of git etc, gone are the days of renaming files code_1, code_2, etc. Similarly, digital creators incrementally make changes to continuously improve their artwork. Collaborating with one's team and sharing large file formats, however, has increasingly become difficult as the needs for better quality content climbs.

What it does

Artists are able to work in public, sharing verifiable credit on contributions that they make on with projects. They are able to create new versioned projects where collaborator are able to use ArtHub as a central source of truth for changes that they make to their projects.

How we built it

Large, distributed file store: Estuary Front end: HTML, CSS, Javascript Back end: Node, Express Database: Firestore

Challenges we ran into

Coming up with a data model for what additional metadata needs to be store in our DB and how that can be integrated with the raw files being stored in Estuary were challenging on the back end side. Front end and back end integration required multiple different moving pieces such as how we get our data uploaded to Estuary while also adding metadata to our backend service.

Accomplishments that we're proud of

Only having just met at the team building event at the start of the hackathon, team is relatively new to hackathons and coding. That said, we set out challenging yet achievable goals for ourselves as a team and were able to get a working demo of our idea while collaborating closely and working off of each others' strengths.

What we learned

Team work makes the dream work.

What's next for ArtHub

We think that integration of NFTs to facilitate group access to certain art projects could be a interesting extension off of our current work.

Built With

Share this project:

Updates