Can I use the calendar as a personal diary and keep my entries private?
Answer
Yes. When adding an event to the calendar, you can choose to make it public or private. Private events are generally used when someone wants to use the calendar system as a diary.
When adding or editing an event, you can enable reminders for yourself and specific user groups. You can also choose how much notice you want for each reminder.
Members can subscribe for reminders on an individual event screen. They can also personalize their reminder settings, including removing reminders or having multiple reminders at different times.
Members can also subscribe for notifications to specific event types to be notified whenever events under those types are scheduled.
How can I schedule Commandr commands to run automatically?
Answer
To schedule commands, create an event with the "System command" event type. This option needs to be enabled in the configuration first. In the event details, you can specify either a URL for Composr to call or a snippet of Commandr code to execute. Be sure to disable the WYSIWYG editor for this type of event. You'll also need to have the system scheduler configured for the commands to run automatically.
What do I do if a recurring event needs to be changed or skipped?
Answer
Composr has a "fixing an event" feature to handle changes to recurring events. This is useful if an event needs to be cancelled or rescheduled. You edit the event as if it were a new, standalone event and choose the "Edit with fixing past recurrences" option. This separates the past occurrences from the modified event, ensuring future recurrences reflect the changes.
What is the "recurrence pattern" and how does it work?
Answer
The recurrence pattern is a powerful tool that defines how often an event repeats. While it might seem complex at first, it provides a lot of flexibility. Think of it as a binary code where each digit represents a time period (like a day or week). A "1" indicates the event occurs, and a "0" means it doesn't. This lets you create complex schedules like "every weekday" (daily with pattern 1111100 if it starts on a Monday) or "every other Tuesday" (weekly on Tuesday with the pattern 10).
Through the Admin Zone or Content Management Zone: Go to Admin Zone > Content > Calendar.
Directly on the calendar: Click on a date box on the calendar view.
Using the "Add Event" button on any calendar view.
Deleting events can be done at the bottom of the event's edit form. You have options for recurring events, such as editing/deleting the specific occurrence, editing/deleting future ones, or all of them.
You categorize events using "Event types". Composr provides default types like "Anniversary", "Appointment", "Birthday", "General", "Public Holiday", "Task", "Vacation", and the special "System command" for executing Commandr commands. You can also add your own custom event types to suit your specific needs, such as "Appraisal Session" for a business website.
What is an "event" in the Composr calendar system?
Answer
An event is any entry in the calendar. Importantly, an event isn't limited to a single point or range in time. Events can recur based on a schedule you define. This makes them very flexible – they can represent anything from one-time appointments to recurring birthdays or even weekly team practices.
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.
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.
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.
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.
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.
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.
