Web Export
Search…
Web Export
Introduction
Getting Started
Install the Plugin
Create or open a project
Export the Artboard
Export Artboard Dialog
Addressing Export Issues
Messages Console
Export types
Keyboard Shortcuts
Responsive Pages
Dynamical page that grows in height
Modifying Individual Elements
Elements and Sub Elements
Styling elements
Element Options
Changed Properties
How to section
Creating Code Blocks
How Exporting Works
Single Page Application API
Element Tokens
Template Tokens
Setting up a server
Putting your site online
Code Block Snippets
Other Features
Learning by Videos
WordPress Integration
Example Packages
Web Developers
Non Web Developers
Debugging
Version
Support
License
Feature and Bug Reports
Related Plugins
Powered By GitBook
Non Web Developers
A page for not web developers
Whatever your background, you can make a web page or a web site with some education and some basic skills. But there are a few things about creating web pages to keep in mind.
Creating a web page or web site is in a rough way a 3 step process.

Design the page > Write the code > Publish it online

In the design world and in Adobe XD what you see is what you get or WYSIWIG. In the development world what you get is what you see WYGIWYS.
In other words, the design software accurately reflects the design (at least on screen) but in development, the software or web page is the sum of many parts. Part code, part design, part browser, part internet, etc and they do not all come together in expected way.
Because designers of WYSIWYG applications typically have to account for a variety of different output devices, each of which has different capabilities, there are a number of problems that must be solved in each implementation. These can be seen as tradeoffs between multiple design goals, and hence applications that use different solutions may be suitable for different purposes.
WYSIWYG
Wikipedia
Assembling all those parts together often requires some knowledge of all of those fields of technology that make up the end product.
To help with that many tools in the software world will report back to you any problems that it encounters as you are building your project.
In fact, in coding environment there is often a Problems view or a console that shows you any problems in your code.
It's a way the computer (the compiler or the browser) replies back to you based on what you gave it.
Consider a robot that makes a cake. It requires that you give it those ingredients it needs in the order it needs them.
In the process of creating a cake with the robot the robot has a set of tasks that it does, some preprogrammed and you have a set of tasks that you do.
When you assemble all the parts together you have a web page or an app.
It is rare that you won't have any problems or issues in the process. The problems views or console will list out any of these issues.
Look for them and read them. Web Export lists any issues in it's own console after you export.
The process of finding and fixing bugs is called debugging.
Web Export will do most of the work for you and over time improve the quality of that work but it's has been designed to be flexible enough to allow you to add to it and modify it.
With some practice and education you will be able to author and build your own web applications.
Use the Web Developer tools that are built into modern day browsers, the problems views and resources like Lynda.com, StackOverflow, the Velara 3 discussion forums, and this guide to fix and address them.
Whether you are new to web development or a hobbyist read Getting Started with the Web on MDN.
Debugging HTML - Learn web development | MDN
What are browser developer tools? - Learn web development | MDN
Getting started with the Web - Learn web development | MDN
Previous
Web Developers
Next
Debugging
Last modified 2yr ago
Copy link