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	What are the different ways to target recipients for my newsletters?
Answer	Composr offers several targeting options: Subscriptions: Users can specifically subscribe to newsletters, separate from site membership. Usergroups (Conversr only): You can send newsletters to members of specific usergroups, regardless of their newsletter subscriptions. CSV imports/exports: You can import subscribers from a CSV file or export your subscriber list for custom targeting.

Question	How can I prevent my emails from being marked as spam?
Answer	Here are some tips to reduce the likelihood of your emails being flagged as spam: Set up SPF records: SPF (Sender Policy Framework) helps verify that your server is authorized to send emails from your domain. Ask users to whitelist your email address: Encourage recipients to add your email address to their contacts list or "Safe Senders" list. Configure DKIM: DKIM (DomainKeys Identified Mail) adds a digital signature to your emails, increasing their legitimacy. Use a reputable email service provider: Consider using a third-party email service if you're struggling with email deliverability.

Question	Why are my emails being blocked by spam filters?
Answer	Several factors can cause emails to be blocked: Server issues: Your server might be on a spam blacklist, or there may be problems with your server's reverse DNS or HELO settings. Content issues: Your email content might trigger spam filters due to factors like an unreasonable image-to-text ratio, broken reply-to addresses, or inconsistent text and HTML versions. SPF records: Your "Website email address" might be hosted on a different server with an SPF record that doesn't authorize your web server to send emails from that address.

Question	How do I configure SMTP settings in Composr?
Answer	Composr can use either its own SMTP connection code or PHP's built-in SMTP functionality. Using PHP's SMTP settings is generally recommended and can be managed at the server level. However, if your SMTP server requires authentication (which PHP doesn't support natively) or if your server lacks an SMTP server, you'll need to use Composr's SMTP connection code, configurable in the Configuration module.

Question	How does Composr send emails?
Answer	Composr constructs emails using language strings and templates written in Comcode. It sends emails in both HTML and plain text formats to ensure compatibility with different email clients. To minimize the chance of emails being marked as spam, Composr embeds CSS and images directly into the email instead of linking to them externally.

Question	How can I make my website design more appealing to different thinking styles?
Answer	Different individuals process information differently. Some are more visual, while others are more analytical. To appeal to diverse thinking styles, a website design should incorporate a balance of elements. For instance, using a striking header image coupled with well-structured, informative text can cater to both visual and analytical thinkers. Understanding your target audience and their thinking styles is key to creating a design that resonates with them.

Question	What considerations are necessary when designing for different user levels on a website?
Answer	User levels often necessitate different content or functionalities. For instance, administrators might need access to content creation tools, while regular visitors only view published content. Consider these factors during design: Visibility: Some elements might need to be hidden or displayed based on user roles (e.g., admin-only links). Permissions: Design elements and interactive features should reflect the permissions granted to different user levels. Customization: Consider allowing users to customize their experience based on their preferences and roles. Remember, a well-designed website should cater to all user levels while maintaining security and a cohesive experience.

Question	How do I make my website theme mobile-friendly in Composr?
Answer	Composr offers several features to optimize themes for mobile: Mobile mode: You can design separate layouts and CSS styles specifically for mobile devices, which Composr automatically activates when a mobile user visits your site. Tempcode's 0 symbol: This symbol helps conditionally display content based on whether the user is on a mobile device or desktop. CSS media queries: By using media queries, you can target specific screen sizes and adjust styles accordingly, making your theme responsive. Viewport meta tag: This tag controls how the browser scales and displays the webpage on mobile devices, ensuring a properly sized and zoomable experience.

Question	What is responsive design, and why is it essential for mobile devices?
Answer	Responsive design ensures a website adapts seamlessly to different screen sizes, providing an optimal viewing experience across devices, particularly mobile phones and tablets. It utilizes techniques like flexible grids, fluid images, and CSS media queries to adjust layout and content based on screen dimensions. This is crucial because mobile device usage is significant, and a non-responsive site leads to a poor user experience on smaller screens, potentially driving visitors away.

Question	How can I create a theme pack for release in Composr?
Answer	After designing your theme, go to the admin panel's "Addons" section. You'll find an option to export your current theme as an addon. Composr will package the necessary files into a downloadable archive, ready to be shared with others or submitted to the Composr community for installation on other sites.

Top 10 Entries

Question	What are some of the default endpoints available in the server-side API?
Answer	Default endpoints cover various functionalities, including: Account: join, login, lost_password, setup_push_notifications Misc: contact_us Content: commandr_fs Specific details on parameters and response data for each endpoint can be found in the documentation.

Question	How does authentication work with the server-side API?
Answer	Authentication is handled automatically using cookies, similar to regular website requests. If cookies are not feasible, the response parameters device_auth_member_id_cn/device_auth_pass_hashed_cn/device_auth_member_id_vl/device_auth_pass_hashed_vl from the login endpoint can be resent as POST parameters in subsequent requests.

Question	How do I access the server-side API for my mobile app?
Answer	The server-side API can be accessed via HTTP calls to http://yourbaseurl/data/endpoint.php. Results are returned in JSON format. The API utilizes endpoints with a 'hook' name and a 'hook type' categorization. Both REST-style and GET-parameter style requests are supported, with the latter recommended for simplicity.

Question	What is the purpose of the Composr Mobile SDK Toolkit?
Answer	The Toolkit, part of the composr_mobile_sdk addon, aids in mirroring Composr website resources into a mobile app. It includes tools for generating iOS/Android string resources from language files and exporting theme images in a directory structure suitable for iOS/Android app image assets.

Question	How can I obtain Composr Mobile SDK?
Answer	The iOS/Android SDK can be found on GitLab at: Composr ecosystem / Composr Mobile SDK · GitLab. To connect to a Composr site, you will need to install the composr_mobile_sdk addon, which is not bundled. This addon provides scripting to generate app assets from the Composr site.

Question	What is Composr Mobile SDK?
Answer	Composr Mobile SDK (CMS SDK) is a toolkit designed for experienced iOS and Android developers to build mobile apps that integrate with a Composr-powered website. It offers both Composr-specific integrations and a collection of standalone utilities for building apps, providing a common base between iOS and Android akin to the PHP and Composr APIs, enabling easier code porting while maintaining a native experience.

Question	What is the Composr maintenance policy?
Answer	Composr follows a rolling release model. This means: New major/minor versions are released as they are ready. Patch releases, primarily containing bug fixes, are only released for the latest supported major/minor version branch. Users are responsible for staying updated to the latest release or applying necessary hotfixes. This policy allows developers to focus resources on the latest versions and encourages users to leverage the ongoing improvements. You can find the release status on the Composr maintenance status page.

Question	What are the general courtesy guidelines for interacting with the Composr community?
Answer	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.

Question	How can I provide design feedback for Composr?
Answer	Constructive design feedback is valuable. To provide effective feedback: 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. Directly reporting specific design bugs to the tracker or redesigning Composr interfaces yourself are excellent ways to contribute.

Question	How do I make a feature suggestion for Composr?
Answer	You can suggest features through the tracker or the Report Issue Wizard. When making a suggestion: 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.

Statistics

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