How can I ensure my website complies with email marketing laws?
Answer
Email marketing laws like CAN-SPAM protect recipients' rights to unsubscribe. Your website must include a clear 'List-Unsubscribe' header in every email, offer an easy unsubscribe process, and respect unsubscribe requests promptly. Composr provides built-in mechanisms, including an unsubscribe endpoint and support for the List-Unsubscribe header, to facilitate compliance.
What are my responsibilities regarding user privacy?
Answer
You must have a comprehensive privacy policy that details the personal data you collect, its usage, and if it's shared with third parties. Laws like GDPR have strict requirements, including logging data access, data purging, and security measures. California law mandates specific elements in your policy, like handling "Do Not Track" requests and a clear process for communicating changes.
Composr has an automatic Privacy Policy generator block to help you get started. This is used by default.
A well-defined rules page is crucial for setting expectations for user behavior and outlining consequences for violations. It should cover a range of offenses with appropriate punishments, reference relevant laws, and assign legal responsibility to users. Composr provides default rules pages that can be customized, and this page is displayed to users upon joining the site.
What are the key legal considerations for running a website?
Answer
Several legal aspects need careful attention when operating a website, especially for large or corporate sites. These include establishing clear rules and terms of service, adhering to privacy laws like GDPR and California's regulations, managing personal data responsibly, complying with email marketing regulations like CAN-SPAM, ensuring website accessibility, addressing eCommerce regulations, and understanding liability for content and user actions.
How do data-tpl and data-view behaviors work in Composr's JavaScript?
Answer
Composr uses data-tpl and data-view behaviors for associating HTML templates and JavaScript views, respectively. This facilitates clean separation of presentation and logic:
data-tpl: Used with the $cms.behaviors.initializeTemplates function and PARAMS_JSON tempcode directive to bind JavaScript logic to HTML templates.
data-view: Used with the $cms.behaviors.initializeViews function to associate JavaScript view classes (inheriting from $cms.View) with specific HTML elements.
How does Composr implement the Model-View-Controller (MVC) pattern?
Answer
Model/API: The sources directory primarily houses scripts forming the Model/API, handling data logic and business rules.
View: Templates in themes/default/templates represent the View, responsible for presenting data to the user. Comcode pages can also be considered part of the View.
Controller: Entry scripts like index.php and site/dload.php act as front controllers, directing requests. Modules and blocks, residing in */pages/modules and sources/[mini]blocks, respectively, serve as controllers, managing user interactions and determining which View to render.
Can I translate my content into multiple languages?
Answer
Yes, Composr supports multi-language content. You can enable this feature by:
Installing multiple language packs: Make sure you have at least two language packs installed.
Enabling the Conversr multi-language option: Go to Admin Zone > Setup > Configuration > Site options > Internationalisation.
Running a Commandr command: Execute the necessary command to set up the database structure for multi-language content (unless you already enabled Support content translations when installing).
Once enabled, you can translate your content into different languages and allow visitors to choose their preferred language.
My language uses gendered descriptors. How can I handle this in Composr?
Answer
Composr offers solutions for languages with gendered descriptors:
Template editing: You can modify templates to use different language strings based on user gender. This involves adding Tempcode logic to dynamically select the appropriate string.
Custom Profile Fields: Create a Custom Profile Field for "Gender" and use it to conditionally display gendered language strings in templates.
These methods allow for flexible handling of gendered language variations.
Language strings are phrases or pieces of text used throughout Composr. They're identified by unique codenames, like WELCOME_MESSAGE. These strings are stored in .ini language files and used to display text in the user interface.
By translating language strings, you change the text displayed on your website without modifying the underlying code.
How can potential conflicts between staff members be avoided (regarding content moderation)?
Answer
Composr incorporates "conflict detection" features to prevent staff from accidentally overwriting each other's work. When multiple staff members attempt to edit the same resource simultaneously, a warning message appears, prompting communication and coordination.
Open communication and transparency are crucial. Encourage staff to share their ongoing tasks and plans with each other to prevent overlaps and potential conflicts. Utilizing shared tools like the staff checklist and private forums can further facilitate coordination.
What should be considered when assigning roles and responsibilities to staff?
Answer
When assigning roles, it's recommended to start new staff with limited responsibilities and gradually increase their authority based on performance and dedication. This fosters a sense of progression and prevents discouragement among existing staff.
Always consider the individual's skills and interests when assigning tasks. For example, someone with strong writing skills might be well-suited for managing content creation, while a technically-minded person could excel at site maintenance.
How can staff be effectively managed in a Composr community?
Answer
Successful staff management requires a mindful approach that prioritizes fostering a positive and productive environment. Key recommendations include:
Respect staff limitations: Avoid overwhelming staff with excessive workload or overly ambitious site expansions.
Active involvement: Maintain active involvement in overseeing staff activities and ensuring their effective functioning.
Open communication: Engage in regular communication, providing feedback, addressing concerns, and recognizing achievements.
Foster teamwork: Encourage collaboration and information sharing among staff members.
Lead by example: Ensure staff adhere to community rules and demonstrate expected behavior.
Empowerment and trust: Grant sufficient freedom and control to enable staff to excel in their roles.
By fostering a supportive and empowering environment, community managers can enable staff to contribute their best efforts and drive the community's success.
How should staff members be chosen for a Composr-based online community?
Answer
Choosing staff for online communities differs from traditional hiring processes due to factors like unpaid positions, varying time commitments, and remote interactions. Focus should be placed on identifying individuals with:
Genuine interest: Look for members passionate about the community and its goals.
Available time: Ensure potential staff can dedicate sufficient time to fulfill their responsibilities.
Relevant skills: Prioritize skills and experience aligned with the specific role requirements.
Maturity and discipline: Seek individuals who demonstrate responsible behavior and commitment.
Recruitment methods like directly approaching active community members or allowing the Composr points system (or the karma non-bundled addon) to identify dedicated contributors can be more effective than traditional advertising.
How can content issues be reported and addressed by staff?
Answer
Composr's content reporting system, powered by the Tickets addon, allows users to report problematic content to staff. Key features include:
Report links: "Report this" links embedded throughout the site enable users to flag content for review.
Custom reporting interface: Forums offer a dedicated interface for reporting individual posts.
Anonymous reporting: Logged-in users can choose to report content anonymously.
Ticket-based management: Reports are automatically created as support tickets, facilitating staff collaboration and record-keeping.
Comprehensive report details: Tickets include content title, type, ID, submitter information, an embedded rendering of the reported content, and the reporter's explanation.
This system ensures efficient handling of content issues, allowing staff to address concerns effectively while maintaining a transparent record of actions taken.
How can staff members collaborate effectively in Composr?
Answer
Composr offers various tools to facilitate staff collaboration:
Private forums: Dedicated forums with restricted access enable staff to discuss site operations and coordinate activities. Composr installs a staff forum by default in Conversr.
Conflict detection: When multiple staff members attempt to edit the same resource simultaneously, Composr displays warnings at the top to prevent accidental overwrites.
Staff checklist & dashboard: The Admin Zone dashboard provides a shared checklist for task management, along with space for notes and links.
Staff notifications and tickets system: Staff receive notifications about various site events, including support tickets from the "Contact Us" page, allowing for efficient issue handling.
Content notes: Staff can embed notes within Comcode or use dedicated "staff notes" fields for various content types to share information and context.
Validation and workflows: Content can be intentionally left unvalidated even by staff, enabling secondary checks before publishing. A dedicated workflows addon allows for complex approval processes with multiple stages involving different staff groups.
System-defined staff: This includes administrators and super moderators who have specific privileges within the forum/member system (Conversr).
Privilege-based staff: Anyone granted the necessary permissions for a particular situation is considered staff for that context.
Composr prioritizes flexibility by utilizing privileges over fixed roles, allowing for customized staff responsibilities. However, certain features like "staff reply" in tickets inherently rely on a pre-existing understanding of "staff."
