Contributors: A-Z Index

A

Name Photograph Title / Role Contributions / Notes
Allen Ellis Image 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 Image 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 Image 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 Image 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 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.

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