The WixAbout the Wix
We use a simple example of an arts college in this paper that collects and shows information about its classes and coaches. The Wix Code data base consists of single table, which we calllections. We have two collection in our example of the arts college (see picture below), one each for the course and teacher.
Any number of columns can be created and filled with an almost unlimited amount of information. They can work directly with your real-time information, i.e. the information your users see when they visit your pages. And you can work with sandbox files so you can try things without affecting your site.
There are several ways to fill your collection. Wix Content Manager allows you to input your content directly, either into your online or sandbox files. When you are an Excel-Ass, you can do all the work in Excel (or any other spread drawing application you prefer), store your sheets as a CSV document, and then bring them into the Wix Code base.
Actually, you can build your whole library this way, with scheme and everything else. Now you can add your sandbox dates to your sandbox or your lives. It is also possible to extract your Wix file to CSV file. When you make sure you use the built-in ID system array, you can change your contents in your spreadsheet before importing them back into your Wix code base so that any records or what we call an element are up-dated.
The third way is to create a template to collect information from users and save it in your databases. So if you already have a data base somewhere, you might think you don't want to rebuild it in Wix. So long as your data base provides an api you can connect to it from your Wix site.
You can use the wix-fetch engine - an implement of the default script Fetch API - for basic tasks to connect to your remote databases with an HTTP query and use this information on the pages of your Wix site. You can use the features provided by these two engines to build SEO-friendly pages that display different types of information based on the type of URL you are using.
You can use wix-router and wix-fetch to type codes that get information from input inquiries for the profiles page, query an outside databank to get the information for the page, and then insert that information into the profiles page. Easily apply hook to action in your collection using the wix-data API. Now you can create and edit wix-data action files.
As an example, we have two separated boxes in our teacher collection: In order to facilitate the display of name on our pages, we also want to have a box containing both of them. For this purpose we can create a beforeInsert-Hook in our teacher-group, which inserts itself into the insertspace, reading the content of the boxes Firstname and Lastname, concatenating them and filling the box Full name.
After we have done the covering of the Wix Code base ourselves, let's discuss the modelling of your Wix Code base with you. As with all collections, each library has a scheme for defining its own cells. Supports all default box styles, as well as text, picture, Boolean text, number, date and hour, and Rich Text. Also there is a special kind of input that has been developed for the URL.
So for example, a teacher in your institution could specify the address of their web site and you could add this hyperlink to their website. Also, you can use the Documents box to save a variety of different kinds of documents. They can allow your learners to either allow you to browse your collection of data (e.g. read list for each course) or to allow your learners to browse and view their own data.
Every compilation has a _ID box, which is the prime identifier for this one. Collectors also have a prime box (identified by a padlock symbol), which is the ad code for each element. If you use referenced entry fields to make a join (see next section), the system takes the data from the source entry area.
Of course, the actual referencing itself uses the _ID box. When planning to use referenced arrays, it is advisable to ensure that the information you save in the main array is unambiguous. References link together collectibles that are already specified in the collective procedure itself. Every referenced box points to a particular set.
From the value of the main box of the referred set, the value shown in the target box in each element of the set is taken. For our example, we have set up a referee box in our course library that refers to our teacher library so that we can indicate who is teaching each group.
There are three advantages to using referential arrays. Firstly, they help preserve information integrity by taking their value directly from the referred set. Secondly, they help avoid duplicate datasets that we all know are the foe of good DBDesigns. Third, when we build our page layout, our references give us the ability to retrieve information from both the referred compilation and the primary compilation we use.
It allows us to build detailed pages for the masters, such as a listing of all the classes given by each one. Naturally, the storage and maintenance of information is beautiful, but the actual purpose of a website is to display contents to you. Uh, so let's just discuss how that works with Wix Code.
There are two different kinds of information: course and teacher. You could therefore begin by creating a page design that displays all the information about each course. You might want to make a detailed page for your Master's, listing all your instructors and the classes they are teaching. If you are creating dynamical pages in Wix Code, first specify the content that your page is allowed to view by defining the first URL.
You can specify a unique element for some URIs and an overall element class for others (for example, all classes at a specific level). Configure the layout by selecting one (or more) of your collection's boxes. For example, a sample that you can use to view any of your classes could be https://.../Courses/.
Every and every times another page is created, the box is substituted with the real name of the page called. Then, you create your page layouts in the Editor by placing various items on the page and linking the items you want to use to view your dynamically changing information to boxes in your library.
Below is an example of how a page design for our course page might look in the editor. Some of the content of the items has, however, been superseded by information about the course from our databank. In particular, notice how the name and photo of the tutor of each course appear on the page, although the detail for each tutor is saved in a seperate set of course information.
One more great thing you can do with Wix Code is creating detailed pages of masters. You can, for example, make a page that serves as an index that will list all the tutors in your institution and the classes they teach. To do this, information from more than one set (courses and teachers) would have to be retrieved and the course filtered by instructor so that only the pertinent course is shown.
All our databases are structured in a multifaceted way; each instructor has many different classes to offer. While above we have presented each course and its personal instructor, now we go the other way and show each instructor and all their work. Linked to both our course and our instructor libraries, the repetater can show information from both libraries in a dynamic way.
Each repetition element's built-in spreadsheet feature shows the course lists each Tutor is teaching. We' ve presented some high-level information about the Wix code base and some of the ways it provides to store your information, manipulate your information, and display your information to your users in a dynamic way. We have also demonstrated how the choices you have are partly driven by the choices you make when creating and connecting your collection.
It is a good suggestion to think about what kind of information you have and how you want to view it before you start building your Wix code base so that you can best mold your work.