What is Wrival?
Wrival was invented to provide the world with an easier way to do web development. The objective was to make custom processes and data be able to be easily used within the actual writing of content opposed to the content being inserted into programming. For the 99% of us that aren't running an enterprise-scale system it's an effective means of skipping the need for a back-end programmer. Or, at the very least it's a means of developing fully functional prototypes of web apps in no time at all. Wrival is a made up of a collection of the following:
- Wrival Insert Language (WIL) – Server-side data insertion and formatting.
- .wrival files are the type of files that are parsed (read and evaluated) by the Wrival compiler. Think of them as raw text or basic HTML files that can do a whole lot more.
- Wrival Inserts are just like HTML tags, but must contain a hash (#) at the beginning and they don't need to close. They may also be embedded inside of each other as well and the scope for them is automatic. Their purpose is to insert reusable content, including from database tables, server variables, and functions into the place in the content of where they were called. This is also known dynamic server-side data.
- Wrival Compiler – This is the engine that parses and evaluates everything for all .wrival file requests. It was made to run with FastCGI (also free), which loads the entire system into memory offering a fast and highly efficient web server environment for Wrival and it's easy to set up with Apache.
- Wrival CMS – The Wrival CMS is a browser-based Content Management System that makes working with WIL incredibly easy. Manage your website or app including all its data and processes, which also has a publishing system for previewing edits before they affect the live site or app.
- nojax.js – As an alternative to clicking on a link and having it load as a completely new page, with nojax.js, the link can instead fetch the request and put its content into an existing element of your choice (such as a <div>). It simply changes what a link's "target" attribute can be used for and does the AJAX automatically in the background for you. Go to nojax.org to learn more about this library.