That depends on several factors. Here are some pros and cons of each:

It is not recommended you do this because you may run into issues. For example, some changes were made in crypto_master.php and data/upgrader2.php prior to the first v11 alpha. These changes will result in a broken upgrade unless you already pulled these changes from git. Similar situations could happen in the future as well.

It is recommended you either discard the git install and use a fresh install from the Downloads, or to maintain a git install and a bleeding-edge release install separately. Do not combine the two.

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.

• Parameters: Placeholders for content passed to the template from Composr / PHP.
• Symbols: Global functions that perform operations, calculations, or retrieve information.
• Directives: Instructions that control the flow or logic of content, such as conditional statements and loops.
• Language strings: References to pre-defined text stored in language files for easy translation.
• Escaping: Ensures the content generated is properly escaped according to its use case.

• GIMP/GIMPShop: These free, open-source image editors provide a robust set of features comparable to Photoshop.
• Paint.NET: This free, Windows-only software offers a user-friendly interface and essential image editing tools.
• Corel Paint Shop Pro: A more affordable alternative to Photoshop, Corel Paint Shop Pro delivers a good balance of features and ease of use.

• Avoid using it as the sole backup method; rely on regular database backups.
• Work primarily under the "var" meta-filesystem and copy specific folders/files rather than the entire repository.
• Do not use tools like "rsync" or Git on the whole repository without careful consideration.

• Automatic syndication is not performed for content added via the repository.
• Multi-language content translations are not retained.
• Transferring complex data schemas between staging sites may have limitations.
• Merging separate websites into one is not supported through the repository. You should use Composr's import tool instead.

• bin: Stores Commandr scripts.
• database: Provides access to the raw database.
• etc: Allows access to Composr configuration options.
• home or filedump: Provides access to the File/Media Library.
  • home contains the files in a special JSON format with metadata
  • filedump contains the raw files
• members: Lists registered members with their settings and user groups.
• raw or root: Provides access to the Composr installation directory.
  • raw contains the raw files without overrides, and modifying any file modifies them directly without automatic override handling
  • root contains the files with applicable overrides applied automatically, and Composr will automatically handle overrides and utilizing _custom directories when these files are modified
• var: Contains structured website resources and content.

• Opacity: Provides a clear view of Composr's content and resource data.
• Tactility: Allows easy manipulation of data through drag-and-drop operations.
• Data transfer: Simplifies transferring data between sites.
• Desktop application integration: Enables using text editors and file-search tools for tasks like mass search and replace.
• Configuration management: Tracks changes to options and facilitates transfer between sites.
• Backups: Allows backing up portions of the repository.
• Revision control: Supports built-in and advanced revision control.
• Filesystem for Commandr: Acts as a file system for the Commandr command line.
• Resource API: Offers an abstract resource API for programmers.
• API for external apps: Provides an API for mobile apps and other external applications.