Continuous integration and deployment works fine in the ohlwebsite.
Andre and I found an issue with regard to the domain name itself. I can recall the details but I think is in an older issue.

The current solution

Commit changes and automatically push to the current production website.

Setup this following these steps:

1. Go to .git\hooks folder in your local ohlwebsite repository. Make sure to unhide these folder if is hidden.
2. Go to post-commit file and replace its current code with the following code:

#!/bin/sh

# abort on errors
# set -e

# load .env
# eval "$(cat .env <(echo) <(declare -x))"

# build
npm run build

# navigate into the build output directory
cd dist

# if you are deploying to a custom domain
# echo 'www.example.com' > CNAME

git init

echo "openhardware4.me" > CNAME

git add -A
git commit -m 'deploy'

git push -f https://github.com/Open-Hardware-Leaders/open-hardware-leaders.github.io.git master

cd -

git push origin

3. (Recommended but not compulsory for now) Test your change also locally running npm start.
4. Make your commits normally and the production repo will be updated automatically.

Hi Everyone, as there has been some difficulties and legit pains with updating the website in Github, I took some time to explain the problems that cause them.

1. The issue with updating the website is not related to the selection of Vuepress or whatever static site generation. The gitlab instance we had worked perfectly because the continuos integration is easier in Gitlab.

2. I tried Github with Actions for continuous integration but it didn't work. So I did how the github web page hosting has been used normally. You basically build the website from the src generating html, and css and running the index.html from gh-pages branch. The main issue I faced was related to changing the remotes and some reference issues with the branch. To solve this I basically had to make a completely new branch and rebase.

3. About the selection of the static site generator: There are several reasons why I started using vuepress:

• Vuepress it is meant for documentation and it has great integration with markdown,
• Vuepress is powered by Vue (a very user friendly and powerful javascript framework), which allows to build easily new functionality and customization.
• I happen to use Vuepress and have a background on Vue so that helps in maintaining the website.
• There are indeed other options, including Hugo which looks great, but you have to peek an option, I don't know GO, which I could learn, neither React, so for the sake of pragmatism I stayed with Vuepress.

👉 For more info on static site generators and how Vuepress is ranked check here a table of comparisons.

Please let me know what issues you encounter in the following:

1. Deploying locally
2. Pushing with the deploy shell

Hi all and welcome!

This week we have presented you with some real case studies and history of open source.
We encourage you to talk about how this reflects in your project.

Here are some questions to get you motivated to comment:

• What learnings have you got from working on your core team?
• How have you found space and resources in your own context to work on your project?
• What things have made your initiative sustainable?
• What challenges are you facing with regard to expanding your community of adopters?
  .......

Make the website https

• Remove the "cohort is running itll May 2020..." tagline
• Add a section for the news in the mainpage

For the added section, I propose the following text:

Important news
Open Hardware Leaders, what happens next

After the graduation of the first cohort and 14 weeks of collaborative work, the organization team has decided to split ways. The differences in our vision are too significant, taking us into this joint decision after much effort on working them out.

OHL was initially an idea and an effort of four people (plus all the volunteers!), and in the spirit of collaboration and openness, we understand no one owns it. So we propose the experience of OHL stays online and open as a pilot project, a repository available for anyone to fork.

The organizers continue working on their different ideas for future hardware programs: "Open Hardware Devs" -led by Jose Urra- and "Open Hardware Makers" -led by Andre Chagas, Alex Kutschera and Juli Arancio-.

Learn more about our decission here. (link to "next cohort" section)

New programs

Open Hardware Devs - Learn more: contact [email protected]

Open Hardware Makers - Learn more at openhardware.space

My proposal of looks (forgot to center both programs info, a detail):

@amchagas had an error when using the sh script at the root.
Apparantely is a common issue and a solution here

It should be open hardware leaders, it still says open leaders for hardware