Featured Sites: A-Z Index

H


Newest 10 Entries

Name Philip Withnall
Title / Role Early Developer
Contributions / Notes

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

Name Allen Ellis
Photograph Image
Title / Role Founder
Contributions / Notes

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

Name Robert Goacher
Photograph Image
Title / Role Founder
Contributions / Notes

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

Name Chris Graham
Photograph Image
Title / Role Founder
Contributions / Notes

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.

Links

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

Website Earth & Sky
Screenshot Image
Short Description Earth & Sky is a Composr v11 gallery website showcasing natural photography by Mark Brunner.
Website Saving Wallden
Screenshot Image
Short Description This is an informational website for a Visual Pinball X game in development called "Saving Wallden". The site features the planned game rules, development news, and a download of the game as it is so far.
Website PDStig, LLC
Screenshot Image
Short Description This is an informational site / portfolio for PDStig, LLC, the company run by one of Composr's lead developers, Patrick Schmalstig.
Website Composr CMS: Content management meets social media
Screenshot Image
Short Description This is the main website for Composr CMS version 11. It runs the latest build of v11. Currently it is just a placeholder but will soon replace compo.sr when v11 becomes stable.
Question Should I use the bleeding edge releases or the git repository?
Answer

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

Bleeding edge releases Git repository (v11 branch)
Easier to set up and use, and does not require knowledge of git Harder to set up and use unless you are familiar with git; must routinely run the file integrity check, database upgrade tool, and check database schema tools in the upgrader after pulling
More stable, but less frequent updates Less stable, but more frequent updates (almost daily!)
Only contains core code and addons unless you manually install non-bundled addons; non-bundled addons must be manually updated Contains all core code and non-bundled addons; non-bundled addons are updated with pulls (though you will need to check file/database integrity often and check blocks/modules for available upgrades)
Ability to test the upgrader / upgrading between new v11 versions Not able to effectively test the upgrader because git pull might load in and update new code early before the release is available
Always contains the latest files.bin and db_meta.bin because these are compiled with every release Does not always contain the latest files.bin and db_meta.bin. Therefore, file and database integrity may report false-positives.
Intended for general user testing Intended for developers / developer testing:
* special run-time checks are enabled for extra debugging (if the .git directory exists in the install)
* contains the automated test suite for running tests

Click here to access the git repository.
Question Can I switch a v11 install from git over to using the releases from composr.app?
Answer

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.

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.