Content
@
https://warpcast.com/~/channel/someone-build
0 reply
0 recast
0 reaction
horsefacts 🚂
@horsefacts.eth
Who's gonna be the /frogfm and @frames of frames v2?
7 replies
9 recasts
44 reactions
Samuel ツ
@samuellhuber.eth
On it. Will have OSS repos + guides on the dTech GH + docs Likely will be a starter repo + docs Unsure yet how a framework would look like Thought about a micro wrapper of the Warpcast SDK to add metrics etc so some boiler plate all frames need are built in
2 replies
0 recast
7 reactions
Harris
@harris-
I think starter repo makes the most sense. A lot of possibility for customizing your framework of choice and ssr vs static. Plus not having limitation on just rendered images opens up the floodgates
1 reply
0 recast
1 reaction
Samuel ツ
@samuellhuber.eth
could you expand on what the starter repo should have for you? and how you'd costumize the framework? What ideas went into your cast, not sure I fully grasped it
1 reply
0 recast
0 reaction
Harris
@harris-
Hmmm I mean like a lot of people will have a favorite web framework or workflow they might already be using, with options for how things are rendered and presented, CSS and whatever else preprocessors or UI libraries they might already be familiar with, as well as hosting options. Now that there aren't so many limitations on the information you can return i.e. images or gifs as the frame, you can reuse something you might already be familiar with and it might be really hard to build a frog/other library to cover all those bases in any better way than someone might already be familiar with
1 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
which means your saying make it a TS only library everyone can leverage? which may just add some utils to warpcast sdk? then have one starter thats opinionated using it and serving as template?
1 reply
0 recast
1 reaction
Harris
@harris-
I would say, make it opinionated to whichever stack people are most likely to use, probably next + tailwind or something, and have maybe some next specific metadata and frame spec generations supplied as helper functions maybe, with some useful defaults and comment out the unused ones / what the default parameters are maybe so people could extend them as they see fit. The metadata generation and opengraph stuff I think will be the difference in each platform, and whether people have their own way of doing the OG/FC tags or just use the framework's provided ones might be super useful
0 reply
0 recast
0 reaction
