We are in the process of updating the WebEdit documentation. Though, some of the content below might still be applicable to your needs.
An asset is any entity within the system that can be used to generate content. For ease of classification, assets are divided into several different groups, such as:
- Folder– A container within WebEdit that contains a group of related assets. From the Dashboard, the Asset Tree to the left is where your folders and all the assets in the system appear. Clicking on a folder or the “-“ icon next to the folder will expand the folder view in the asset tree, revealing the assets and/or subfolder(s) inside. Additionally, clicking on a folder from the asset tree will open it in the main viewing area as well.
- Page – A core asset built by WebEdit. It represents the grouping of several items together such as content and files. Pages are the grouping of these items that a user publishes out to display new web content. Essentially, your ‘page’ becomes a new web page. Pages can represent many different types of content on a website. Pages can be frequently asked questions (FAQs), Event Calendars, news articles, faculty/staff profiles, news articles, simple content, and anything else you might find on online.
- File – Files are typically created by external programs and imported for use in WebEdit. They may be an image (.jpg, .gif., etc.), Document (.doc, .xls) or Pdf (.pdf)
- External link – an asset that points to a specific URL outside of WebEdit. As it is an indexable asset, an external link is useful when there is a need to include external pages in a dynamic navigation menu.
- Reference – A special asset that is created to represent an existing asset in another location, allowing it to be indexed in multiple folders. While a single asset appears in navigation as if it were in multiple locations, in actuality, it directs back to the original asset.
The system asset tree is the list of assets (files, pages, folders) located at the very left side bar. In Willamette's WebEdit system, the Base folder is top asset located in the tree, however, the bulk of Willamette's assets are located inside the folder www.willamette.edu.
Navigation menus on websites are typically a graphical view of a site's hierarchy. When pages are added, deleted, moved, or renamed, all corresponding links need to be updated on the navigation menus throughout the site. The Left Nav allows a navigation menu to update automatically, based on the state of a website's content.
The Left Nav directly corresponds to the system tree based on ordering, indexing and publishing.
The personalized home area upon logging into WebEdit. The dashboard is used as a starting location, tracking information such as the history and recycle bin. It also summarizes WebEdit activity relevant to the user.
Publishing works at taking new assets and copying them to the live Willamette web site. Upon the publishing of content, the information is completely decoupled from the WebEdit system, allowing it to operate independently in any standard environment. Essentially, this allows these assets to appear publicly.
Additionally, for assets already created that have been edited, it is necessary to publish them again. Submitting a page is the equivalent of saving the information to the WebEdit system. However, the changes made to the assets are not seen on the live site until the page is re-published.
The folder that an asset (subfolder, page, etc.) lives in.
The default page for a parent folder. This is the automatic homepage for a folder.
WYSIWYG is an acronym for “What You See Is What You Get.” WebEdit’s word processing functionality is referred to as the WYSIWYG editor because as its name implies, it allows you to see formatting while editing in your content in the word processor (much like Microsoft Word®).
Anything within WebEdit.
Anything outside of the WebEdit.
Metadata is data within WebEdit that describes an Asset. Common fields such as title, summary, or keywords provide quick information about the content contained inside of a particular Asset. Because the system manages all assets as XML, the Metadata that a user enters for Assets can be used for display purposes on site pages.
Willamette’s primary uses of the metadata are for display in the left navigation and titles.
WebEdit maintains a full version history on each asset in the system. As changes (specifically, submissions) are made to any asset in the system, WebEdit keeps track of the changes in separate copies of the asset called Versions. These are accessible through the More tab and selecting “Versions” from the drop-down.
The versions list for each asset shows a list of each version, the author for each change, including the original creator of the asset, as well as the time and date of the change and any notes available. Users may navigate through the various versions, compare them with the current version, and activate any version desired. This will replace the current version.
Drafts are separate entities from the current page, used for content that is incomplete or needs review before officially saving over (submitting) the current page's content. If the revisions are not needed, the draft can simply be discarded, not affecting the current page's content.
A path points to an asset by following the hierarchy expressed in the system/asset tree. Essentially, the path is the URL.
Breadcrumbs are a type of Navigation typically used for every page except the home page. By showing a navigation trail from the home page to the current page, breadcrumbs ensure that users know where they are and how they got there. For Willamette’s website, the breadcrumbs can be viewed at the top of every page.
A Staging Server is a web server used to test the various components of, or changes to a web site before propagating them to a production server. This server is viewed by the web editor, but is not public.
A Production Server is a web server that delivers what is often called the "live site." It is typically available to the entire web and houses the most recent version of its respective site. This is where a published product will be displayed publicly.
Similar to a computer’s “Trash”, the Recycle Bin temporarily stores recently deleted assets (for 15 days). Assets in the Recycle Bin can be restored to their original location or purged from the system permanently either one at-a-time or in bulk.