Managing the Flock Website

Adrian Edwards (moralcode), Justin W. Wheeler (jflory7)

This document provides instructions for managing the Flock conference website, which was recently redesigned to align with the Fedora website’s design language and leverage existing infrastructure, including the CMS, community translations, and a unified navbar.

Website Structure

The Flock website’s content is divided into two primary sections to cater to different user needs:

  • Main page: This section provides general information about Flock for new contributors and those unfamiliar with the conference.

  • Year page: This section contains specific details about the Flock conference in a specific year.

Each year of Flock will have its dedicated page under the /flock directory (e.g., /flock/2025, /flock/2026, etc.).

CMS Features

Migrating the website to the CMS enabled the implementation of several useful features, including:

  • Toggle switches for showing/hiding website sections, allowing for content relevance management.

  • Alt text and attribution fields for images, improving accessibility and copyright clarity.

Known Issues and Future Improvements

The following areas require further attention:

  • Call for Proposals (CFP) Section: The CFP section within the CMS has been disabled and may contain unresolved issues. Testing is required before enabling this feature.

  • "Thank You" Section: A dedicated "thank you" section for quick activation is currently absent.

Future development will focus on creating a new page for each year of the conference. The process for adding these pages is described in the following section. While the CMS supports dynamic page creation, this approach was not used for Flock 2024 to minimize complexity.

Adding New Flock Year Pages

Adding a new year page for a future Flock conference involves modifying both the CMS and the main website repositories. The process is detailed below:

CMS Repository Changes

  1. Fork the CMS Repository: Fork the Fedora websites CMS repository.

  2. Copy and Paste Event Data: Copy the Flock event data block from the events.yml file (starting around line 421 and ending before the next event block). Paste this block below the existing Flock event entries.

  3. Modify Event Data: Update the first three lines of the copied block to reflect the new year (replace X with the appropriate year).

    label: "Flock 202X"
name: "flock-202X"
file: "/content/events/flock/202X.yml"

  4. Duplicate Event Content File: Navigate to the /content/events/flock directory within the repository. Duplicate the existing year’s YAML file (e.g., 2024.yml) and rename it to match the new year (e.g., 2025.yml).

  5. Commit and Create Merge Request: Commit your changes to a new branch and create a merge request to the main CMS repository for review.

Website Repository Changes

After the CMS changes are merged, the following steps are required to update the website:

  1. Fork the Website Repository: Fork the main Fedora websites repository.

  2. Duplicate Page File: Duplicate the existing year’s page file (e.g., /pages/flock/2024.vue) and rename it to match the new year (e.g., /pages/flock/2025.vue).

  3. Update Page File: Inside the new page file, modify the second line to point to the new year’s CMS data (replace X with the appropriate year):

    const data = await getCMS("events/flock/202X");

  4. Commit and Create Merge Request: Commit your changes to a new branch and create a merge request to the main website repository. Ensure this merge request is submitted after the CMS merge request to avoid website errors.

CMS Management

Following the above procedures, all other website updates should be manageable directly within the CMS interface.

Want to help? Learn how to contribute to Fedora Docs ›