Adobe Certified Professional Dreamweaver cheat sheet

A Dreamweaver site has two parts: a local site folder (working copies) and a remote server folder defined in the Site Setup dialog.

Site > New Site opens Site Setup, which collects Site Name, Local Site Folder, and Servers settings into a single site definition.

The Files panel reads the local site folder; changes appear only after saving files to that folder, not to the server.

Server settings require a connection method: FTP, SFTP, FTPS, WebDAV, or Local/Network; SFTP is required for SSH-based hosting.

Testing Server settings are needed only for server-side pages (e.g., PHP); static HTML pages do not require them.

Check In/Check Out and cloaking are site-wide options that prevent accidental overwrites and exclude folders from Get/Put.

Get copies remote to local; Put copies local to remote; Sync compares timestamps and transfers only differing files.

A relative link path resolves from the current document; a site-root-relative path begins with / and resolves from the server root.

The HTML document skeleton is doctype, html, head (metadata, title, link, script), and body (rendered content).

triggers standards mode; omitting it can trigger quirks mode in browsers.

Block elements (div, p, h1-h6, ul, header) start on a new line; inline elements (span, a, em, strong) flow within text.

The head contains title, meta charset, meta viewport, link rel=stylesheet, and script; none of these render as visible body content.

Semantic elements header, nav, main, section, article, aside, and footer describe page regions and aid accessibility.

An img element requires src and alt; a missing alt attribute fails accessibility validation.

Lists nest as ul/ol containing li; a description list uses dl with dt (term) and dd (description) pairs.

Tables use table, tr, th/td, with thead and tbody for structure; th marks header cells and carries scope.

Cascade order (low to high): browser defaults, author styles, then user styles; among author rules, specificity then source order decide.

Specificity weights: inline style (1,0,0,0); ID (0,1,0,0); class/attribute/pseudo-class (0,0,1,0); element/pseudo-element (0,0,0,1).

!important overrides normal declarations in the cascade and should be reserved for exceptions.

The box model is content, padding, border, margin; box-sizing: border-box makes width include padding and border.

The CSS Designer panel creates and edits selectors, properties, and media queries, and links external stylesheets.

Class selectors begin with a period (.note); ID selectors begin with a hash (#header); element selectors use the tag name.

Pseudo-classes such as :hover, :focus, and :nth-child select states or positions, not fixed markup.

External stylesheets are linked with ; @import inside CSS loads dependent stylesheets.

The viewport meta tag is required for correct mobile scaling.

Media queries use @media (min-width: 768px) { ... } to apply rules above a breakpoint; min-width is mobile-first.

Flexbox (display:flex) distributes items along one axis via justify-content (main) and align-items (cross).

CSS Grid (display:grid) defines rows and columns with grid-template-columns and places items by line or area.

position: relative offsets from normal flow; absolute positions against the nearest positioned ancestor; fixed pins to the viewport.

float removes an element from normal flow and wraps inline content; clear or a clearfix restores container height.

z-index orders positioned elements; it has no effect on elements with position: static.

Responsive images use max-width:100% and height:auto, or srcset with sizes for resolution switching.

The Assets panel catalogs images, colors, URLs, and library items found inside the defined local site folder.

Library items (.lbi) store reusable markup; editing the source updates every page that uses the item on save.

Templates (.dwt) define locked and editable regions; pages created from a template update when the template changes.

Images should be optimized before import; Dreamweaver can resize visually but does not resample the original file.

The Files panel Put operation uploads dependent files (images, CSS, scripts) when prompted, keeping links intact.

Broken links are found with Link Checker (Site > Check Links Sitewide); it reports broken, external, and orphaned files.

Preview in Browser uses a temporary local file; server-side features require testing through the testing server URL.

Publishing workflow: save locally, run link check, Put to remote, then verify the live URL in a browser.