coopdevs / coopdevs-old-web Goto Github PK

We currently set the text of the blog posts justified to both sides. This causes undesirable wholes on the composition which break the rhythm of the reading. As we won't carefully and manually fix the lines that contain them, it's best to justify the text to the left by default.

In order for the medium to long blog posts not to feel like a massive block of text, we should scale images to be narrower than the text. This provides a nice dynamism to the layout which will make readers find the blog post less boring.

It'd be great to speed up CI runs with dependency caching. Circle CI has documentation about it in https://circleci.com/docs/2.0/caching/#full-example-of-saving-and-restoring-cache, https://circleci.com/docs/2.0/language-ruby/ and https://circleci.com/docs/2.0/language-javascript/.

I'm pretty sure we can even find examples of static sites running on Circle CI and see how they deal with this.

Note we install dependencies with both bundler and yarn.

https://github.com/coopdevs/coopdevs.github.io/blob/be1a2f40d1647f6109afa013764f354e55c2924a/_i18n/ca.yml#L25

The text width in the blog for desktop devices it feels a bit too narrow. It has 589.84px wide while it should be somewhere around 700px to get a better readability.

With the current line height, the paragraphs are hard to read and discourage reading the whole blog post. Short line heights are known to decrease readability.

The recommended line height is between 1.5 and 2 and we now have 1.5

The line length is too large and makes it hard too read text on wide screens. See below

This is the standard Coopdevs screen we bought recently ☝️

I get the following warning on my inbox every time I deploy:

The page build completed successfully, but returned the following warning for the master branch:

The custom domain for your GitHub Pages site is pointed at an outdated IP address. You must update your site's DNS records if you'd like it to be available via your custom domain. For more information, see https://help.github.com/en/articles/using-a-custom-domain-with-github-pages.

For information on troubleshooting Jekyll see:

https://help.github.com/articles/troubleshooting-jekyll-builds

Amb l'Albert de Megafon vam arribar a la conclusió de que aquest text no s'entenia

Optimització de processos empresarials
Analitzem i optimitzem processos empresarials per a cooperatives, fomentem la intercooperació en els processos que impliquen les TIC.

La meva proposta de millora:

Millora de processos empresarials
A partir de les dades que genera la vostra activitat empresarial, analitzem la situació actual i us proposem millores de processos i eines tecnològiques per tal d'assolir els vostres objectius.

Com ho veieu @sauloperez @enricostano @danypr92

This stems from #31 (comment).

As we want to have people other than devs to write on our site, it's important to have the build and deploy happen elsewhere, not in people's machines. While we're able to setup the project on our dev machines, others don't.

Also, it's less error-prone to trust these steps to a 3rd party service/server so no conflicts with dependencies or problems with the dev machine stop you from deploying.

There's not enough room between paragraphs, videos and images. The media placed between paragraphs needs to breathe a bit more. Check out http://coopdevs.org/2018/04/24/Por-fin-llegamos-A-la-casilla-de-salida.html to see an example.

we need human pictures on our website... 😈

We should remove the following styling

https://github.com/coopdevs/coopdevs.github.io/blob/20a38b214ffc201f17ba7f00f79ec16dfeacfad5/_includes/footer.html#L1

to a TailwindCSS color in

https://github.com/coopdevs/coopdevs.github.io/blob/20a38b214ffc201f17ba7f00f79ec16dfeacfad5/_includes/tailwind.config.js#L6

as gray 100. I don't see any DOM element using the existing gray 100 so we should be able to replace it.

We want to bring in what we learned in https://github.com/coopdevs/katuma-landing-page about setting up a dev env that helps contributors running windows.

We need to copy here the Dockerfile and docker-compose.yml files and then properly document in the README as we did in that repo.

Using a grey text body provides a better readability on white backgrounds (due to reduced contrast) and improves the hierarchy of the page making the titles and images stand out a bit more.

We need a way to keep the selected language in all the page

We probably will do articles in different languages and we want search engines index it properly with html lang atribute

In #31 we start using a Jekyll plugin that is not supported by Github. This means we can no longer rely on Github's build process and we have to do it ourselves locally and then push the static files to Github pages.

We can use something similar to https://gist.github.com/SirRawlins/8684701 or https://gist.github.com/motemen/8595451 to automate this process.

Another solution could be to use Travi's Github pages deployment support but it feels a bit overengineering to bring an extra dependency on a 3rd party service to do this.

There is this "Prueba" section on the README that seems a forgotten thing. Should I remove it?

https://github.com/coopdevs/coopdevs.github.io/blob/develop/README.md#prueba

https://developers.facebook.com/docs/sharing/webmasters

Desde la Federació de Cooperatives ens demanen que actualizem el logo amb la nova imatge

https://www.cooperativestreball.coop/sites/default/files/materials/somcoop1.png

Maybe we should use the official PAM a PAM banner, I suggest the round one:

https://pamapam.org/ca/baners-pam-pam/

Thoughts?

Analitzant el menú principal se m'acut que podria ser molt més útil amb els següents canvis:

1. Moure els idiomes al peu
2. Menú afegint 2 links

• Quí som (de moment link a https://coopdevs.org/2018/04/24/Por-fin-llegamos-A-la-casilla-de-salida.html)
• Blog
• Comunitat
• Contacte (de moment mailto:[email protected])

I have noticed that if we open the hamburguer menu and do the screen big without closing it by clicking, we have two visible menus.

We need to change the office place from the description text in the home page.

Replace Espai30 by Coworking Nogués

We use "-" in title for subtitle, for example Blog post title would be "Coopdevs - Blog post title" in home we want to remove it.

title should change dynamically, in posts is the title of post

We need to use the default.new layout for the 404.html page.

The trick here is that it looks like this if we only replace the Jekyll layout variable