This provides a partial overview of the most important parts of Appframe Web structure. The most important components in an Appframe Web Site can be divided into general site components and apps.
Templates, scripts and stylesheets all have a test version and production version.
This allows you to test things before pushing them out to clients.
All sites will typically be configured with both test
and production domains. For example
Current changes to an article/app will show on your test server. To push changes to the production server you must publish the app. This will also create a version of that app. It is a good idea to always comment the changes you did to the app.
Appframe web apps are called articles. When your browser requests
an URL for the Appframe server, it identifies the article name using the last part of
the URL before a query string or hash, like this
mydomain.com/abc/APPNAME?foo=bar or this
mydomain.com/abc/APPNAME#Filter-dsSaker%3D%26page%3D0. If no article name
is supplied, it will use the StartUp article instead.
When rendering the article on the server, it will load the specified or default
template for that article. In the template, the razor expression
@Render("ArticleBody") will decide where in the template the article
itself is rendered.
Both the template and the article are rendered using Razor. The most common usage of
Razor in the article is to structure parts, using HTML Blocks such as
@Render("Block", ID: "someBlockID"), but it can also be used for rendering
The server also provides an API for data and other services.
refreshDataSource() on a data object makes this data object fetch
the specified data and render any HTML registered with this data object.
The data object sets up a two-way binding so you can also save changes back to the
Placeholder "LocalizeWeb2016" failed