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 is Tempcode, and how is it used in website themeing?
Answer	Tempcode is a templating language used within Composr. It offers a powerful way to control the output of dynamic content and design elements on a website. It works by using: Parameters: Placeholders for content passed to the template from Composr / PHP. Symbols: Global functions that perform operations, calculations, or retrieve information. Directives: Instructions that control the flow or logic of content, such as conditional statements and loops. Language strings: References to pre-defined text stored in language files for easy translation. Escaping: Ensures the content generated is properly escaped according to its use case. Tempcode empowers theme designers to create highly customizable and dynamic websites, allowing for logic, conditional rendering, and manipulation of various website elements.

Question	What are some alternatives to Photoshop for web design?
Answer	While Photoshop is a popular choice, there are other excellent options available, including: GIMP/GIMPShop: These free, open-source image editors provide a robust set of features comparable to Photoshop. Paint.NET: This free, Windows-only software offers a user-friendly interface and essential image editing tools. Corel Paint Shop Pro: A more affordable alternative to Photoshop, Corel Paint Shop Pro delivers a good balance of features and ease of use.

Question	How can design elements like dominance and attention to detail improve a website?
Answer	Dominance and attention to detail are key to a balanced and engaging website. Important elements can be emphasized using techniques like larger text, unique colors, and increased spacing. Conversely, less crucial elements should receive less emphasis. This interplay helps guide the visitor's eye and ensures a visually harmonious layout. Attention to detail involves eliminating inconsistencies and distractions, such as typos, misaligned elements, and low-quality images, that can detract from the overall aesthetics and message of the website.

Question	What is the importance of color schemes in website design?
Answer	Color schemes are crucial as they convey emotions and brand identity. Choosing colors that align with your website's purpose can evoke desired feelings in visitors. For example, a website selling chocolates might use shades of brown to subconsciously trigger associations with chocolate. However, an environmental website would be better suited using green, aligning with pre-existing perceptions of environmentalism. It is also important to maintain consistency with your color scheme, limiting the number of colors used to avoid a conflicting and cluttered appearance.

Question	Can I use Comcode / resource IDs directly when working with the repository?
Answer	Using Comcode / resource IDs directly is not recommended as they may not match between different sites. Use GUIDs instead, which Composr automatically substitutes for IDs before parsing Comcode. You can use Commandr commands like find_guid_via_id to find the GUID for specific resources.

Question	What precautions should I take when using the Composr Repository?
Answer	Exercise caution when working with the repository: Avoid using it as the sole backup method; rely on regular database backups. Work primarily under the "var" meta-filesystem and copy specific folders/files rather than the entire repository. Do not use tools like "rsync" or Git on the whole repository without careful consideration.

Question	What are the limitations of the Composr Repository?
Answer	While powerful, the repository has limitations: Automatic syndication is not performed for content added via the repository. Multi-language content translations are not retained. Transferring complex data schemas between staging sites may have limitations. Merging separate websites into one is not supported through the repository. You should use Composr's import tool instead.

Question	How can I access the Composr Repository?
Answer	You can access the repository using WebDAV (non-bundled addon), which allows you to view it as a folder on your computer. Composr uses the SabreDAV PHP library for WebDAV functionality. However, please be aware that SabreDAV is deprecated and may not function correctly on newer PHP versions.

Question	How is the Composr Repository structured?
Answer	The repository is structured as a filesystem with various meta-filesystems mounted under a root directory. These meta-filesystems include: bin: Stores Commandr scripts. database: Provides access to the raw database. etc: Allows access to Composr configuration options. home or filedump: Provides access to the File/Media Library. home contains the files in a special JSON format with metadata filedump contains the raw files members: Lists registered members with their settings and user groups. raw or root: Provides access to the Composr installation directory. raw contains the raw files without overrides, and modifying any file modifies them directly without automatic override handling root contains the files with applicable overrides applied automatically, and Composr will automatically handle overrides and utilizing _custom directories when these files are modified var: Contains structured website resources and content.

Question	What are the benefits of using the Composr Repository?
Answer	The repository offers several benefits: Opacity: Provides a clear view of Composr's content and resource data. Tactility: Allows easy manipulation of data through drag-and-drop operations. Data transfer: Simplifies transferring data between sites. Desktop application integration: Enables using text editors and file-search tools for tasks like mass search and replace. Configuration management: Tracks changes to options and facilitates transfer between sites. Backups: Allows backing up portions of the repository. Revision control: Supports built-in and advanced revision control. Filesystem for Commandr: Acts as a file system for the Commandr command line. Resource API: Offers an abstract resource API for programmers. API for external apps: Provides an API for mobile apps and other external applications.

Statistics

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