Featured Sites: A-Z Index
H
Newest 10 Entries
Question | What are some of the default endpoints available in the server-side API? |
---|---|
Answer | Default endpoints cover various functionalities, including:
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:
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 |
|
Question | How can I provide design feedback for Composr? |
---|---|
Answer | Constructive design feedback is valuable. To provide effective feedback:
|
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:
|
Top 10 Entries
Question | How does Composr handle color contrast for accessibility? |
---|---|
Answer | Composr is designed with high graphic standards that aim to avoid poor color contrast in the default theme and Theme Wizard. But it is not perfect, especially for dark mode themes. Webmasters are still responsible for ensuring sufficient contrast in their own content and in custom themes. |
Question | How do I provide text equivalents for images and multimedia in Composr? |
---|---|
Answer | Composr's web standards checker ensures that alternative text (using the "alt" attribute) is provided for images. It will warn if any images do not contain alt text. For multimedia, webmasters are responsible for providing captions and auditory descriptions either in the multimedia itself, on the description of the media, or uploaded as a caption file. |
Question | How can I make sure my Composr website is accessible? |
---|---|
Answer | Enable the web standards checker in Composr while editing templates. Also do the same when previewing edited or new Comcode pages. Use the provided accessibility options in the Admin Zone to customize the webmaster experience according to your accessibility needs. Follow the webmaster concerns outlined in the "Helping improve site accessibility for disabled users" tutorial. Regularly test your website using third-party accessibility validation tools such as the WAVE Web Accessibility Evaluation Tool or the AChecker. |
Question | What accessibility features are built into Composr? |
---|---|
Answer | Composr has an inbuilt web standards checker that helps ensure compliance with accessibility guidelines. Composr provides automatic sitemap generation functionality, a default sitemap page, and an advanced menu editor to manage navigation. Composr supports ARIA (Accessible Rich Internet Applications), which helps make dynamic content accessible. Composr includes options in the Admin Zone to fine-tune the webmaster experience for specific accessibility requirements. |
Question | Does Composr comply with accessibility standards? |
---|---|
Answer | - Yes, Composr complies with the highest level of the WCAG (version 1.0 at the time of writing), level 3. - Composr also meets Section 508 guidelines, XHTML and CSS specifications, and the highest level of ATAG. - Composr conforms to these standards throughout, from user-facing screens to administrator interfaces. |
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 |