Skip to main content

Why People Use WordPress and Wix

The Internet as we know it is structured because of HTML, looks pretty because of CSS, and functions properly because of JavaScript. While this may be a somewhat basic view of web development as it exists today, these three components still reign king over any application or website built to be accessible over the Internet. Sure, there exist languages that generate HTML from a different set of syntax, but the goal of these tools is to make creating HTML easier, not to replace HTML altogether. And sure, most websites use some backend server to do most heavy calculations, but scripts are still needed on the website itself to communicate with this server and then properly display this information.

It’s a testament to the principles of design and abstraction, then, that we are able to create websites through means other than writing lines of code on an otherwise blank text file—especially considering that every instruction on the computer must be rendered as binary at the end of the whole process. Indeed, web creation tools such as Wix and WordPress not only make the website creation process seem visual instead of technical, but they also allow an audience who may not have any experience with web development to have a good chance at successfully creating the product they want. And yet, when many people continue to develop using technical code, and when websites created through this method are generally considered to be more flexible, responsive, and dependable than those created with tools such as the ones above, an outsider may wonder why we need these sorts of visual tools and how they can compete with HTML, CSS, and JavaScript development.

The answer, of course, generally comes down to one thing: technical unapproachability. As mentioned, a functioning website generally needs a multitude of components, and the design of the frontend will likely be only one part of the finished product. Because each of these components will likely communicate in a different way, even if one can design a good set of web pages to display using the languages discussed above, there still may be other components of the product that use different sets of conventions and syntax; each part of the website may therefore require significant time to learn and understand, and this sort of time is often not available in a real workplace.

After all, each new programming language can seem like a cipher to its users, especially to ones who are unfamiliar with the various concepts of computer logic. Along with learning what each keyword in a language does, users may also need to find relevant libraries to import certain functionalities or wrestle with the particulars of a data type within a certain language; this struggle can only increase when someone unfamiliar with coding tries to understand relatively established topics that are nonetheless unintuitive, such as the first element of a list being at the 0 position or a range of 1 to 5 oftentimes returning only four elements, starting at the second. Even though there do exist several tools that can help make coding more approachable, effectively using a programming language to design a complex website can still be difficult and frustrating.

Ultimately, most programming languages are not only hard to use if one doesn’t understand their syntax or conventions—they are also hard to understand if one doesn’t know where to look for or how to comprehend documentation about syntax, library calls, dependencies, and etc. Many languages are built to resemble how the machine thinks rather than the user, and since the user will not be a machine, it requires experience to comprehend the logic. The strengths of these languages instead lie in how much one can get a computer to do if they know the proper code, which is far more than a website creation application such as WordPress—but for many people who want to build basic websites that look good, this is generally not an issue. Instead, what these people want is a visual way to build a website, something that intuitively allows them to add content to a page and see it update correctly, even if the most advanced options are removed. By offering this to users who don’t have the time or experience to code a website by hand, website creation tools like Wix and WordPress therefore fill a strong niche and are able to thrive, even as they exist alongside technical website code.

Comments

Popular posts from this blog

Proposed Plan for Socially Distanced User Study of Wix.com

Plan for User Study: www.Wix.com I. Introduction Although a usability test is unlikely in this socially-distanced and pandemic-filled world, if I were to do one, this post describes how I would see myself doing it as well as a basic overview of my plan of study, had this been an option. II. Identifying Users 1. The users of this site align most with the age group of 20-35. This demographic uses Wix primarily for educational purpose and small business website platforms. 2. Users in this case will work through website creation, as that is the main function of the site. III. Target Identification of Problems Below are the main heuristics and an associated question to further explore the content of the site as I plan a User Study. A. Engagement Are the screen and workplace too crowded, and are they layered to maximize engagement? Is the site   nested too deeply with helpful tools to be useful? B. Error Tolerance Does the Help Desk analysis show enough specific problem de...

Design Surrounds Us

Despite surrounding us in every object that we own, encounter, and interact with, design is oftentimes an invisible sort of force. Good design generally directs the user without being overtly noticeable, which means that it is often easier for us to pick out elements of bad design—that is, we most often notice design when we’re frustrated or confused by it. However, when we feel these emotions, it is important to understand which aspect of a design has caused them. Sometimes the failure in design is not caused by the most obvious component; indeed, the design of a specific frustrating component may have been the best design available if there are external and unmalleable constraints that it had to work within. Noting which level a design fails at, then, will make addressing design concerns much more exact and relevant, as critiquing a specific frustration without addressing the wider problematic system brings about no progress. While perhaps not the most exciting topic, a strong exampl...

Think “Experience Architecture”

At the beginning of this class, we were assigned readings and videos about airports in order to conceptualize the main theme of the course, experience architecture. Experience architecture is the design of spaces (architecture) for users (experience), such as an airport. In de Botton's work, "A Week at the Airport," de Botton addresses a doubt about experience architecture that sheds light on the scope in which the concept applies. "Standing before costly objects of technological beauty, we may be tempted to reject the possibility of awe, for fear that we could grow stupid through admiration...[and] yet to refuse to be awed at all might in the end be merely another kind of foolishness. In a world full of a chaos and irregularity, the terminal seemed a worthy and intriguing refuge of elegance and logic." (de Botton, 2009, p. 3-4). Simply put, experience architecture is design that is meant for the experience of the user. De Botton communicates this through an exp...