Absolutely! Frequent changes may be made to both bundled and non-bundled addons. Bundled addons will be updated via the upgrader. For non-bundled addons, you will have to update them through the addons management screen (Admin Zone > Structure > Addons). You will be informed which ones need updated.

Once version 11 reaches release candidate, we do not expect frequent updates to non-bundled addons anymore. But it is still good practice to check after every update.

Yes, for basic non-custom v10 sites. However, expect some issues to arise in the process. And please report those issues to the tracker.

For v10 sites with non-bundled addons or customisations, upgrading to v11 will likely break the site until you update the non-bundled addons or temporarily remove the customisations.

We aim to have the upgrader fully functional for a large majority of types of sites and for sites using non-bundled addons by the time version 11 reaches release candidate stage.

We do not recommend upgrading production v10 sites at this time until v11 reaches stable.

Yes (probably). Always remember especially during alpha and beta phases that things can break. Please make backups first. And let us know on the issue tracker if an issue occurs.
 

Note: You cannot upgrade from 11 alpha to 11 beta without first upgrading to 11.alpha4 (if you are not already on 11.alpha4).

As of July 22, 2024, we entered beta status where our focus is now smashing bugs and stabilising the software. All planned features have been implemented for 11.0 (and most others deferred to 11.1 or later), though we may still merge in a few minor features or tweaks. The upgrader has been tested on a typical non-custom v10 site.

We will be releasing several beta versions in the beta phase.

We do not know when we will be able to release the first Release Candidate or stable versions at this time.

These plans are all subject to change without notice.

• Protocols: HTTP/HTTPS, FTP, SFTP, SMTP, IMAP, POP3, DNS, and others
• Data formats: XML, JSON, CSV, PHP's serialized format, iCalendar, and various image and archive formats
• Standards: Accessibility standards (WCAG, WAI-ARIA), metadata standards (Open Graph, schema.org, Dublin Core), and microformats
• Server-side technologies: PHP, SQL (for database interaction)
• Composr-specific technologies: Tempcode (template system), Comcode (content language), Page-links, Filtercode, Selectcode, and Language packs

• Automatic browser behavior: Browsers typically disable background images when printing.
• CSS print stylesheets: Composr utilizes CSS to define specific display rules for printed versions of pages, such as removing margins and hiding social media links.
• wide_print parameter: This parameter, activated through specific links or specifying it in the URL, further influences page layout for printing.

• Virtual Machines: Use virtual machines to run different operating systems and test various Internet Explorer versions.
• Device Emulation: Use built-in device emulation features in browsers like Chrome to simulate mobile devices.
• Online Testing Services: Employ commercial online testing services like BrowserStack to access a wide range of browsers and devices hosted in the cloud.
• Real Devices: Conduct testing on physical mobile devices for a more realistic user experience.

• Fonts and typography: Defining font families, sizes, weights, and styles.
• Colors and backgrounds: Setting colors for text, backgrounds, borders, and other elements.
• Layout and positioning: Controlling the placement and arrangement of elements on a page.
• Visual effects: Adding shadows, gradients, transitions, and other visual enhancements.

• Modify page layout: Change the arrangement and positioning of elements on a page.
• Add new content: Insert additional text, images, or other multimedia elements.
• Customize the appearance of existing elements: Change fonts, colors, sizes, and other visual styles.
• Integrate interactive features: Embed JavaScript code for dynamic functionality.

• Dynamic content updates: Modifying page content without requiring a full page reload.
• User interface enhancements: Creating interactive elements like dropdown menus, image sliders, and form validation.
• Animations and visual effects: Adding visual appeal and engaging user experiences.
• Asynchronous communication: Fetching data from, or sending data to, servers in the background without disrupting user interaction.

• Storage: Cookies are stored on the user's computer, while sessions are stored on the server.
• Expiration: Session cookies expire when the browser is closed, while persistent cookies have a set expiration date. Sessions typically expire after a period of inactivity.
• Data sensitivity: Sessions are generally used for more sensitive data, as the information is not stored on the user's computer and therefore less likely to be stolen by a hacker.

• User identification: Cookies can be used to identify a specific user, even if they are not logged in. This allows websites to remember user preferences, shopping cart contents, and other information.
• Tracking user behavior: Cookies can be used to track user behavior on a website, such as the pages they visit and the links they click. This information can be used to improve the website's design and content.
• Advertising: Cookies can be used to deliver targeted advertising to users based on their browsing history.

• Session cookies: These cookies are temporary and are deleted when the user closes their web browser. They are often used to store information about the user's current session, such as the items in their shopping cart.
• Persistent cookies: These cookies are stored on the user's computer for a longer period. They can be used to remember user preferences, such as their login details or language settings.