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: README.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,9 +38,8 @@ The list of events is driven by the conferences file in the `_data` directory -
38
38
39
39
**Conferences**
40
40
41
-
The file to be changed is `_data/conferences.yml`. It is NOT order-dependent.
42
-
Put your conference in the YAML file at the end.
43
-
The page will sort the conferences by `start_date`.
41
+
The file to be changed is `_data/conferences.yml`.
42
+
This file is order-dependent. Put your conference in the YAML file sorted by its `start_date`.
44
43
45
44
Here is a list of the keys that can be used:
46
45
@@ -60,19 +59,20 @@ Extra keys for the upcoming events:
60
59
*`cfp_open_date`: The date when the CFP was opened - ISO8601 formatted (yyyy-mm-dd).
61
60
*`cfp_close_date`: If there is a CFP deadline, enter that here - ISO8601 formatted (yyyy-mm-dd).
62
61
*`cfp_link`: A link to the CFP submission page.
63
-
*`status`: Typically you want to put "Canceled", "Postponed" or "To be announced" here.
64
-
*`date_precision`: Controls the precision of the `start_date` and `end_date` when the conference dates aren't announced just yet but it's confirmed that the conference is happening. Possible values: `full` (implicit default), `month` or `year`. The `start_date` and `end_date` fields still need to be fully formatted ISO8601 dates, you can put the last day of the month/year in it so it also gets ordered properly.
65
-
*`announced_on`: The date on which the conference was announced - ISO8601 formatted (yyyy-mm-dd). This date is used as the publish date for the [RSS feed](https://rubyconferences.org/feed.xml) so people can stay up to date with newly announced conferences.
62
+
*`status`: Typically you want to put "Cancelled", "Postponed" or "To be announced" here.
63
+
*`date_precision`: Controls the precision of the `start_date` and `end_date` when the conference dates aren't announced just yet, but it's confirmed that the conference is happening. Possible values: `full` (implicit default), `month` or `year`. The `start_date` and `end_date` fields still need to be fully formatted ISO8601 dates, you can put the last day of the month/year in it so it also gets ordered properly.
64
+
*`announced_on`: The date on which the conference was announced - ISO8601 formatted (yyyy-mm-dd). This date is used as the publishing date for the [RSS feed](https://rubyconferences.org/feed.xml) so people can stay up to date with newly announced conferences.
66
65
67
66
Extra keys for the past events:
68
67
69
68
*`video_link`: A url to the videos for the event.
70
69
71
70
**Meetups**
72
71
73
-
The file to be changed is `_data/meetups.yml`. It is NOT order-dependent.
74
-
Put your meetup in the YAML file at the end.
75
-
The page will sort the conferences by `date`.
72
+
The file to be changed is `_data/meetups.yml`.
73
+
This file is order-dependent. Put your meetup in the YAML file sorted by its date.
74
+
Otherwise, put the meetup at the end of the YAML file and run `rake sort_meetups`.
75
+
Please make sure to preserve any comments in the YAML file.
76
76
77
77
Here is a list of the keys that can be used:
78
78
@@ -87,6 +87,7 @@ Here is a list of the keys that can be used:
87
87
* ZZZ - timezone (e.g. CDT or EST)
88
88
*`end_time`: The end time of the event - ISO8601 formatted as (hh:mm:ss ZZZ) using same values as `start_time`
89
89
*`url`: The url for the event.
90
+
*`status`: Typically you want to put "Cancelled" or "Postponed" here.
0 commit comments