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 web technologies does Composr use beyond HTML, CSS, and JavaScript?
Answer	Composr relies on a wide range of web technologies (depending on what features and settings you use), including: Protocols: HTTP/HTTPS, FTP, SFTP, SMTP, IMAP, POP3, DNS, and others Data formats: XML, JSON, CSV, PHP's serialized format, iCalendar, and various image and archive formats Standards: Accessibility standards (WCAG, WAI-ARIA), metadata standards (Open Graph, schema.org, Dublin Core), and microformats Server-side technologies: PHP, SQL (for database interaction) Composr-specific technologies: Tempcode (template system), Comcode (content language), Page-links, Filtercode, Selectcode, and Language packs

Question	How does Composr ensure printed web pages look appropriate?
Answer	Composr uses a combination of approaches to ensure printed web pages have a suitable layout: Automatic browser behavior: Browsers typically disable background images when printing. CSS print stylesheets: Composr utilizes CSS to define specific display rules for printed versions of pages, such as removing margins and hiding social media links. wide_print parameter: This parameter, activated through specific links or specifying it in the URL, further influences page layout for printing.

Question	How can I test my website's compatibility across different browsers and devices?
Answer	Testing your website on different browsers and devices can be challenging due to operating system limitations and device availability. Here are some solutions: Virtual Machines: Use virtual machines to run different operating systems and test various Internet Explorer versions. Device Emulation: Use built-in device emulation features in browsers like Chrome to simulate mobile devices. Online Testing Services: Employ commercial online testing services like BrowserStack to access a wide range of browsers and devices hosted in the cloud. Real Devices: Conduct testing on physical mobile devices for a more realistic user experience.

Question	What are the recommended desktop settings for viewing a Composr website?
Answer	A minimum screen resolution of 1024x768 is strongly recommended for viewing a Composr website. This is the minimum resolution for which the default theme is designed. Using a lower resolution might lead to display issues or an unsatisfactory browsing experience. As of version 11, smaller resolutions will often trigger the mobile layout automatically (responsiveness) to ensure a better UI for smaller displays.

Question	How does Composr handle browser compatibility?
Answer	Composr aims to support all modern browsers, including the latest versions of Chrome, Firefox, Safari, Edge, and Internet Explorer 11. It is designed to work seamlessly with browsers that automatically update, like Chrome and Firefox. For browsers with manual updates, Composr generally supports the last two releases. While not explicitly supported, Composr will often address bug reports for other popular browsers like Opera, Chromium, and Konqueror. Additionally, Composr strives to provide an accessible experience for text-mode browsers and those designed for users with disabilities.

Question	What is CSS and how does it impact website design?
Answer	CSS (Cascading Style Sheets) is a language used to describe the visual presentation of a web page written in HTML or XHTML. It controls aspects like: Fonts and typography: Defining font families, sizes, weights, and styles. Colors and backgrounds: Setting colors for text, backgrounds, borders, and other elements. Layout and positioning: Controlling the placement and arrangement of elements on a page. Visual effects: Adding shadows, gradients, transitions, and other visual enhancements. By separating content structure (XHTML) from visual presentation (CSS), websites become easier to maintain and update. Changes to the design can be made without altering the underlying HTML structure. Composr utilizes CSS extensively for theming, allowing users to manipulate the website's visual appearance.

Question	Why is understanding XHTML important for website customization?
Answer	XHTML (Extensible HyperText Markup Language) is the language used to structure web page content. It defines the various elements of a webpage, such as headings, paragraphs, images, and links. Understanding XHTML is crucial for website customization because it allows you to: Modify page layout: Change the arrangement and positioning of elements on a page. Add new content: Insert additional text, images, or other multimedia elements. Customize the appearance of existing elements: Change fonts, colors, sizes, and other visual styles. Integrate interactive features: Embed JavaScript code for dynamic functionality. Composr uses XHTML for its templates, allowing users to extensively customize the website's design and layout.

Question	How does JavaScript enhance website interactivity?
Answer	JavaScript is a programming language that runs in web browsers, allowing for dynamic and interactive elements on web pages. It enables features like: Dynamic content updates: Modifying page content without requiring a full page reload. User interface enhancements: Creating interactive elements like dropdown menus, image sliders, and form validation. Animations and visual effects: Adding visual appeal and engaging user experiences. Asynchronous communication: Fetching data from, or sending data to, servers in the background without disrupting user interaction. Composr relies on JavaScript for its default theme and administrative features.

Question	What is the difference between cookies and sessions?
Answer	While both cookies and sessions are used for user identification and maintaining state, there are key differences: Storage: Cookies are stored on the user's computer, while sessions are stored on the server. Expiration: Session cookies expire when the browser is closed, while persistent cookies have a set expiration date. Sessions typically expire after a period of inactivity. Data sensitivity: Sessions are generally used for more sensitive data, as the information is not stored on the user's computer and therefore less likely to be stolen by a hacker. Composr uses both cookies and sessions. Session cookies are primarily used for user identification (such as anonymously matching a user to a session in the server database), while persistent cookies can be used for remembering login details if the user chooses.

Question	What are cookies and how do they work?
Answer	A cookie is a small piece of data that a website stores on a user's computer. It is sent from the user's web browser to the web server each time a page is viewed. Cookies are used for various purposes, including: User identification: Cookies can be used to identify a specific user, even if they are not logged in. This allows websites to remember user preferences, shopping cart contents, and other information. Tracking user behavior: Cookies can be used to track user behavior on a website, such as the pages they visit and the links they click. This information can be used to improve the website's design and content. Advertising: Cookies can be used to deliver targeted advertising to users based on their browsing history. There are two main types of cookies: Session cookies: These cookies are temporary and are deleted when the user closes their web browser. They are often used to store information about the user's current session, such as the items in their shopping cart. Persistent cookies: These cookies are stored on the user's computer for a longer period. They can be used to remember user preferences, such as their login details or language settings.

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