ian/rodeo

A static site generator, making NFT galleries

👋 I'm Ian.

I'm a Web3 developer, more on me: https://ianh.xyz.

rodeo's Issues

npx giddyup script

This is the main project initialization CLI script.

This is meant to be run as an npx command.
It will:

• ask what's the name of the project
• create the project directory
• add package.json dependencies
• runs rodeo config
• displays success message to user to run rodeo dev

Support for organizing tokens into collections

While tags originally seemed like the best route to organize tokens as they would be able to be rendered as index pages, there could be a lot of value in supporting the idea of "collections" as a first-class citizen in Rodeo.

There are many use cases collections could provide:

• Enabling a collector to bring together many disparate pieces under a category (e.g. "OG tokens, pixel art, etc.")
• Enabling a creator to organize a series of works under one banner (Beeple's "Everydays" vs. any other project)
• Enabling a curator to promote the sale of different works from different artists together as a single collection

I propose that collections would have:

• Title
• Description
• Assets
• Cover art and logo (optional)

Additionally we could eventually support "smart collections" which could have a ruleset to populate them, all of which could be based on our pre-existing contexts such as the creator's address, owner's address, timestamp, etc.

[FIRST] Lerna project structure

Initialize the project as a monorepo via Lerna

Support adding notes to individual tokens

Inspired by DC Investor's tweet, it would be very useful if a creator or collector could add some text alongside the tokens that they have in their wallet. The tweet:

https://twitter.com/iamDCinvestor/status/1377969412909715457?s=20

Some reasons:

• Creators may have a story behind their NFTs that they want to write up that goes beyond the metadata that they had included in the file
• Collectors might want to add a description as to why they had collected a particular NFT

We may also want to add some sort of description in the JSON as to who the party is that is leaving the note. This way themes could render "Creator's note" or "Collector's note" as a header to the notes themselves.

Examples of how to use rodeo? Example repo with NFTs?

rodeo CLI script

This should run the main tokenrodeo service CLI script.

Commands include:
rodeo config - configure your web3 accounts
rodeo dev - start a devserver with hotmodule reloading
rodeo build - build the production version of tokenrodeo

Allow for uploading of a theme package

Along the lines of #19 it would be useful if users could simply upload a ZIP file containing the theme that they would care to use for their site. This is similar to how Ghost works (https://ghost.org/docs/themes/).

UI-based configuration for setting up and maintaining a gallery

For "normal" users Rodeo should have a UI that's easy to use once the server has started from the terminal. This configuration UI should have all of the features the CLI provides, available to it in an easy-to-use manner.

Here are some potential UI options:

Why not deploy to IPFS via pinata or whatever?

You should be able to automagically deploy to IPFS using a persons pinata keys.

You could also become a controller on their eth domain and deploy and point automatically as well.

Can we get an edition number in a 1 of n series?

It would be interesting to enable themes to prominently display the edition number alongside a token. Being able to retrieve the n of an edition should enable us to do this.

Is the project dead? Moved away? How can we get this to be maintained?

Support for Rarible Protocol for token sales

The Rarible Protocol offers features that could enable Rodeo gallery owners to process sales right from their sites. Adding support for the protocol would open up new opportunities for gallery owners, as well as help to solidify Rodeo's case to be funded by the Rarible Protocol DAO.

Fix install / npx docs

They push you to use rodeo dev but this only works from a global npm install. Right now default install will fail.

Change rodeo dev to yarn dev etc.

Would like to keep the project localized and not require global installs but my mind can be changed.

Support adding notes to collections

Similar to #22 creators and collectors may have a desire to add additional color to a given collection. For the purposes of this issue, a "collection" may be a specifically defined collection by way of the various marketplace APIs, or the ERC-1155 token contract, or it may simply be a tag that has been set up in their Rodeo instance.

Allow for multiple wallet addresses to be fetched from

There are use cases in displaying NFTs that may require fetching from more than one wallet address. Some examples include:

• Collectors that use both cold and hot wallets for their assets
• Artist collectives that would like to display all of the works of their constituents
• Creators that minted from one address but moved to another at a later date

In all of the above examples Rodeo will need to support fetching and managing from multiple wallet addresses.

Enable switching to a theme from a repository URL

It would be slick if Rodeo could use a Github URL as an input for switching themes. Grabbing the latest build from a theme repository would ensure that the user has the most up-to-date and valid code to launch their site with.