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 | 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:
|
Question | Can I integrate a dedicated issue management system with Composr? |
---|---|
Answer | While Composr doesn't have a built-in issue tracker, a non-bundled addon (cms_homesite_tracker) provides an integrated, modified version of Mantis. Additionally, the Support Ticket system can function as a basic private issue tracker using features like Post Templates. |
Question | How can I restrict access to the support system to specific users? |
---|---|
Answer | Utilize Composr's page access permissions to control who can access the Support Ticket page. This ensures only authorized users can submit support requests. You can also control permissions based on ticket type when adding or editing a ticket type. Make sure if you go this route that the Support Ticket page permissions are very liberal (e.g. allow anyone to access, or just restrict to guests if you will never allow guests to make tickets). Otherwise, some people cannot make tickets even if they have permission on the type. |
Question | What are Post Templates and how are they beneficial for support? |
---|---|
Answer | Post Templates are predefined text blocks that can be used as templates for new forum posts. They are particularly useful in support scenarios by:
Post Templates can be configured to be the default post in specific forums or restricted to certain user groups. Go to Admin Zone > Structure > Forums > Post Templates. |
Question | How does Composr handle email integration for support? |
---|---|
Answer | Composr can integrate with email for ticket management, assuming certain requirements are met:
With email integration, users can submit tickets via email, and staff can reply through the system. Composr cleans up email text for ticket clarity and allows forwarding emails to the integrated address for efficient handling. |
Question | How can I categorize and prioritize support requests? |
---|---|
Answer | Support Ticket System: Utilize support ticket types, managed in the Admin Zone > Setup > Support tickets. Staff can set individual notifications for different types. Discussion Forums: Create dedicated subforums for different support categories or priority levels. Feedback System: The content to which the feedback is attached implicitly categorizes it. For prioritization, subforums can be used. |
Question | What are the advantages of using the Support Ticket system over the Discussion Forums? |
---|---|
Answer | While both systems can be used for support, the Support Ticket system provides advantages like:
|
Question | How can Composr be used as a support desk tool? |
---|---|
Answer | Composr offers three main systems for providing online support: 1. Support Ticket System: This system allows users to submit tickets and staff to respond, track, and resolve them. It features email notifications, ticket categorization and prioritization, staff assignment, and attachment support. 2. Discussion Forums: Conversr, Composr's built-in forum software, can be utilized for support by creating dedicated forums or subforums. Features like post templates and multi-moderations enhance support capabilities. 3. Feedback System: This system allows for comments on various content types, facilitating support directly related to that content. |
Question | How can I access the raw data behind the statistics graphs? |
---|---|
Answer | Every graph in Composr offers a spreadsheet export option. This allows you to download the data in a spreadsheet format, enabling detailed manual review or further analysis using third-party tools. |
Top 10 Entries
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. |
Question | How can staff be effectively managed in a Composr community? |
---|---|
Answer | Successful staff management requires a mindful approach that prioritizes fostering a positive and productive environment. Key recommendations include:
By fostering a supportive and empowering environment, community managers can enable staff to contribute their best efforts and drive the community's success. |
Question | How should staff members be chosen for a Composr-based online community? |
---|---|
Answer | Choosing staff for online communities differs from traditional hiring processes due to factors like unpaid positions, varying time commitments, and remote interactions. Focus should be placed on identifying individuals with:
|
Question | How can content issues be reported and addressed by staff? |
---|---|
Answer | Composr's content reporting system, powered by the Tickets addon, allows users to report problematic content to staff. Key features include:
This system ensures efficient handling of content issues, allowing staff to address concerns effectively while maintaining a transparent record of actions taken. |
Question | How can staff members collaborate effectively in Composr? |
---|---|
Answer | Composr offers various tools to facilitate staff collaboration:
|
Question | What defines a staff member in Composr? |
---|---|
Answer | There are two ways to define "staff" in Composr:
Composr prioritizes flexibility by utilizing privileges over fixed roles, allowing for customized staff responsibilities. However, certain features like "staff reply" in tickets inherently rely on a pre-existing understanding of "staff." |
Question | What steps should I take if my website has been hacked? |
---|---|
Answer | If you suspect a security breach, take immediate action:
|
Question | What additional security measures can I implement for my Composr website? |
---|---|
Answer |
|
Question | How does Content Security Policy (CSP) contribute to Composr security? |
---|---|
Answer | CSP adds a layer of protection by controlling the resources the browser is allowed to load. It helps prevent:
Composr's CSP implementation utilizes "Trusted partner sites" and nonces for fine-grained control. |