Features: A-Z Index
A
B
C
D
E
F
G
I
L
M
N
P
Q
R
S
T
W
Newest 10 Entries
Title | Galleries |
---|---|
Icon | ![]() |
Description | 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. |
Title | Catalogues |
---|---|
Icon | ![]() |
Description | 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. |
Name | Patrick Schmalstig |
---|---|
Photograph | ![]() |
Title / Role | Lead Developer |
Contributions / Notes | 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. |
Links |
Name | Jim Davidson |
---|---|
Title / Role | contributor |
Contributions / Notes | written many tutorials via Arvixe |
Name | Chris Warburton |
---|---|
Title / Role | developer for ocProducts |
Contributions / Notes | Made some key contributions to ocPortal |
Name | Haydn Maidment |
---|---|
Title / Role | project manager for ocProducts |
Contributions / Notes | None available |
Name | Steve Jarvis |
---|---|
Title / Role | project manager for ocProducts |
Contributions / Notes | Wrote many tutorials via Arvixe |
Name | Philip Withnall |
---|---|
Title / Role | Early Developer |
Contributions / Notes | 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 |
Name | Allen Ellis |
---|---|
Photograph | ![]() |
Title / Role | Founder |
Contributions / Notes | 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 |
Name | Robert Goacher |
---|---|
Photograph | ![]() |
Title / Role | Founder |
Contributions / Notes | 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 |
Top 10 Entries
Question | How do I install geo-location data for Composr statistics? |
---|---|
Answer | Geo-location data installation is usually automatic during the Composr installation process. If not, you can manually install it by navigating to Admin Zone > Audit > Site statistics > Install geolocation data. This action will reschedule the installation task. If you don't see this option, the geo-location data is already installed. |
Question | What are the key differences between Google Analytics and Composr statistics? |
---|---|
Answer | While there is some overlap, Composr statistics and Google Analytics are complementary tools. Google Analytics Pros:
Google Analytics Cons:
Composr Statistics Pros:
Basic users may find Composr statistics sufficient, while expert marketers might prefer the power of Google Analytics. |
Question | What tools and strategies can be used for staff training and development? |
---|---|
Answer | While Composr itself doesn't provide built-in training features, several approaches can be used for staff development:
By investing in ongoing staff training and development, communities can ensure their teams possess the necessary knowledge and skills to perform their roles effectively and contribute to the platform's overall success. |
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." |