Right, so I might be wrong here, but my understanding of mashlib is that it’s only ever showing a single users data at a time, that is, you’re just browsing a single WebID / Pod, and maybe following some relationships to pull in additional public data.
This typically works by having the URL be the WebID, or by passing in the WebID via the URL query params or similar. Compare that to a homepage with multiple users data all served together from the root, i.e., /. In the homepage you’ll need some store of data which is “which users am I loading data from”, which then gets into some tricky territory when it comes to sorting, paginating & making the loading performant (these might be able to be patched over by using QPF or Sparql query indexing)
But you’ll still need something that acts as a central store for your “homepage”, and some way to “find” the content you wish to display