Naming for the "Razor Pages" feature

[DamianEdwards]

This issue covers what names we're going to use for the feature described in #494.

Considerations There are a few things to consider when it comes to naming this feature, including but not limited to:

• the descriptive feature name itself
• the names of classes and methods associated with the feature (e.g. for configuring in MVC options, the base class of the generated page, the Razor directive to declare a page, etc.)
• search-ability (Google-fu), e.g. how unique is it
• the names for item templates in Visual Studio (e.g. adding a new page)
• the names of NuGet packages associated with the feature
• this isn't intended to be a separate framework, it's a feature of ASP.NET Core MVC
• we can't invent new "brands", i.e. it needs to be descriptive
• we cannot change the file extension. It will remain .cshtml

Consider the following prior uses of common terminology used to describe this feature that are already part of ASP.NET history (and/or present), and as such aren't suitable candidates:

• We already have a product called "ASP.NET Web Pages". This feature is not a new version of this product.
• The base-class for Razor views in ASP.NET Core MVC is RazorPage
• The Visual Studio item template for adding new Razor views to ASP.NET Core MVC is "MVC View Page"

Creating & Voting on Suggestions Suggestions should be created as comments on this issue, copying the format and detail of the first suggestion below then updating it with the details of the suggestion.

Folks can indicate their preference by adding a reaction to the issue (the smiley face in the top-right corner):

• Thumbs-up (:+1:) for like
• Thumbs-down (:-1:) for dislike

If you want to simply comment on a suggestion, by all means do so. Just create a new comment on this issue and please be sure to make it clear which suggestion you're commenting on.

Notes Please note the following:

• We won't necessarily automatically choose the suggestion with the most likes. This isn't a ballot, it's an opportunity to obtain and gauge feedback.
• We'll edit suggestions as necessary to ensure they're consistent with the format specified
• We'll disqualify suggestions as necessary (and edit them to show this) if they can't be used due to legal, political, etc. reasons
• We're trying this process out and have no idea how well it will work, but we appreciate your participation :smile:

@rynowak @Eilon

[DamianEdwards]

Item	Name
Feature name	ASP.NET Core MVC Routable Views
Page Base Class	Microsoft.AspNetCore.Mvc.Razor.RoutableRazorPage
Page directive	@route
MVC options builder method	.AddRazorRoutableViews
Item template	MVC Routable View Page
NuGet package	Microsoft.AspNetCore.Mvc.Razor.RoutableViews

[DamianEdwards]

Item	Name
Feature name	ASP.NET Core MVC Controllerless Views
Page Base Class	Microsoft.AspNetCore.Mvc.Razor.ControllerlessRazorPage
Page directive	@route
MVC options builder method	.AddRazorControllerlessViews
Item template	MVC Controllerless View Page
NuGet package	Microsoft.AspNetCore.Mvc.Razor.ControllerlessViews

[DamianEdwards]

Item	Name
Feature name	ASP.NET Core MVC Pages
Page Base Class	Microsoft.AspNetCore.Mvc.Razor.Page
Page directive	@page
MVC options builder method	.AddRazorPages
Item template	MVC Page
NuGet package	Microsoft.AspNetCore.Mvc.Razor.Pages

[DamianEdwards]

Item	Name
Feature name	ASP.NET Core MVC View Pages
Page Base Class	Microsoft.AspNetCore.Mvc.Razor.RazorViewPage
Page directive	@page
MVC options builder method	.AddRazorViewPages
Item template	MVC View Page
NuGet package	Microsoft.AspNetCore.Mvc.Razor.ViewPages

[DamianEdwards]

Item	Name
Feature name	ASP.NET Core MVC Razor Pages
Page Base Class	Microsoft.AspNetCore.Mvc.RazorPages.Page
Page directive	@page
MVC options builder method	.AddRazorPages
Item template	MVC Razor Page
NuGet package	Microsoft.AspNetCore.Mvc.Razor.Pages

[pebezo]

Does it have to be under MVC? Could it be "ASP.NET Core Pages"? Since it's not technically MVC it may be confusing to put it under MVC (I understand that MVC is a product name, but for people new to ASP.NET, MVC is an architectural pattern).

[DamianEdwards]

@pebezo the current preference is for it to be a sub-feature of MVC, but I certainly appreciate your point. Unfortunately, MVC is the product name for better or worse and that's not going to change.

[DamianEdwards]

@ThoughtHaven pls make your suggestions in the full format outlined above.

[villanus]

Why does microsoft suck so bad at marketing. Rails, Flask, Django, Node, cake php, Mountain Lion...

See the pattern here? Instead of naming things after what they are (mvc), its better to name them something unique, searchable, and brandable.

Asp.net core naming was a step in the right direction. cleared up the confusion with the MVC 6 nonsense.

Now please do the same for Razor View Pages without the words: Razor, View or Pages.

Some suggestions: Asp.net MVC blaze Asp.net MVC rocket Asp.net MVC diesel asp.net MVC Apollo Asp.net MVC Silverback Asp.net MVC fastlane

I am sure the marketing team has a dictionary. Tell them to choose a name that is easy to brand, easy to search on Google, stack overflow, amazon and makes it crystal clear.

If you can drop the MVC part, that would be a Huge plus.

[hishamco]

Naming is hard 😄 , IMHO "Razor Pages" is a cool product name, especially if we isolate Razor from MVC, so Razor will no longer tightly coupled MVC. Hope the dream comes true

Item	Name
Feature name	ASP.NET Core Razor Pages
Page Base Class	Microsoft.AspNetCore.Razor.Page
Page directive	@page
Options builder method	.AddRazorPages
Item template	Razor Page
NuGet package	Microsoft.AspNetCore.Razor.Pages

[villanus]

@hismacho I like it but how will this be google friendly? I really wish msft would replace the words Web / Pages with something so unique it can easily be googled. The more brandable the better.

[Eilon]

Closing because the name has been established as Razor Pages.