The "About Us" section of our website requires updates to reflect current information and changes within our group. There are several updates needed, including modifying the organiser section, updating the Slack channel information, and considering changes proposed in ticket #19.

Details

Update Organiser Section:

• Addition: Please add Kyle Harrison to the list of organisers.

• Deletion: Remove Stephen McCullough and Paddy Carey from the list of current organisers as they are no longer actively managing the group.

• New Section: Consider creating a new section for past organisers, where we can move Stephen McCullough and Paddy Carey to recognise their contributions to the group.

Slack Channel Information:

The Slack channel currently mentioned on the website is the Irish Tech Slack. However, we should update this to point to the Northern Ireland Tech Slack channel, which is more relevant to our group.

Ticket #19 Consideration:

If the changes proposed in ticket #19 are actioned, please ensure that the updates mentioned in this issue are still applicable and integrated accordingly. If ticket #19 is not actioned, please proceed with the updates in this issue regardless.

Action Required:

• Update the "About Us" section on the website.

• Add Kyle Harrison to the list of organisers.

• Remove Stephen McCullough and Paddy Carey from the current organisers.

• Create a new section for past organisers and move Stephen McCullough and Paddy Carey there.

• Update the Slack channel information to point to the Northern Ireland Tech Slack channel.

• Review ticket #19 and ensure that the updates in this issue are compatible with any changes proposed in that ticket.

Rationale:

Updating the "About Us" section and the organiser information is essential to provide accurate information to our community members, recognise the contributions of past organisers, and direct members to the appropriate communication channels.

Let's prioritise these updates to ensure our website accurately represents our group and its current state.

Description

As a developer,
I want to upgrade the outdated software currently used to create and maintain the PyBelfast website,
So that we can improve the security, efficiency, and maintainability of the website, while ensuring it's up-to-date with current best practices and compatible with modern browsers and devices.

Tasks

• - Upgrade ruby to 3.1.2
• - Upgrade gems

Jekyll has been a great tool for generating our static website, but it is built on Ruby, and as a Python group, it would be more consistent and beneficial for us to use a Python-based alternative. There are several Python-based static site generators available that offer similar functionality and can seamlessly integrate with our existing workflow.

Suggested Solution:

• Evaluate Python-based static site generators: Review and select a Python-based static site generator that best suits our needs. Some popular options include Pelican, MkDocs, and Nikola.

• Migrate existing content: After selecting an appropriate static site generator, we need to migrate the content from our Jekyll-based site to the new platform. This may involve converting markdown files, updating templates, and adjusting configurations.

• Update build and deployment scripts: As part of the transition, we should update our build and deployment scripts to work with the new static site generator.

• Testing and validation: Ensure that the new site works as expected, including checking for broken links, formatting issues, and any other inconsistencies. Perform thorough testing across different browsers and devices.

• Update documentation: Update our internal documentation to reflect the change in technology and provide guidance on using the new static site generator.

Benefits:

• Consistency: Using a Python-based static site generator will align with our technology stack and programming language preference.

• Easier Maintenance: Our team's familiarity with Python will make it easier to maintain and customise the site.

• Community Engagement: Transitioning to a Python-based solution may encourage more contributions and engagement from the Python community.

Actions Required:

• Discuss and decide on the most suitable Python-based static site generator for our needs.

• Assign a team to handle the migration process, including content migration, template updates, and configuration changes.

• Update the build and deployment scripts to work with the new static site generator.

• Test and validate the new site.

• Update documentation and communicate the change to relevant stakeholders.

By transitioning to a Python-based static site generator, we can stay true to our technology stack, encourage more community engagement, and make it easier for our team to maintain and customise the site.

Let's start planning and execute this change in a smooth and timely manner.

The current site is written using Jekyll. We should probably use a python site generator. I think pelican is the best choice but am not picky. Here is a list of static site generators in python.

This would be a great issue to get started for a first time contributor. If you need anyhelp #pybelfsat on the NI Slack channel is a great place to start.

I identified a bug in our Sass files where the division operation (/) is used outside of the calc() function. This usage is deprecated and will be removed in Dart Sass 2.0.0. As a result, the affected code may become incompatible with future versions of Dart Sass, leading to errors and unexpected behaviour.

Steps to reproduce:

Run the jekyll server - bundle exec jekyll serve
Open the relevant Sass files.
Search for instances where the division operation (/) is used outside of the calc() function.

Expected behaviour:
Division operations should either be within the calc() function or replaced with the appropriate alternative.

Actual behaviour:
Division operations are used outside of the calc() function, which is deprecated.

Impact:
This issue may lead to errors and unexpected behavior when using Dart Sass 2.0.0 or later versions.

Suggested solution:
Update the Sass files to either move the division operations within the calc() function or replace them with the appropriate alternative, such as the math.div() function.

It is important to address this bug as soon as possible to ensure compatibility with future versions of Dart Sass and avoid potential errors.