One of the most popular types of Themelia Pro endpoints is the page endpoint.  This type of endpoint logically connects an user to a physical page.  From a technical standpoint, this type of endpoint is similar to URL rewriting, except that 1) Themelia Pro page endpoints are a web domain-aware topic and 2) URL rewriting quite literally rewrites the URL inside the web browser, thus destroys the orignal URL completely and destroys your ability to use query strings.  A page endpoint is much more mature concept than rewriting. Not only that, but 3) most Themelia Pro endpoints won't be page endpoints, but sequence endpoints (see ) for more information-- thus making the entire point moot)

You can setup a page endpoint in in two ways: via web components and via configuration.  Web Components will be discussed in a difference place, so here only the configuration method will be discussed.

As with all types of endpoints, page endpoints are setup in their endpoint.  So, let's start our example with the following endpoint:

<themelia.web>

  <webDomains>

    <add defaultPage="/Page_/Home/Home.aspx">

      <endpoints>

        <add selector="pathStartsWith" text="/contact/" type="Page" />

      </endpoints>

    </add>

  </webDomains>

</themelia.web>

At this point, the configuration is meaningless.  There's an endpoint, but there's nothing there to tell the endpoint how to handle the page endpoint.  To provide this information, we use the endpoint "parameter" attribute to specify which page we are going to use for this endpoint:

<themelia.web>

  <webDomains>

    <add defaultPage="/Page_/Home/Home.aspx">

      <endpoints>

        <add matchType="pathStartsWith" type="Page" text="/contact/" parameter="/Sequence_/Contact.aspx" />

      </endpoints>

    </add>

  </webDomains>

</themelia.web>

There's all there is to it.  Other endpoints types will use the parameter attribute for other things, but page endpoints use "parameter" to represent the target page.