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.

PDStig, LLC

written many tutorials via Arvixe

Made some key contributions to ocPortal

None available

Wrote many tutorials via Arvixe

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

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

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

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

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

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

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

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

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

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

• Confirmed: When you actively log in with your credentials.
• Non-confirmed: When you return to the site and are automatically logged in via cookies.

• Choose a Secure Host: Opt for hosts that offer suEXEC and open_basedir for better account isolation.
• Test Security: Verify the host's security measures with the provided filesystem_browser.php script.
• Restrict _config.php: Remove world-writable permissions from _config.php after installation.