• Understand that Composr is developed and maintained by volunteers who dedicate their time to the project.
• Refrain from demanding free support or expecting developers to work on specific schedules.
• Avoid placing undue pressure on volunteers or pushing them beyond their capacity.
• Approach the community with respect and a collaborative spirit.
• Remember that offering financial sponsorship for desired features can accelerate development.

• Be specific and detailed. Identify particular issues and provide clear examples.
• Offer solutions. Suggest improvements or provide mockups demonstrating your ideas.
• Avoid vague statements. General comments like "it looks dated" are unhelpful.
• Understand design constraints. Consider factors like modularity, generality, feature density, compatibility, performance, and the subjective nature of design.

• Be comprehensive and self-contained. Provide all necessary information and context for the developers to understand your suggestion.
• Focus on widely beneficial features. Esoteric suggestions are less likely to be implemented.
• Understand developer constraints. Feature development depends on factors like developer availability, funding, and project strategy.
• Consider sponsoring features. Financial contributions can prioritize the development of desired features as it affords developers the time to implement it.

• Open a tracker issue explaining the problem and providing as much detail as possible (mark it as a major bug).
• Help the developers help you. Provide access to your site (see the software feedback tutorial for more information), describe the exact situation, and avoid protracted back-and-forth communication.
• Take backups before upgrading. This allows for easier recovery in case of problems.

• Check for duplicates: Make sure the bug hasn't already been reported.
• Report bugs individually: Each issue should be reported separately for better tracking and resolution.
• Verify it's a Composr bug: Issues with third-party addons and code should be reported to their respective developers.
• Consult the FAQ and tutorials: Check for common problems and solutions, particularly server configuration issues.
• Provide comprehensive information: Include a clear and specific title, detailed steps to reproduce the problem, your browser version, Composr version, error messages, stack traces (if available), and any other

• Use clear and concise language: Write in proper English, use correct terminology, and avoid vagueness.
• Be respectful and patient: Remember that developers are volunteers and may not respond immediately.

Multimedia: Supports images, videos, audio, and more.

Personal galleries: Allow your members to create their own galleries which show up on their profile.

Support for embedding YouTube videos: Save on bandwidth.

Auto-detection of video length and resolution (most file formats)

Full tree-structure support: Have galleries within galleries within galleries.

Multiple display modes

View entries as a slideshow

Automatic thumbnail generation

Mass import: Also supports importing metadata

Optional watermarking: To guard against thieving swines .

Geotargeting

Adjustments: Automatic size and orientation adjustments according to metadata.

Think “databases on my website”.

Flexible data control: Set up multiple catalogues, each with its own set of fields. There are many types of fields, such as short text fields, upload fields, and date fields.

Multiple display modes: Display the contents of categories using tables, boxes, or lists.

Powerful structure: Each catalogue contains categories which contain entries. Catalogues can have a tree structure of categories and/or work from an index.

Configurable searching: Choose which fields are shown on categories, and which can be used to perform searches (template searches).

Compliance with data protection legislation: Specify which fields may contain sensitive data. These fields will be anonymised as appropriate when members download or purge their data.

Entirely customisable: Full support for customising catalogues, categories, and entries, exactly as you want them- field by field. You can even make custom page templates per-catalogue.

Classified ads: Entries can automatically expire and get archived. You can also send out view reports.

Community interaction: You can allow users to comment upon and rate entries.

Import data from CSV files

Periodic content reviews: Helping you ensure ongoing accuracy of your data.

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

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