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 | 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. |
Top 10 Entries
Question | How can I ensure my website complies with email marketing laws? |
---|---|
Answer | Email marketing laws like CAN-SPAM protect recipients' rights to unsubscribe. Your website must include a clear 'List-Unsubscribe' header in every email, offer an easy unsubscribe process, and respect unsubscribe requests promptly. Composr provides built-in mechanisms, including an unsubscribe endpoint and support for the List-Unsubscribe header, to facilitate compliance. |
Question | What are my responsibilities regarding user privacy? |
---|---|
Answer | You must have a comprehensive privacy policy that details the personal data you collect, its usage, and if it's shared with third parties. Laws like GDPR have strict requirements, including logging data access, data purging, and security measures. California law mandates specific elements in your policy, like handling "Do Not Track" requests and a clear process for communicating changes. Composr has an automatic Privacy Policy generator block to help you get started. This is used by default. |
Question | How can I create effective website rules? |
---|---|
Answer | A well-defined rules page is crucial for setting expectations for user behavior and outlining consequences for violations. It should cover a range of offenses with appropriate punishments, reference relevant laws, and assign legal responsibility to users. Composr provides default rules pages that can be customized, and this page is displayed to users upon joining the site. |
Question | What are the key legal considerations for running a website? |
---|---|
Answer | Several legal aspects need careful attention when operating a website, especially for large or corporate sites. These include establishing clear rules and terms of service, adhering to privacy laws like GDPR and California's regulations, managing personal data responsibly, complying with email marketing regulations like CAN-SPAM, ensuring website accessibility, addressing eCommerce regulations, and understanding liability for content and user actions. |
Question | How do data-tpl and data-view behaviors work in Composr's JavaScript? |
---|---|
Answer | Composr uses data-tpl and data-view behaviors for associating HTML templates and JavaScript views, respectively. This facilitates clean separation of presentation and logic:
|
Question | What are the advantages of using Composr's JavaScript libraries? |
---|---|
Answer | Composr's JavaScript libraries like $cms, $util, and $dom offer several advantages:
|
Question | How does Composr implement the Model-View-Controller (MVC) pattern? |
---|---|
Answer |
|
Question | Can I translate my content into multiple languages? |
---|---|
Answer | Yes, Composr supports multi-language content. You can enable this feature by:
|
Question | My language uses gendered descriptors. How can I handle this in Composr? |
---|---|
Answer | Composr offers solutions for languages with gendered descriptors:
|
Question | What are language strings, and how are they used? |
---|---|
Answer | Language strings are phrases or pieces of text used throughout Composr. They're identified by unique codenames, like WELCOME_MESSAGE. These strings are stored in .ini language files and used to display text in the user interface. By translating language strings, you change the text displayed on your website without modifying the underlying code. |