This commit progressively enhances the co-op grid to show the contents
of the `/co-op/<id>` page in a HTML `<dialog>` element. This improves
the existing experience by retaining the scroll position and returning
the user to the correct page when the dialog is closed.
In case JS isn't available, and for SEO purposes we link to the co-op
pages as previously (but with the disadvantage that the "close" button
always returns to the homepage irrespective of where the co-op grid is
used).
Natasha and I went through the design together and made a number of
small tweaks.
In particular we removed the responsive line-height in favour of a
fixed one at all screen sizes.
I've decided to style these pages to look like "modals" for now, but I
haven't implemented them as such yet. I think we might be able to add
some progressive enhancement to retain the scroll position when a
co-op logo is clicked to make it feel more like a separate modal
dialog is opening.
I think it's probably easier to start from a cleaner slate for this
redesign, rather than try to incrementally refactor towards the new
design. Some of the base styles are fine and I've retained some of the
CSS variables. I've also kept the header as it probably will be useful
to refactor rather than completely re-do this.
In the new designs we are no longer showing services, clients,
technologies, member counts, maps, addresses, email addresses or
social links for our member co-ops. So we can remove this metadata
altogether.
Before this commit the logos were a fairly garish mixture of different
colours, and many of the logos didn't work very well on a white
background.
In keeping with the new brand guidelines we've applied a greyscale
filter to the logos, and Natasha has created some variants of the
existing logos that work better on a black background. I've decided to
keep all the original logos and their variants in case we want to
switch again later, and chosen which one to used based on my taste.
This seems to improve things and we can ask co-ops to provide us with
higher res logos that work on black backgrounds later if we want to
improve things further.
Co-authored-by: Natasha Natarajan <natasha@outlandish.com>
I took the SVG favicon from the brand assets pack Creative Coop
produced and put it through an online tool[1] to
generate these files.
[1] https://realfavicongenerator.net
Creative Co-op have recently prepared some brand guidelines for
CoTech, including a new logo, typography suggestions and background
images. This commit restyles the site to apply, as best we can, these
guidelines. It's hard to split this into smaller commits because the
decision to use a black background colour means many things have to
change.
Notably we've removed the "about/join" footer, as it was hard to
choose a bg colour and without one it became more apparent that this
footer was more in the way than useful.
Co-authored-by: Natasha Natarajan <natasha@outlandish.com>
Rather than attempt to recreate the exact burger menu from the old
version of the site, since it requires a number of dependencies, I've
added a burger menu with some inline javascript to handle the toggle
states.
I used Claude 4 to help generate the CSS here.
The site had around 7000 lines of CSS and 23,000 lines of JS. It also
used a framework called "Zurb" to build the layout. We're planning to
rebrand the website and to make that work easier I think it would help
me (and hopefully those that come after me) to strip out all of these
technologies and recreate the site with a simple stylesheet.
By doing so I think we lose a couple of features, such as the zooming hover
states on the grids of images. Some features, like the "sticky" header
are probably better implemented nowadays in pure CSS.
Given that the site is maintained by volunteers I think the simpler we
can make it the better.
Ruby 2.6.6 has reached the end-of-life and I had some trouble
installing the dependencies locally as a result. I've updated to the
latest version of ruby and regenerated the Gemfile.lock with the
latest versions of the two gems we depend on, and their dependencies.
Everything looks to still be working in terms of site generation.
This seems to have been inadvertently broken in this commit [1]. Perhaps
even the GitLab Web IDE was confused by the "duplicate" image files...?
[1]: f0f0c3aea7
Both Blake House and Open Data Services were already using lowercase
version of the Power to Change client markdown and image files, i.e.
`_clients/power-to-change.md` and `images/clients/power-to-change.png`.
So the uppercase versions of the files, i.e.
`_clients/Power-to-Change.md` and `images/clients/Power-to-Change.png`,
were effectively duplicates.
This led to the following warning messages on case-insensitive
filesystems, making it hard to work on the project on such systems:
> warning: the following paths have collided (e.g. case-sensitive paths
> on a case-insensitive filesystem) and only one from the same colliding
> group is in the working tree
In this commit, I've added the website from `Power-to-Change.md` into
`power-to-change.md`, deleted `Power-to-Change.md` &
`Power-to-Change.png`, and changed the reference in `dot-project.md`
from `Power-to-Change` to `power-to-change`. I think this is the right
thing to do, because ideally all the markdown files should be lowercase
in case they are used in URL paths.
Although no coops seem to be referencing this client, there were already
lowercase versions of the relevant files, i.e. `_clients/kaspersky.md`
and `images/clients/kaspersky.svg`. So the uppercase version,
`Kaspersky.md` was effectively a duplicate.
This led to the following warning messages on case-insensitive
filesystems, making it hard to work on the project on such systems:
> warning: the following paths have collided (e.g. case-sensitive paths
> on a case-insensitive filesystem) and only one from the same colliding
> group is in the working tree
In this commit, I've deleted `Kaspersky.md` which didn't contain
anything different to `kaspersky.md`. I think this is the right thing to
do, because ideally all the markdown files should be lowercase in case
they are used in URL paths.
There are other similar issues, but I plan to address them in separate
commits.
Both Blake House and InFact were already using lowercase version of the
CAST client markdown and image files, i.e. `_clients/cast.md` and
`images/clients/cast.png`. So the uppercase versions of the files, i.e.
`_clients/CAST.md` and `images/clients/CAST.png`, were effectively
duplicates.
This led to the following warning messages on case-insensitive
filesystems, making it hard to work on the project on such systems:
> warning: the following paths have collided (e.g. case-sensitive paths
> on a case-insensitive filesystem) and only one from the same colliding
> group is in the working tree
In this commit, I've added the website from `CAST.md` into `cast.md`,
deleted `CAST.md` & `CAST.png`, and changed the reference in
`dot-project.md` from `CAST` to `cast`. I think this is the right thing
to do, because ideally all the markdown files should be lowercase in
case they are used in URL paths.
There are other similar issues, but I plan to address them in separate
commits.
This repo is [hosted at git.coop](https://git.coop/cotech/website) and [push mirrored to GitHub](https://github.com/cotech/jekyll-website).
If you would like to contribute to this repo you have two options:
1. [Join Webarchitects](https://webarch.coop/join) to [create an account at git.coop](https://webarch.coop/git#free) and then request access to the [CoTech group](https://git.coop/cotech) and when that has been granted you can update this repo directly.
2. Use a GitHub account to create a [pull request](https://github.com/cotech/jekyll-website/pulls) at GitHub and then ask someone who is a member of [Webarchitects](https://www.webarchitects.coop/) to [patch the repo for you](https://community.coops.tech/t/cotech-website-repo-mirroring-to-github/2818).
## Introduction
## Introduction
This is a port of the current WordPress version of the CoTech website to a statically-generated site using Jekyll. The site consists of a bunch of markdown files and images stored in git.coop. The Jekyll build process is automated so that there is no need to have Jekyll installed and running to make changes to the site.
This is a port of the old WordPress version of the CoTech website to a statically-generated site using Jekyll. The site consists of a bunch of markdown files and images stored in git.coop. The Jekyll build process is automated so that there is no need to have Jekyll installed and running to make changes to the site.
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
