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