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	Can I move a Wiki+ page?
Answer	Technically, Wiki+ pages cannot be moved because they don't have a fixed location within the network structure. Creating child links forms a path, not a strict hierarchy. However, you can manipulate the breadcrumbs by ensuring only one path leads to a page.

Question	Can I track changes made to Wiki+ pages?
Answer	Yes, Wiki+ includes a revision history feature accessible through the page edit screen. This feature allows you to view a log of edits, see changes highlighted in tooltips, and revert to previous versions of a page as needed.

Question	How can I view the complete tree structure of my Wiki+?
Answer	You can access a view of the complete Wiki+ tree structure through the designated option in the admin panel. However, it's important to note that this view will reflect guest access permissions. Some pages may be hidden if they are restricted to specific user groups.

Question	What moderation tools are available in Wiki+?
Answer	Wiki+ offers several features to help you moderate user contributions and maintain the quality of information: Email Notifications: When a new post is submitted, an email notification is sent to the designated staff address, alerting you to new contributions. Permissions Control: You can configure permissions to determine whether regular users can create new pages or only contribute through posts. Page History: The revision history feature allows you to track edits made to pages and revert to previous versions if necessary. Composr Moderation Tools: Wiki+ integrates with Composr's site-wide moderation features, providing additional tools for monitoring and managing user contributions.

Question	Can users contribute content to Wiki+?
Answer	Yes, users can contribute content to Wiki+ through posts. When the "Show posts" option is enabled for a page, users can add their insights and information as posts below the main page content.

Question	What are orphaned pages and how should I handle them?
Answer	Orphaned pages are pages that exist within the Wiki+ database but are not linked to the main tree structure. These pages are not accessible through the tree navigation but can still be reached through direct links or cross-linking. Orphaned pages are not necessarily problematic. They can be intentional if you prefer to link pages using the wiki-style syntax instead of a rigid tree hierarchy. You have the flexibility to choose the linking method that best suits your content organization.

Question	How can I create and organize pages in Wiki+?
Answer	Pages in Wiki+ can be created in several ways: Referencing them in the child-list of an existing page. Using the special Comcode syntax [[pagename]] to create inline links, which automatically generates new pages when accessed. Utilizing the "Edit tree" button visible on Wiki+ pages to add child pages directly. The tree structure can be easily manipulated through the same interface, allowing you to arrange pages in a hierarchy that suits your needs.

Question	How does Wiki+ differ from a regular wiki?
Answer	While Wiki+ shares similarities with traditional wikis, it provides two key distinctions: Optional Post Contributions: Wiki+ allows users to contribute short snippets of information (posts) directly on pages, enriching the content without formally editing the page itself. This feature is optional and can be enabled or disabled as needed. Optional Tree Structure: Unlike standard wikis that rely solely on cross-linking, Composr's Wiki+ offers the flexibility of organizing pages within a hierarchical tree structure. This structure can be used in conjunction with or as an alternative to cross-linking.

Question	What is Wiki+?
Answer	Wiki+ is a feature in Composr that allows you to create a collaborative, tree-structured database of information. It functions similarly to a traditional wiki but offers enhanced features such as post contributions, a hierarchical structure, and moderation capabilities.

Question	Are there other Composr features helpful for support?
Answer	Yes, features like: Staff-only replies in the Support Ticket system enable private communication among support staff. Notifications for new tickets, replies, or feedback ensure timely responses. Blocks like main_contact_us provide a simplified front-end for ticket creation. Forum moderation tools help manage support discussions effectively.

Top 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.

Statistics

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