Simply put, SSR has already rendered the content of the page when requesting it, so the SEO problem is naturally solved (crawlers can read the content directly when accessing).
Routing is actually isomorphic, that is, the same code can be understood and run by both the front and back ends, so there is no need to treat it differently.
I wrote a little bit last year, you can refer to it:
Simply put, SSR has already rendered the content of the page when requesting it, so the SEO problem is naturally solved (crawlers can read the content directly when accessing).
Routing is actually isomorphic, that is, the same code can be understood and run by both the front and back ends, so there is no need to treat it differently.
I wrote a little bit last year, you can refer to it:
https://ruby-china.org/topics...
https://ruby-china.org/topics...