You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _includes/BHD.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ <h3 class="section-heading">What is Brainhack Donostia?</h3>
13
13
14
14
<pclass="text-muted" style="font-size: 20px"> A gender-balanced board of researchers from BCBL invites you to join a three-day in-person workshop focused on project development to foster new ideas, findings and future collaborations. In addition, we will host four international keynote speakers that will share their experience on state of the art methods, good practices in science and hot topics in research nowadays. By doing so, we will continue to grow our contributions towards sharing knowledge openly and transparently across disciplines and specialties, and to the development of open-source tools. <br/>
15
15
Accessibility to science is an important objective for BHD and we are determined in making this year's event more inclusive and open. Following last year's organization, a real-time transcription system will be provided during all talks and tutorials in order to ensure fluid and intelligible subtitles for deaf and hard of hearing participants. This system is also a valuable aid for all those participants who are not native speakers of English. <br/>
16
-
BHD 2024 will award travel grants to help cover travel and registration costs for the event. Through these travel awards we want to encourage and promote the participation of junior scientists who have less access to fundings. Awards will be assigned based on statements of purposes provided by the participants themselves, which will be assessed by our committee. If you would like to be considered for one of these travel grants, feel free to click on the following button and to fill out the form. You will be asked to write a short statement of purpose on why you believe this grant could help you attend BHD 2024. <br/>
16
+
BHD will award travel grants to help cover travel and registration costs for the event. Through these travel awards we want to encourage and promote the participation of junior scientists who have less access to fundings. Awards will be assigned based on statements of purposes provided by the participants themselves, which will be assessed by our committee. If you would like to be considered for one of these travel grants, feel free to click on the following button and to fill out the form. You will be asked to write a short statement of purpose on why you believe this grant could help you attend BHD. <br/>
17
17
The deadline for the statement of purpose submission is the 8th of November. The grants consist in refunds for travel or registration costs after the event. If you have any questions about this process, feel free to contact us at [email protected] .</p>
18
18
19
19
<divclass="container">
@@ -28,7 +28,7 @@ <h3 class="section-heading">What is Brainhack Donostia?</h3>
28
28
<h3class="section-heading">
29
29
Open Science projects in Neurosciences </h3>
30
30
31
-
<pclass="text-muted" style="font-size: 20px"> Brainhack Donostia is not an ordinary conference but an event focused on cooperation and collaboration in Neuroscience, as well as the promotion of Open Science. Our aim is to explore the multiple applications of neuroscience from a cross-disciplinary perspective. With this goal in mind, we bring together students, researchers, users, and non-academic industry professionals to learn about and develop collaborative projects. BHD 2024 is an opportunity to learn new skills and create long-lasting collaborations with interesting people from various backgrounds with a strong interest in Open Science. <br/>
31
+
<pclass="text-muted" style="font-size: 20px"> Brainhack Donostia is not an ordinary conference but an event focused on cooperation and collaboration in Neuroscience, as well as the promotion of Open Science. Our aim is to explore the multiple applications of neuroscience from a cross-disciplinary perspective. With this goal in mind, we bring together students, researchers, users, and non-academic industry professionals to learn about and develop collaborative projects. BHD is an opportunity to learn new skills and create long-lasting collaborations with interesting people from various backgrounds with a strong interest in Open Science. <br/>
32
32
These projects are proposed by the attendees for the attendees, and can be in any stage of development (i.e, it can be just an idea). Any attendee can propose any number of project, but can only lead one. The presenter of the project is responsible for making sure that anyone can contribute to the project, regardless of their level of expertise and background knowledge in programming. If possible, the project leaders should try to define some 'beginners' tasks'. We firmly believe that every single one of the attendees has something valuable to contribute to any project and we can't wait to see what it will be!</p>
Copy file name to clipboardExpand all lines: _site/README.md
+98-46Lines changed: 98 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,59 +7,115 @@ The resulting jekyll theme uses Ruby >=2.5, GCC and Make.
7
7
8
8
For more information on specific OS setting see: https://jekyllrb.com/docs/installation/
9
9
10
+
*IMPORTANT NOTE!* MacOS have a preinstalled ruby version that is not gonna work. Follow the official jekyll documentation to install other one outside main system. Finally, if you can't exec the server try runnin bundle update so that it uses the gems you already have *DO NOT PUSH GEM CHANGES TO MASTER!*
I definetly suggest you working with ssh keys so that you dont need to prompt any password everytime you push. For that check [ssh-key linux] (https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent?platform=linux) or [ss-key mac](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent?platform=mac).
22
23
23
-
-To check local changes or to display on a local host
### To check local changes or to display on a local host
46
+
47
+
48
+
bundle exec jekyll serve --trace
24
49
25
-
$ bundle exec jekyll serve --trace
26
50
27
51
or
28
52
29
-
$ jekyll serve
30
53
31
-
#Git branches
54
+
jekyll serve
32
55
33
-
Commit and push changes on BHD2023 or a personal sub-branch from there. When you are sure about your changes, push them to BHD2023 and open a pull request.
56
+
57
+
# Git branches
58
+
59
+
Commit and push changes on BHD2025 or a personal sub-branch from there. When you are sure about your changes, push them to BHD2025 and open a pull request.
34
60
35
61
**NOTE: remember to run pull before working locally**
36
62
37
-
-Changing to BHD2023 branch
38
-
$ git checkout BHD2023
63
+
### Changing to BHD2025 branch
64
+
65
+
66
+
git checkout BHD2025
67
+
68
+
69
+
### Creating your sub-branch from BHD2025
70
+
71
+
72
+
git checkout -b YourAmazingSubbranch
73
+
39
74
40
-
- Creating your subranch from BHD2023
41
-
$ git checkout -b YourAmazingSubbranch
75
+
### Checking the status of the current branch
42
76
43
-
- Checking the status of the current branch
44
-
$ git status
45
77
46
-
- Adding untracked changes
47
-
$ git add filename1 filename2
48
-
or to add all
49
-
$ git add .
78
+
git status
50
79
51
-
- Commit changes
52
-
$ git commit -m "Your message explaining your commited work"
53
80
54
-
- Push changes from locall to repo
55
-
$ git push -u origin BHD2023
81
+
### Adding untracked changes
56
82
57
-
- Merging with master
58
-
$ git checkout master
59
-
$ git merge BHD2023
60
83
61
-
- You could also push your commit to a specific branch intead of merging and without checkout master
62
-
$ git push -u origin master
84
+
git add filename1
85
+
86
+
87
+
or to add all (not recommended)
88
+
89
+
90
+
git add .
91
+
92
+
93
+
### Commit changes
94
+
95
+
96
+
git commit -m "Your message explaining your commited work"
97
+
98
+
99
+
### Push changes from locall to repo
100
+
101
+
102
+
git push -u origin BHD2025
103
+
104
+
105
+
### Merging with master (only if you know what you are doing)
106
+
107
+
108
+
git checkout master
109
+
110
+
111
+
git merge BHD2025
112
+
113
+
114
+
### You could also push your commit to a specific branch intead of merging and without checkout master. Then you merge from the website GUI
115
+
116
+
117
+
git push -u origin BHD2025
118
+
63
119
64
120
## How to use
65
121
@@ -74,34 +130,35 @@ Within such folder you will find several html named after the section they stand
74
130
Your amazing second paragraph. </h3>'
75
131
76
132
77
-
###Portfolio
133
+
###Portfolio
78
134
79
135
Portfolio projects are in '/_posts'
80
136
81
137
You need to create a markdown for each post. The files must be named something like this:
0 commit comments