Other features

Core.web’s complete list of features actually reads like Tolstoy’s War and Peace. To keep things short, sweet and to the point, without spending too much time, space and bandwidth, we’ve decided to list some of the remaining features here:

Human-readable, search-engine-friendly URIs & auto meta-tags
Links generated inside the core.web framework have a form similar to this: http(s)://domain/(language)/something/something-else. This increases the URI’s readability and memorability, but it also greatly improves search engine indexing (and search engine ranking – as a direct result of the search engine’s ability to index the entire site). Meta tags for the core.web generated pages are created automatically from the actual content of the generated page, using an algorithm similar to the one search engines use when scanning web sites. The option of manually specifying meta information is available upon request.

Gzipped output
Content generated through core.web is transparently compressed before being sent to the browser, using something called gzip output buffering. If a browser doesn’t support that feature (but all modern browsers do), it receives non-compressed content. The gain of such compression can be huge, especially for text-based content. You can read more about it, and test any site’s requested page sizes with and without gzip compression

Web standards compliance
Core.web generated content strives to be web standards compliant. If you as a client have something against that, and wish for your site to be rendered in quirks mode, have tons of nested tables for layout purposes and other generally bad coding practices – we’ve learned to live with that occasionally, but we’ll do our best to try to convince you that it’s not a good idea. Sorry.

XML / XSLT / XMLRPC / XMLHttpRequest / RSS / Atom / insert other fancy new buzzword here
Core.web knows about these. It can use them if required. We’ve developed several custom implementations of fetching, parsing and/or transforming content from remote locations. Publishing content to remote locations, importing and/or exporting XML based content is no deal breaker either. We did it in various forms, using various technologies.
However, we’re not pushing the use of all these by default, since they’re not always needed, some are still being actively developed and standardized, and often serve a single specific purpose. Nonetheless, if you need it, you can have it.

Printer friendly pages
Content published on your site may often end up being printed. There’s no need for your site’s visitors to print screen-specific content. If they decide to print a page, they’ll print just what they need, without the superfluous graphics and screen-specific content, with a clear indication of where they printed it from, so they can return for more. It can be achieved with merely a separate print stylesheet, or a completely different printing layout template. You choose.

Intranet / extranet / business solutions
Core.web is a framework for developing web applications and web sites. Being such a cool framework, it can be deployed in practically any environment. Therefore, intranets, extranets and other business solutions can and have already been developed on top of it. Recent projects include: a hospital lab results and diagnosis management application, stock data archive and analysis, and several intranet installations for couple of small companies who use it as their internal content management solutions.