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 | How can I customize Composr without modifying the core files? |
---|---|
Answer | Composr offers a robust override system. Instead of altering the original files, create a parallel structure within _custom directories. For example, to modify site/pages/modules/polls.php, place your customized version in site/pages/modules_custom/polls.php. The tutorials outline additional information on how to utilise overrides. |
Question | What are the main components of the Composr framework? |
---|---|
Answer | Composr consists of:
|
Question | How can I embed third-party widgets into my Composr pages? |
---|---|
Answer | Composr supports embedding widgets from various websites, like Google Maps, Vimeo, and YouTube, by simply pasting the URL. For manually embedding widget code, you can paste it into the HTML source view of the WYSIWYG editor or within Comcode html tags if not using the WYSIWYG editor. |
Question | What is the difference between blocks and boxes in Composr? |
---|---|
Answer | Boxes are visual elements that provide a container for content, while blocks are functional units that generate and display dynamic content. Although blocks often appear within boxes in the default templates, they are not inherently tied to any visual representation. |
Question | Can I customize the appearance of blocks? |
---|---|
Answer | Yes, you can style blocks by editing the associated templates and CSS. Templates are typically named after the block they represent. For example, the main_news block uses the BLOCK_MAIN_NEWS.tpl template. |
Question | How do I create custom filter forms for my content? |
---|---|
Answer | The main_content_filtering block can help you generate filter forms automatically. You can use it to create a default form and then customize the generated Filtercode string to refine the filtering options. Once satisfied, you can either continue using the block or extract the HTML and modify it further. |
Question | Where can I use Filtercode and Selectcode in Composr? |
---|---|
Answer | Filtercode is supported in various blocks, such as main_multi_content, main_gallery_embed, and main_cc_embed. It's also actively used in modules like catalogues, downloads, galleries, members, and news. Selectcode is supported in blocks and Comcode tags that explicitly mention it, including the main_multi_content block and the if_in_group Comcode tag. |
Question | What is the difference between Filtercode and Selectcode? |
---|---|
Answer | Filtercode is used for querying content based on properties and values, while Selectcode is used for directly specifying a list of IDs or categories to include or exclude. Filtercode offers more complex filtering options, while Selectcode is more straightforward for simple selections. |
Question | How can I filter content in Composr? |
---|---|
Answer | Composr provides two filtering systems: Filtercode and Selectcode.
|
Question | What are blocks in Composr and how can I use them? |
---|---|
Answer | Blocks are dynamic elements that can be inserted into Comcode pages to add interactive and data-bound functionality to your website. They are essentially reusable components that automatically generate content, such as recent forum posts or information about the logged-in user. You can add blocks to your pages using the block construction assistant, which allows you to select from a list of available blocks, set their parameters, preview them, and generate the necessary Comcode. |
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:
|
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:
|
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:
|
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:
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:
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:
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:
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:
There are two main types of cookies:
|