splash issueshttps://gitlab.fabcloud.org/fabevent/FAB16/splash/-/issues2019-12-12T21:40:58Zhttps://gitlab.fabcloud.org/fabevent/FAB16/splash/-/issues/2Clean up .gitlab-ci.yml2019-12-12T21:40:58Zviktorsmariviktorsmari@smartcitizen.meClean up .gitlab-ci.ymlNormally, Jekyll builds the website and puts everything in one folder `_site`
The `_site` folder should normally be in `.gitgnore` - in our case it is not.
Also the `gitlab-ci.yml` is doing things differently then the default:
https:...Normally, Jekyll builds the website and puts everything in one folder `_site`
The `_site` folder should normally be in `.gitgnore` - in our case it is not.
Also the `gitlab-ci.yml` is doing things differently then the default:
https://gitlab.com/pages/jekyll/blob/master/.gitlab-ci.yml
We could clean it up, or keep it like it is?
Also, find a way so we can have both pages working fine:
* http://fab16.org/
* http://fabevent.fabcloud.io/FAB16/splash/
djangossouldjangossoulhttps://gitlab.fabcloud.org/fabevent/FAB16/splash/-/issues/1Create a branch for pushing content2019-11-07T01:12:02ZdjangossoulCreate a branch for pushing contentAs the FAB16 website management is separated in 2 parts (Montreal for the content & FF for the infrastructure), could it be a good workflow to create a second branch "staging" or "content" ?
This way, the Montreal team could :
- push new...As the FAB16 website management is separated in 2 parts (Montreal for the content & FF for the infrastructure), could it be a good workflow to create a second branch "staging" or "content" ?
This way, the Montreal team could :
- push new contents : texts, images and video urls
- (ideally preview the staging site on a subdomain)
- request a merge
And then, the FF team could approve (or not) the merge to make it online
How does it sound for you @fibasile ?