I have an ASP.NET Core application that is currently serving a Single Page App as static files (https://github.com/Zoltu/bags-client/blob/master/Startup.cs#L56). I want to make it so that the `index.html` page is rendered server side before being served so I can tweak the page headers based on the route the index page is accessed at.
This project is (hopefully) a small project to simply make it so the `index.html` page that is currently being served statically will instead be served as an Razor view, without moving the file or changing it at all. I believe Razor views are backwards compatible with standard HTML pages, so I think (correct me if I'm wrong) this task can be achieved without actually changing the contents of `index.html`, and instead just referencing it as a Razor view.
The goal of this project will be to have a controller for the `index.html` route that uses `index.html` as its Razor view so I can add code into the controller that will alter the header of the rendered page. As an example, the title of the page is static right now (https://github.com/Zoltu/bags-client/blob/master/client/index.html#L70) but depending on the route the user uses to get to the page I would like to make it so the title changes to reflect that (e.g., "Bag Cupid - Michael Kors").
I have a front-end engineer who works on the HTML and my goal is for this change to have the lowest impact on his workflow, which does not currently involve MVC, ASP.NET, Visual Studio, etc. I recognize that there may be some impact, but I really want to minimize that as much as possible which is why I want to use the existing `index.html` in place and treat it as a Razor view.
This project is written using ASP.NET Core and runs on the Core CLR. In my production environment it runs in Linux and uses Docker for its build/deploy system. I don't expect applicants to have experience with all of this since a lot of it is bleeding edge, but you must be prepared/capable of quickly adapting to working in this environment.
This project is run/managed on GitHub. Submissions will need to be in GitHub Pull Request format. I don't expect a Git master, though I do want someone who is familiar enough with it to submit a Pull Request, or someone who is willing to learn how to do this on their own (I can provide links to online tutorials/instructions).