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

Top 10 Entries

Question	What are URL Monikers and how do they benefit SEO?
Answer	URL Monikers replace generic numerical IDs in your URLs with descriptive keywords derived from your content titles. For example, instead of yoursite.com/page.php?id=123, you can have yoursite.com/about-us. This makes your URLs more user-friendly and helps search engines understand the topic of each page, improving your search ranking. You can set monikers in the "Metadata" section when adding / editing content.

Question	What is an XML Sitemap and why is it important?
Answer	An XML Sitemap is a file that lists all the pages on your website, helping search engines understand your site's structure and content. Composr automatically generates a comprehensive sitemap, including forum topics if you are using Conversr. Ensure your system scheduler is enabled for automatic sitemap submission to search engines. You can also manually generate and submit the sitemap if necessary.

Question	How can I improve my website's ranking in search engines?
Answer	Composr offers various features and best practices to enhance your SEO: Content Optimization: Write high-quality, keyword-rich content using clear headings, relevant links, and descriptive image alt text. URL Monikers: Enable this feature to create human-readable URLs that incorporate keywords instead of numerical IDs. XML Sitemaps: Composr automatically generates and submits XML Sitemaps to major search engines, aiding them in discovering and indexing your content. robots.txt: This file allows you to control which parts of your site search engines can access and index. Composr provides a default robots.txt that can be customized as needed.

Question	What are the primary metadata elements I should focus on?
Answer	While Composr provides extensive metadata options, the key elements to prioritize are: Title: The title tag appears in browser tabs, search results, and when your page is shared. It should be concise, descriptive, and include relevant keywords. Meta Description: This short summary entices users to click on your search result. It should be engaging, informative, and accurately reflect the page's content. Open Graph data: These protocols control how your content appears when shared on social media and other websites. They utilize elements like title, description, and images to create visually appealing previews. Favicon and Apple Web Clip image: These small icons represent your website in bookmarks, browser tabs, and on mobile home screens. They contribute to branding and visual recognition.

Question	What is metadata and why is it important for my website?
Answer	Metadata is information about your web pages that isn't directly visible to visitors, but is used by search engines and social media platforms to understand and categorize your content. Well-crafted metadata helps search engines properly index your site, making it more likely to appear in relevant search results. It also improves how your website appears when shared on social media, encouraging clicks and engagement.

Question	What should I do about offensive or off-topic discussions?
Answer	Decide on your moderation approach: balancing viewpoints, adhering to community standards, or focusing on topic relevance. Be prepared to face criticism regardless of your decisions. Establish clear rules and policies to guide user behavior.

Question	What resources are available to help me navigate these legal and social challenges?
Answer	Composr offers various resources, including tutorials on accessibility, staff management, and general website dos and don'ts. You can also consult external resources like the COPPA website and Wikipedia for more in-depth information on specific laws and regulations. Remember that seeking legal counsel may be necessary for complex situations.

Question	What are some social considerations for running a website with community features?
Answer	Managing a community involves addressing social issues like child protection, free speech, discrimination, and abuse. Establish clear policies on these matters, including content moderation guidelines and procedures for handling feedback. Consider the diverse personalities and potential vulnerabilities of your users.

Question	What are my legal responsibilities regarding illegal content posted by users?
Answer	While "safe harbor" laws offer some protection, you are still obligated to take down illegal content upon becoming aware of it. Implement measures like content checks, clear rules prohibiting illegal uploads, and liability disclaimers. The level of responsibility varies depending on the severity of the content, from copyright infringement to more serious criminal content.

Question	What steps should I take to make my website accessible?
Answer	Website accessibility is essential for inclusivity and may be legally required under anti-discrimination laws. Composr is designed to meet high accessibility standards, but you need to maintain this when creating content or modifying templates. Following WCAG guidelines is crucial, and you can find more information in the accessibility tutorial.

Statistics

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