In order to publish the website properly, we should use GitHub actions, at least to identify easily if there is any error building the site.

I prefer not to install/manage Ruby versions and their dependencies on my Mac and keep them safely contained in a Docker container.

If you have Docker installed on you machines then with a simple docker-compose.yaml file in the project

version: '3'

services:
  jekyll:
    image: bretfisher/jekyll-serve
    volumes:
      - .:/site
    ports:
      - '4000:4000'

You can spin up the site locally with

docker-compose up

Without needing to install Ruby and manage it.

Note: there are various Docker images that help you do this, I picked bretfisher/jekyll-serve at random from a quick Google search but if open to this I can review and choose a good candidate image to provide this feature.

Based on the number of JUGs we have... it will be really great to paginate all the "records" to be able to paginate all of them.

Also, it would be great to be able to offer a search feature to find exactly the JUG the user wants.

Currently, only Twitter handles are parsed in the website for each JUG md file.
Not all JUG uses Twitter as the main social platform.
Including other social media platforms like Facebook or others can be included in the parsing.

The website looks very different right now in the current public website VS when it is rendered local.

We must use the same style everywhere and therefore be able to render the website properly (in local and in remote)

We agree to have a dedicated page that enables each JUG around the world to fill in the following information:

• Name (*)
• Location (*)
• Website (*)
• Social media
  • twitter (*)
• Recurrent events
• Newsletter
• Q&A (redirect to the general Q&A section)

(* recommended to have)

The metadata for the map can be coming from the proposed structure defined in #5

Add a JUG index page order alphabetically by Country.
For example, the jugIndex will contain a reference to git/jugs/Global/JUGS/M/

Taking into consideration that one Country can have 1-*(to many) JUGs, the proposal for the tree structure is:

.
└── Global
    ├── JUGS
    │   ├── G
    │   │   └── Guatemala
    │   ├── M
    │   │   └── Mexico
    │   │       ├── JUG-1
    │   │       └── JUG-2
    │   ├── S
    │   │   └── Spain
    │   └── aTemplate.md
    ├── LICENSE
    ├── README.md
    └── jugIndex.md

Overall steps:

• Under git/jugs/Global/JUGS/G/Guatemala create the JUG landing pageGuate-JUG.md containing as a minimum the information described in the JUG template (currently available in this PR: #3)
• Feel free to promote on Social media that you open a PR to encourage more JUGs to start creating PR's ;)

The current footer has references to jekyll github and jekyllrb twitter accounts:

In terms of footer content (without focusing yet on design), my suggestion is to have at least:

1. Existing JUG mailing list https://jugs.groups.io/g/jug-leaders [This is already part of the footer]
2. Link to jugleaders slack https://jugleaders.slack.com/
3. Twitter: https://twitter.com/WWJUGs
4. Contribute! link pointing to website repo readme file: https://github.com/World-Wide-JUGs/GlobalWWJugs

Current map page: https://world-wide-jugs.github.io/GlobalWWJugs/map doesn't render the map properly.

It seems to be related with the service we use for map returning a 403 https://github.com/World-Wide-JUGs/GlobalWWJugs/blob/gh-pages/map.html#L54

This issue doesn't occur when running the site locally.

cc: @icougil