Blazor-server-side Multi routing such as in mvc

[Alerinos]

I have two sides

@page "/{article?}"

<h2>@article</h2>

@code {
    [Parameter]
    public string article { get; set; } = "";

    protected override async Task OnInitializedAsync() 
    {
        if(article != "testArticle")
        {
            // return NOTFOUND
        }
    }

}

@page "/{game?}"

<h2>@game</h2>

@code {
    [Parameter]
    public string game { get; set; } = "";

    protected override async Task OnInitializedAsync() 
    {
        if(game != "testGame")
        {
            // NOTFOUND
        }
    }

}

I would like many sites to be able to run under one domain like in mvc
example:

domain.com/good-news
dmoain.com/best-game
domain.com/good-forwarding
domain.com/testGame
domain.com/testArticle

in mvc it was enough to give return NotFound();

[javiercn]

@Alerinos thanks for contacting us.

This is already possible today provided that you host your apps in different base paths. Here is a sample I wrote a while ago that you can use as a starting point. It's for Blazor webassembly, however you should be able to adapt it for Blazor server without much trouble.

[Alerinos]

I didn't really mean it. The application is shared, but large sites have several sections.
For example, a sports website may have articles, players and sports clubs.
Instead of doing

domain.com/club/Manchester-United -> domain.com/Manchester-United
domain.com/footballer/ronaldo ->domain.com/ronaldo
domain.com/article/best-match-ever-2020 -> domain.com/best-match-ever-2020

@javiercn I don't think your example will work that well

[javiercn]

@Alerinos it's not clear to us what you are trying to achieve.

Are you looking for something similar to Areas in MVC?

[Alerinos]

@javiercn
I am looking for a way for many pages to have a common dynamic link. Articles, clubs, footballers, coaches, stadiums. I want to do short links for SEO. Instead of creating a link with the module name, it's all directly from the database. When entering the page, one query flies, if it finds it, it returns the result, if not, it continues with the query. If you find something in the database, this page is displayed.