• 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

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

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

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

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

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

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

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

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

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

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

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

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.

gameRevolt (@[email protected]) - LinuxRocks.Online

That depends on several factors. Here are some pros and cons of each:

It is not recommended you do this because you may run into issues. For example, some changes were made in crypto_master.php and data/upgrader2.php prior to the first v11 alpha. These changes will result in a broken upgrade unless you already pulled these changes from git. Similar situations could happen in the future as well.

It is recommended you either discard the git install and use a fresh install from the Downloads, or to maintain a git install and a bleeding-edge release install separately. Do not combine the two.