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: Respect staff limitations: Avoid overwhelming staff with excessive workload or overly ambitious site expansions. Active involvement: Maintain active involvement in overseeing staff activities and ensuring their effective functioning. Open communication: Engage in regular communication, providing feedback, addressing concerns, and recognizing achievements. Foster teamwork: Encourage collaboration and information sharing among staff members. Lead by example: Ensure staff adhere to community rules and demonstrate expected behavior. Empowerment and trust: Grant sufficient freedom and control to enable staff to excel in their roles. 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: Genuine interest: Look for members passionate about the community and its goals. Available time: Ensure potential staff can dedicate sufficient time to fulfill their responsibilities. Relevant skills: Prioritize skills and experience aligned with the specific role requirements. Maturity and discipline: Seek individuals who demonstrate responsible behavior and commitment. Recruitment methods like directly approaching active community members or allowing the Composr points system (or the karma non-bundled addon) to identify dedicated contributors can be more effective than traditional advertising.

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: Report links: "Report this" links embedded throughout the site enable users to flag content for review. Custom reporting interface: Forums offer a dedicated interface for reporting individual posts. Anonymous reporting: Logged-in users can choose to report content anonymously. Ticket-based management: Reports are automatically created as support tickets, facilitating staff collaboration and record-keeping. Comprehensive report details: Tickets include content title, type, ID, submitter information, an embedded rendering of the reported content, and the reporter's explanation. 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: Private forums: Dedicated forums with restricted access enable staff to discuss site operations and coordinate activities. Composr installs a staff forum by default in Conversr. Conflict detection: When multiple staff members attempt to edit the same resource simultaneously, Composr displays warnings at the top to prevent accidental overwrites. Staff checklist & dashboard: The Admin Zone dashboard provides a shared checklist for task management, along with space for notes and links. Staff notifications and tickets system: Staff receive notifications about various site events, including support tickets from the "Contact Us" page, allowing for efficient issue handling. Content notes: Staff can embed notes within Comcode or use dedicated "staff notes" fields for various content types to share information and context. Validation and workflows: Content can be intentionally left unvalidated even by staff, enabling secondary checks before publishing. A dedicated workflows addon allows for complex approval processes with multiple stages involving different staff groups.

Question	What defines a staff member in Composr?
Answer	There are two ways to define "staff" in Composr: System-defined staff: This includes administrators and super moderators who have specific privileges within the forum/member system (Conversr). Privilege-based staff: Anyone granted the necessary permissions for a particular situation is considered staff for that context. 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: Identify the Cause: Analyze access logs for suspicious activity and pinpoint the vulnerability. Clean and Restore: Restore your website from a clean backup and thoroughly remove any malicious code. Address Vulnerabilities: Patch security holes, update software, and strengthen security configurations. Seek Expert Help: If needed, consult security professionals for assistance with cleanup and prevention.

Question	What additional security measures can I implement for my Composr website?
Answer	SSL: Enable HTTPS for encrypted communication and improved user trust. Secure Zones: Configure sensitive zones to require confirmed sessions. Restrict Logins: Enforce IP address confirmation for enhanced account security. Maintenance Scripts: Restrict access to maintenance scripts like upgrader.php via IP restrictions. Server Hardening: Disable unnecessary services, change default ports, enable automatic updates, and more. Robots.txt: Use the robots.txt file to prevent search engine indexing of sensitive areas.

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: XSS Attacks: By restricting inline scripts and limiting script sources. Data Injection Attacks: By controlling the allowed origins for data requests. Clickjacking: By specifying allowed framing sources. Composr's CSP implementation utilizes "Trusted partner sites" and nonces for fine-grained control.

Top 10 Entries

Question	What is Tempcode, and how is it used in website themeing?
Answer	Tempcode is a templating language used within Composr. It offers a powerful way to control the output of dynamic content and design elements on a website. It works by using: Parameters: Placeholders for content passed to the template from Composr / PHP. Symbols: Global functions that perform operations, calculations, or retrieve information. Directives: Instructions that control the flow or logic of content, such as conditional statements and loops. Language strings: References to pre-defined text stored in language files for easy translation. Escaping: Ensures the content generated is properly escaped according to its use case. Tempcode empowers theme designers to create highly customizable and dynamic websites, allowing for logic, conditional rendering, and manipulation of various website elements.

Question	What are some alternatives to Photoshop for web design?
Answer	While Photoshop is a popular choice, there are other excellent options available, including: GIMP/GIMPShop: These free, open-source image editors provide a robust set of features comparable to Photoshop. Paint.NET: This free, Windows-only software offers a user-friendly interface and essential image editing tools. Corel Paint Shop Pro: A more affordable alternative to Photoshop, Corel Paint Shop Pro delivers a good balance of features and ease of use.

Question	How can design elements like dominance and attention to detail improve a website?
Answer	Dominance and attention to detail are key to a balanced and engaging website. Important elements can be emphasized using techniques like larger text, unique colors, and increased spacing. Conversely, less crucial elements should receive less emphasis. This interplay helps guide the visitor's eye and ensures a visually harmonious layout. Attention to detail involves eliminating inconsistencies and distractions, such as typos, misaligned elements, and low-quality images, that can detract from the overall aesthetics and message of the website.

Question	What is the importance of color schemes in website design?
Answer	Color schemes are crucial as they convey emotions and brand identity. Choosing colors that align with your website's purpose can evoke desired feelings in visitors. For example, a website selling chocolates might use shades of brown to subconsciously trigger associations with chocolate. However, an environmental website would be better suited using green, aligning with pre-existing perceptions of environmentalism. It is also important to maintain consistency with your color scheme, limiting the number of colors used to avoid a conflicting and cluttered appearance.

Question	Can I use Comcode / resource IDs directly when working with the repository?
Answer	Using Comcode / resource IDs directly is not recommended as they may not match between different sites. Use GUIDs instead, which Composr automatically substitutes for IDs before parsing Comcode. You can use Commandr commands like find_guid_via_id to find the GUID for specific resources.

Question	What precautions should I take when using the Composr Repository?
Answer	Exercise caution when working with the repository: Avoid using it as the sole backup method; rely on regular database backups. Work primarily under the "var" meta-filesystem and copy specific folders/files rather than the entire repository. Do not use tools like "rsync" or Git on the whole repository without careful consideration.

Question	What are the limitations of the Composr Repository?
Answer	While powerful, the repository has limitations: Automatic syndication is not performed for content added via the repository. Multi-language content translations are not retained. Transferring complex data schemas between staging sites may have limitations. Merging separate websites into one is not supported through the repository. You should use Composr's import tool instead.

Question	How can I access the Composr Repository?
Answer	You can access the repository using WebDAV (non-bundled addon), which allows you to view it as a folder on your computer. Composr uses the SabreDAV PHP library for WebDAV functionality. However, please be aware that SabreDAV is deprecated and may not function correctly on newer PHP versions.

Question	How is the Composr Repository structured?
Answer	The repository is structured as a filesystem with various meta-filesystems mounted under a root directory. These meta-filesystems include: bin: Stores Commandr scripts. database: Provides access to the raw database. etc: Allows access to Composr configuration options. home or filedump: Provides access to the File/Media Library. home contains the files in a special JSON format with metadata filedump contains the raw files members: Lists registered members with their settings and user groups. raw or root: Provides access to the Composr installation directory. raw contains the raw files without overrides, and modifying any file modifies them directly without automatic override handling root contains the files with applicable overrides applied automatically, and Composr will automatically handle overrides and utilizing _custom directories when these files are modified var: Contains structured website resources and content.

Question	What are the benefits of using the Composr Repository?
Answer	The repository offers several benefits: Opacity: Provides a clear view of Composr's content and resource data. Tactility: Allows easy manipulation of data through drag-and-drop operations. Data transfer: Simplifies transferring data between sites. Desktop application integration: Enables using text editors and file-search tools for tasks like mass search and replace. Configuration management: Tracks changes to options and facilitates transfer between sites. Backups: Allows backing up portions of the repository. Revision control: Supports built-in and advanced revision control. Filesystem for Commandr: Acts as a file system for the Commandr command line. Resource API: Offers an abstract resource API for programmers. API for external apps: Provides an API for mobile apps and other external applications.

Statistics

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