cltk_frontend
cltk_frontend copied to clipboard
Browse view
This is an issue for the longer-term epic-sized task of building a search page to use for searching the classical texts served by the CLTK. As much as is useful, we should split smaller issues related to the search page into their own issues.
@achaitanyasai, I think that sometimes people will want to browse and discover and sometimes want to search for a specific work. In my mind, these should be two separate views. I think a good way to do it might be that focusing on the search input text element on the homepage actually pushes the user to /search where they can type their query, and then the homepage and /browse can share similar components for browsing/discovering works instead of searching. How does that sound?
Yeah got it, thanks.