This is just a placeholder site for Composr CMS 11 beta. It will become the new homesite once version 11 reaches stable. For the current v10 homesite, click here. Please also use the v10 tracker to report v11 issues.

Contributors: A-Z Index

A

Name	Photograph	Title / Role	Contributions / Notes
Allen Ellis		Founder	Original designer for ocPortal Also conceived and coded the Theme Wizard and Point Store Son of one of the early inventors of Internet protocols (Usenet, aka Internet newsgroups) Token non-brit	View

C

Name	Photograph	Title / Role	Contributions / Notes
Chris Graham		Founder	Original developer of ocPortal, former lead developer of Composr CMS Masters degree in Computer Science from The University Of Sheffield Undertaken work for over 15 FTSE-100 companies, as well as many small and mid-sized organisations. Includes a number of banks and major brands.	View
Chris Warburton		developer for ocProducts	Made some key contributions to ocPortal	View

H

Name	Photograph	Title / Role	Contributions / Notes
Haydn Maidment		project manager for ocProducts	None available	View

J

Name	Photograph	Title / Role	Contributions / Notes
Jim Davidson		contributor	written many tutorials via Arvixe	View

P

Name	Photograph	Title / Role	Contributions / Notes
Patrick Schmalstig		Lead Developer	Joined Chris Graham behind the scenes in the development of Composr CMS in 2016. Took on the lead developer role in 2023 when Chris Graham stepped back to attend to his new lifestyle changes. Spearheaded the development of Composr CMS v11 and the new website, Composr.app. Formed the company PDStig, LLC to take on professional support and development for Composr CMS users especially after the discontinuation of ocProducts, Ltd.	View
Philip Withnall		Early Developer	Coded the chatroom, blogging support, the analytics system, and OcCLE (now Commandr) Masters Degree in Computer Science degree from The University Of Cambridge Other work has included helping out with Firefox, and ongoing work on GNOME	View

R

Name	Photograph	Title / Role	Contributions / Notes
Robert Goacher		Founder	Ran some of the early websites where ocPortal came from Technically the original developer of ocPortal, in that he wrote the first few lines of code Heavily involved in the feature design process Hosted some of our early meet-ups	View

S

Name	Photograph	Title / Role	Contributions / Notes
Steve Jarvis		project manager for ocProducts	Wrote many tutorials via Arvixe	View

Newest 10 Entries

Question	Why does Composr use pre-computed statistics?
Answer	Composr generates statistics from pre-computed data for several reasons: GDPR compliance: Prevents indefinite storage of raw (potentially personal) data while preserving historical statistics. Computational efficiency: Avoids real-time execution of complex calculations, ensuring optimal performance. Scalability: Handles vast amounts of data without performance degradation. Responsiveness: Enables quick and seamless statistics browsing and filtering. Data accessibility: Makes generated data readily available for other Composr components.

Question	What are KPIs and how are they used in Composr?
Answer	KPIs (Key Performance Indicators) are specific measurements selected for marketing analysis. In Composr, time-series graphs can be added as KPIs. They offer several benefits: Quick reference: Available on the Admin Zone dashboard staff checklist. Target setting: Allows setting targets against KPIs, visualized on graphs and in overview summaries. Notifications: Staff members receive regular notifications regarding target achievement status.

Question	How can I perform split testing in Composr?
Answer	Split testing in Composr involves combining tracking codes with events. The simplest approach utilizes Tempcode: Random tracking code: Choose a random tracking code from a set and activate it for the user session. Conditional output: Generate different content variations based on the active tracking code. Subsequently, you can analyze event success rates based on the assigned tracking codes, utilizing both inbuilt events and custom-created events.

Question	What is the purpose of tracking codes in Composr?
Answer	Tracking codes help you identify the sources driving user sessions to your website or associate specific split testing variations with users. Composr offers integrated referral tracking through various means: URL parameter: The _t URL parameter can contain any custom tracking code, automatically registered by the stats addon. Recommend addon: This addon automatically includes tracking codes for the referral source, referring member, and the referred page. Member joining: When a referred member joins, the referring member receives points and a friend request. Referrals addon: Allows manual tracking code input upon joining and facilitates a referrer reward system. Stats addon: Generates graphs of tracking codes, including conversion rate measurements. User lookup tool: Allows checking if a user accessed the site via a tracking code. Tempcode integration: Inject tracking codes into Tempcode using symbols like `{$SET_TRACKING_CODE,some code}` or `{$SPLIT_TEST,some code,some other code}`.

Question	What are the different ways to track events in Composr?
Answer	Composr offers various methods for tracking events: Inbuilt events: Automatically recorded for actions like form submissions, purchases, newsletter signups, etc. Tempcode symbol: Use the `{$LOG_STATS_EVENT,event}` symbol within your templates to track events when the template is displayed. JavaScript function: Employ the `$cms.statsEventTrack` JavaScript function to track events from within your JavaScript code. HTML data attribute: Add `data-click-stats-event-track="{ category: 'some event', nativeTracking: true }"` to HTML elements. This method acts as a wrapper for the JavaScript function. URL wrapping: Wrap URLs in links using the `{$STATS_TRACK_URL,URL,event}` symbol. This approach records events via a redirection script and doesn't rely on JavaScript. The JavaScript and HTML data attribute methods can also be integrated with Google Analytics events.

Question	How do I install geo-location data for Composr statistics?
Answer	Geo-location data installation is usually automatic during the Composr installation process. If not, you can manually install it by navigating to Admin Zone > Audit > Site statistics > Install geolocation data. This action will reschedule the installation task. If you don't see this option, the geo-location data is already installed.

Question	What are the key differences between Google Analytics and Composr statistics?
Answer	While there is some overlap, Composr statistics and Google Analytics are complementary tools. Google Analytics Pros: Offers sophisticated functionality for professional marketers. Integrates with other Google products like AdSense and Search Console. Provides insights based on Google's marketing data, such as visitor demographics. Google Analytics Cons: Limited to web visit data unless custom programming or complex configuration is implemented. Relies on JavaScript for tracking, which can be blocked by users. Uses tracking cookies, raising privacy concerns and potential GDPR compliance issues. Data is potentially sold to third-party data brokers or used for targeted advertising by Google. Closed-source platform. Composr Statistics Pros: Server-side tracking, independent of JavaScript and browser configurations. Contextual information and graphs for data beyond web visits (e.g., sales). Enhanced privacy as it only uses IP addresses, session IDs, and member IDs. Complete data control as it is hosted on your website. Open-source addon, fully customizable. Basic users may find Composr statistics sufficient, while expert marketers might prefer the power of Google Analytics.

Question	What tools and strategies can be used for staff training and development?
Answer	While Composr itself doesn't provide built-in training features, several approaches can be used for staff development: Documentation & Tutorials: Utilize the extensive Composr documentation and tutorials available online to familiarize staff with the platform's functionalities. Mentorship: Pair experienced staff with newcomers to provide guidance and support during the initial learning phase. Private Forums & Chat: Create dedicated communication channels where staff can exchange knowledge, ask questions, and share best practices. Regular Meetings: Conduct regular staff meetings to discuss updates, share information, and address any arising challenges. External Resources: Leverage external resources like online courses or workshops focused on relevant skills, such as content management or community moderation. By investing in ongoing staff training and development, communities can ensure their teams possess the necessary knowledge and skills to perform their roles effectively and contribute to the platform's overall success.

Question	How can potential conflicts between staff members be avoided (regarding content moderation)?
Answer	Composr incorporates "conflict detection" features to prevent staff from accidentally overwriting each other's work. When multiple staff members attempt to edit the same resource simultaneously, a warning message appears, prompting communication and coordination. Open communication and transparency are crucial. Encourage staff to share their ongoing tasks and plans with each other to prevent overlaps and potential conflicts. Utilizing shared tools like the staff checklist and private forums can further facilitate coordination.

Question	What should be considered when assigning roles and responsibilities to staff?
Answer	When assigning roles, it's recommended to start new staff with limited responsibilities and gradually increase their authority based on performance and dedication. This fosters a sense of progression and prevents discouragement among existing staff. Always consider the individual's skills and interests when assigning tasks. For example, someone with strong writing skills might be well-suited for managing content creation, while a technically-minded person could excel at site maintenance.

Top 10 Entries

Question	How do I change my website's logo?
Answer	You can change your site's logo manually or by using the Logo Wizard. To change it manually, go to Admin Zone > Style > Themes. Choose "logo/-logo" from the dropdown list, which represents the logo for the Welcome Zone and any zone without a specific logo. Replace the current image by uploading a new .jpeg, .gif, or .png file. Ensure that the 'Name' field remains unchanged.

Question	What are Composr addons and how do I manage them?
Answer	Composr is built using a series of addons that provide different functionalities. All "bundled" addons are installed by default. Once you are familiar with Composr, it's recommended to remove any bundled addons you don't need to simplify your site and prevent accidental exposure of unconfigured features to visitors (the Setup Wizard can also uninstall these addons based on your preferences). You can manage addons by navigating to Admin Zone > Structure > Addons. Uninstalled addons are archived and can be restored later, but any associated data will be permanently lost. Composr also offers non-bundled addons. These addons are not bundled because they are not considered mainstream, rely on third-party services, haven't been vetted to Composr standards, or don't fully conform to those standards. You can install non-bundled addons by going to Admin Zone > Structure > Addons, scrolling to the bottom and clicking "Import non-bundled addon(s)". You will need to browse to the addon file and click the import button. Once imported, review the warnings and proceed to install the addon. You can also download and import addons from this website under the Downloads section.

Question	What are some of the default Comcode pages in Composr?
Answer	Composr includes several default Comcode pages, each serving a specific purpose: home (Welcome and Site zones): The default front pages for the respective zones. sitemap (Welcome zone): Displays the sitemap, typically generated automatically. _rules (Welcome zone): Outlines the site rules, also displayed during registration. The "rules" page (no underscore) is a wrapper for this page. privacy (Welcome zone): Provides privacy policy information. By default, this is generated automatically with Composr's privacy policy generator block. 404 (Welcome zone): The page shown for 404 errors (page not found) and includes a sitemap. help (Site zone): Contains general help information. userguide_comcode (Site zone): A basic guide to Comcode for users. Remember that you can edit these default pages or create entirely new ones to tailor your site's content to your specific needs.

Question	How do I hide a Comcode page from the sitemap?
Answer	If you want to prevent a Comcode page from appearing in your sitemap, you can simply prefix its name with an underscore (_). For example, pages named "_test" or "_example" would be excluded from the sitemap. Note that this generally does not hide the page from your site itself (to do that, use the validation addon to turn validated to "OFF" for the pages); it only hides them from the sitemap / search engines.

Question	Can I organize Comcode pages in a hierarchical structure?
Answer	Yes, Composr allows you to simulate a hierarchical structure for your Comcode pages using multi-part paths in the page monikers. By editing the page monikers to include slashes (e.g., "about/team"), you can create a virtual directory structure within a single zone, enhancing your site's organization and navigation.

Question	How do I embed content from other modules into a Comcode page?
Answer	You can use various blocks to embed content from different modules: main_content block: Allows you to feature individual entries from modules/content like news or articles. main_multi_content, main_cc_embed, main_gallery_embed, main_news blocks: Enable you to pull in and display multiple entries based on categories or other criteria. main_include_module block: Provides a powerful way to integrate any module screen directly into a Comcode page.

Question	What is the difference between blocks and boxes in Composr?
Answer	While both terms may seem similar, they have distinct meanings in Composr: Blocks are functional units that generate dynamic content or provide specific features. They don't inherently have a visual form and their output can vary widely. Boxes are a visual design element in Composr, essentially containers that visually group content on a page and often with a title at the top. In practice, blocks often place their content within a box, but this isn't a requirement / standard.

Question	Can I customize the appearance of blocks?
Answer	Yes, you can customize the appearance of blocks by editing the associated templates and CSS. Each block typically has a corresponding template file (e.g., BLOCK_MAIN_NEWS.tpl for the main_news block) that controls its HTML structure. You can modify this template to change the layout and styling of the block's output. An easy way to do this is through the template editor in Admin Zone > Style > Themes, and click edit templates for the relevant theme.

Question	How do I add dynamic content to my Comcode pages?
Answer	Composr utilizes "blocks" to embed dynamic content and functionality within Comcode pages. These blocks can range from displaying recent forum posts to showing information about the logged-in user. To add a block, you can use the "block construction assistant" accessible via a button above the editor. This tool provides a user-friendly way to: Browse and select available blocks. Configure the block parameters. Preview the block output. Generate the necessary Comcode to embed the block.

Question	How do I create a new Comcode page?
Answer	Composr provides two easy ways to create a new Comcode page: Method 1: Direct URL Entry Type the desired URL of your new page into your browser's address bar. Since the page doesn't exist yet, Composr will present you with a 404 error and a link to create it. Click the link to open the Comcode page editor. Method 2: Admin Zone Navigate to Admin Zone > Content > Pages (Comcode pages). Scroll down to the list of existing pages and enter the name of your new page using the ":" (page-link) format. For example, a new page in the Welcome zone named "about" would be entered as ":about", or a new page in the "site" zone named "foobar" would be entered as "site:foobar".

Statistics

Forum statistics:	45 topics, 14 posts, 2 members Our newest member is test