Sitemaker CMS℠ Tutorial
FAQ: Overview
Build from "scratch" with components. Enhance with HTML & CSS.
Index
Definition
Question: What is a "standard" page?
Answer: SM "pages" are assembled with "components" like text, graphics, lists and pre-configured forms called containers and column sets (grid, flex formats). Text components may include HTML/CSS specifications, so a skilled user can freely enhance the automated content.
Components can be pushed to their desired locations; they follow the usual rules of webpage construction as to sequence and justification.
Components can be pushed to their desired locations; they follow the usual rules of webpage construction as to sequence and justification.
[ Back... ]
Question: What is a Sitemaker component?
Answer: Components are pre-built code blocks that you can place on standard pages. Place them on a page in "logical HTML order" and they will behave as hand-coded sections, automatically conforming to HTML's layout rules. You can also modify the behavior of components and their contents using cascading style sheets (CSs).
Some examples are components that contain text, graphics, links, videos, etc. Using components is normally faster than hand-coding such comments. See the Components section of this FAQ for more detail.
Some examples are components that contain text, graphics, links, videos, etc. Using components is normally faster than hand-coding such comments. See the Components section of this FAQ for more detail.
[ Back... ]
Access
Who may see or change what in editing, public or member views.
Question: What is the system's general privacy standard?
Answer: Tools have privacy settings managed by individual and group permission lists. Other pages may be set by the site owner-editor(s) to author, group, member or public privacy levels. Throughout, privacy settings set by default to maximum at initialization; site owners may adjust privacy settings with appropriate statements of actual privacy levels. Hosts and the Sitemaker Team are not responsible for results of relaxation of security provisions by site owner-operators.
To effect this standard, certain combinations of HTML/CSS are not supported by Sitemaker.
To effect this standard, certain combinations of HTML/CSS are not supported by Sitemaker.
[ Back... ]
Question: How can I improve utility for users with visual disabilities?
Answer: Enhancing accessibility for blind users involves combining best practices in web development with awareness of how assistive technologies, such as screen readers, interact with your site. Here are three actionable strategies:
1. Ensure Proper Use of Semantic HTML
- Use headings (h1-h6) to structure content logically.
- Mark up lists, tables, and navigation menus semantically.
- Provide descriptive title and alt attributes for each page and all images.
- Use landmarks like nav, main, aside, and footer to help screen reader navigation.
- Avoid using div or span tags for important content structure unless necessary.
2. Implement ARIA (Accessible Rich Internet Applications) Attributes
- Add relevant ARIA roles and states to dynamic elements (dialogs, sliders, tabs).
- Use aria-label or aria-labelledby on elements that lack clear text labels.
- Mark non-essential decorative elements with aria-hidden="true" to prevent screen reader notification.
- Regularly test ARIA usage with screen readers to ensure clarity and proper function.
3. Optimize Keyboard Navigation and Focus Management
- Ensure all interactive components (forms, menus, buttons) can be operated via keyboard (tab, arrow keys, etc.).
- Display visible focus indicators for interactive elements.
- Use logical tab order and avoid keyboard traps.
- Programmatically manage focus for dynamic content updates (e.g., after form submission or opening modals) using JavaScript to set focus() appropriately.
Implementing these improvements ensures a more inclusive website experience for blind users, especially when tested in combination with popular screen readers such as JAWS, NVDA, or VoiceOver.
W3C Accessibility Guidelines
WebAIM – Basic Screen Reader Support
MDN – Keyboard accessibility recommendations
[ Back... ]
Tools
Links to individual FAQs for Sitemaker tools. Most tools require a basic understanding of the other following attributes of the system.
Plain Text
This section explains how to add plain text to a text component.
Question: How do I construct a unique page?
Answer: Editing an open-layout page in SitemakerCMS℠
1. Sign in.
2. Open the page list and click the page under Page Code. You may also click New Page. The page layout will appear; initially it will be empty; existing pages will display their contents and some editing links.
3. Scroll to the component you wish to edit.
4. Click the Edit link in the control bar below the component. An editing form will open. Each component type has its own form with appropriate settings and content options.
5. Type/paste, etc., your changes and save the form. The changes will be immediately reflected on the website. Review the public view before making other changes; revise as needed.
6. To delete a component click the puzzle piece with the red stroke.
7. To add a component, scroll to the component directly above and click the Add link (puzzle piece with plus sign). To add a component in first position click the similar button near top right.
8. A small number in each control bar shows the logical sequence of the components. Reorder components by clicking the Up/Down or Left-Center-Right-None buttons."None" will let the user’s browser position the component in web-standard fashion.
Always review each change before proceeding to another.
The forms are intended to be self-explanatory, but if unclear ask your representative.
1. Sign in.
2. Open the page list and click the page under Page Code. You may also click New Page. The page layout will appear; initially it will be empty; existing pages will display their contents and some editing links.
3. Scroll to the component you wish to edit.
4. Click the Edit link in the control bar below the component. An editing form will open. Each component type has its own form with appropriate settings and content options.
5. Type/paste, etc., your changes and save the form. The changes will be immediately reflected on the website. Review the public view before making other changes; revise as needed.
6. To delete a component click the puzzle piece with the red stroke.
7. To add a component, scroll to the component directly above and click the Add link (puzzle piece with plus sign). To add a component in first position click the similar button near top right.
8. A small number in each control bar shows the logical sequence of the components. Reorder components by clicking the Up/Down or Left-Center-Right-None buttons."None" will let the user’s browser position the component in web-standard fashion.
Always review each change before proceeding to another.
The forms are intended to be self-explanatory, but if unclear ask your representative.
[ Back... ]
Miscellaneous
Question: Can I distribute non-Sitemaker documents (e.g., PDF, MP3s) from my site?
Answer: If you have opted for Premium service, you have an ancillary storage folder that is intended for such materials. You can link any page and most tools to make the saved files available to your users. Click on the Files tab in the Editing Suite's main function bar for details.
[ Back... ]
Question: What is the most foolish thing ever said by a politician from Texas?
Answer: The leading candidate in most years is Ma (or Pa) Ferguson's 1920s assertion, "If English was good enough for Jesus Christ, it's good enough for Texas schoolchildren." Some 21st Century speakers have posed strong challenges.