1ifeworld / river

Set information free.
https://river.ph
GNU Affero General Public License v3.0
25 stars 2 forks source link

Jawn/index #583

Closed jawndiego closed 2 months ago

vercel[bot] commented 2 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
river-site ✅ Ready (Inspect) Visit Preview Apr 19, 2024 7:01pm
river-site-metadata ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 19, 2024 7:01pm
railway-app[bot] commented 2 months ago

This PR is being deployed to Railway 🚅

railway-app[bot] commented 2 months ago

This PR is being deployed to Railway 🚅

river-delta-production: ◻️ REMOVED

salieflewis commented 2 months ago

Index seems to be a reserved namespace, what is the alternate name for it

What is the active state of the link when navigating to that route? Is the text just black, does ‘River’ become grey?

What is the ordering logic for these channels?

cc: @1ifeworld/core

0xTranqui commented 2 months ago

Index seems to be a reserved namespace, what is the alternate name for it

What is the active state of the link when navigating to that route? Is the text just black, does ‘River’ become grey?

What is the ordering logic for these channels?

cc: @1ifeworld/core

  1. can we dig into the name space more please? quick search of google + nextjs docs did not give any indication that "index" is reserved namespace.
  2. I think we should put whatever this "directiory/index" is as a dropdown item, not in the header. and then we dont have to deal with this. the only issue with this approach is that the index would be inaccessible to peopel without an account/logged in
  3. i think first pass on ordering should be alphabetical, so as to serve as a logical way to find specific entities
0xTranqui commented 2 months ago

another smol nit atm is that this page should have the marquee at the top, as according to these designs in wip6

Screenshot 2024-04-15 at 5 23 04 PM
jawndiego commented 2 months ago

image

current view // pending user query .. which likely involves fetching all existing ids and associating it with a username then sorting all usernames and printing them in grids. need to add mobile stacking of grid.