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 web technologies does Composr use beyond HTML, CSS, and JavaScript?
Answer	Composr relies on a wide range of web technologies (depending on what features and settings you use), including: Protocols: HTTP/HTTPS, FTP, SFTP, SMTP, IMAP, POP3, DNS, and others Data formats: XML, JSON, CSV, PHP's serialized format, iCalendar, and various image and archive formats Standards: Accessibility standards (WCAG, WAI-ARIA), metadata standards (Open Graph, schema.org, Dublin Core), and microformats Server-side technologies: PHP, SQL (for database interaction) Composr-specific technologies: Tempcode (template system), Comcode (content language), Page-links, Filtercode, Selectcode, and Language packs

Question	How does Composr ensure printed web pages look appropriate?
Answer	Composr uses a combination of approaches to ensure printed web pages have a suitable layout: Automatic browser behavior: Browsers typically disable background images when printing. CSS print stylesheets: Composr utilizes CSS to define specific display rules for printed versions of pages, such as removing margins and hiding social media links. wide_print parameter: This parameter, activated through specific links or specifying it in the URL, further influences page layout for printing.

Question	How can I test my website's compatibility across different browsers and devices?
Answer	Testing your website on different browsers and devices can be challenging due to operating system limitations and device availability. Here are some solutions: Virtual Machines: Use virtual machines to run different operating systems and test various Internet Explorer versions. Device Emulation: Use built-in device emulation features in browsers like Chrome to simulate mobile devices. Online Testing Services: Employ commercial online testing services like BrowserStack to access a wide range of browsers and devices hosted in the cloud. Real Devices: Conduct testing on physical mobile devices for a more realistic user experience.

Question	What are the recommended desktop settings for viewing a Composr website?
Answer	A minimum screen resolution of 1024x768 is strongly recommended for viewing a Composr website. This is the minimum resolution for which the default theme is designed. Using a lower resolution might lead to display issues or an unsatisfactory browsing experience. As of version 11, smaller resolutions will often trigger the mobile layout automatically (responsiveness) to ensure a better UI for smaller displays.

Question	How does Composr handle browser compatibility?
Answer	Composr aims to support all modern browsers, including the latest versions of Chrome, Firefox, Safari, Edge, and Internet Explorer 11. It is designed to work seamlessly with browsers that automatically update, like Chrome and Firefox. For browsers with manual updates, Composr generally supports the last two releases. While not explicitly supported, Composr will often address bug reports for other popular browsers like Opera, Chromium, and Konqueror. Additionally, Composr strives to provide an accessible experience for text-mode browsers and those designed for users with disabilities.

Question	What is CSS and how does it impact website design?
Answer	CSS (Cascading Style Sheets) is a language used to describe the visual presentation of a web page written in HTML or XHTML. It controls aspects like: Fonts and typography: Defining font families, sizes, weights, and styles. Colors and backgrounds: Setting colors for text, backgrounds, borders, and other elements. Layout and positioning: Controlling the placement and arrangement of elements on a page. Visual effects: Adding shadows, gradients, transitions, and other visual enhancements. By separating content structure (XHTML) from visual presentation (CSS), websites become easier to maintain and update. Changes to the design can be made without altering the underlying HTML structure. Composr utilizes CSS extensively for theming, allowing users to manipulate the website's visual appearance.

Question	Why is understanding XHTML important for website customization?
Answer	XHTML (Extensible HyperText Markup Language) is the language used to structure web page content. It defines the various elements of a webpage, such as headings, paragraphs, images, and links. Understanding XHTML is crucial for website customization because it allows you to: Modify page layout: Change the arrangement and positioning of elements on a page. Add new content: Insert additional text, images, or other multimedia elements. Customize the appearance of existing elements: Change fonts, colors, sizes, and other visual styles. Integrate interactive features: Embed JavaScript code for dynamic functionality. Composr uses XHTML for its templates, allowing users to extensively customize the website's design and layout.

Question	How does JavaScript enhance website interactivity?
Answer	JavaScript is a programming language that runs in web browsers, allowing for dynamic and interactive elements on web pages. It enables features like: Dynamic content updates: Modifying page content without requiring a full page reload. User interface enhancements: Creating interactive elements like dropdown menus, image sliders, and form validation. Animations and visual effects: Adding visual appeal and engaging user experiences. Asynchronous communication: Fetching data from, or sending data to, servers in the background without disrupting user interaction. Composr relies on JavaScript for its default theme and administrative features.

Question	What is the difference between cookies and sessions?
Answer	While both cookies and sessions are used for user identification and maintaining state, there are key differences: Storage: Cookies are stored on the user's computer, while sessions are stored on the server. Expiration: Session cookies expire when the browser is closed, while persistent cookies have a set expiration date. Sessions typically expire after a period of inactivity. Data sensitivity: Sessions are generally used for more sensitive data, as the information is not stored on the user's computer and therefore less likely to be stolen by a hacker. Composr uses both cookies and sessions. Session cookies are primarily used for user identification (such as anonymously matching a user to a session in the server database), while persistent cookies can be used for remembering login details if the user chooses.

Question	What are cookies and how do they work?
Answer	A cookie is a small piece of data that a website stores on a user's computer. It is sent from the user's web browser to the web server each time a page is viewed. Cookies are used for various purposes, including: User identification: Cookies can be used to identify a specific user, even if they are not logged in. This allows websites to remember user preferences, shopping cart contents, and other information. Tracking user behavior: Cookies can be used to track user behavior on a website, such as the pages they visit and the links they click. This information can be used to improve the website's design and content. Advertising: Cookies can be used to deliver targeted advertising to users based on their browsing history. There are two main types of cookies: Session cookies: These cookies are temporary and are deleted when the user closes their web browser. They are often used to store information about the user's current session, such as the items in their shopping cart. Persistent cookies: These cookies are stored on the user's computer for a longer period. They can be used to remember user preferences, such as their login details or language settings.

Statistics

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