This template is used to create a "time-to-event" list that documents the careers of people or the development of events. Compared with direct listing, it is more concise and neat.
Usage
Basic usage
in(Time)=Event
| Code | Effect |
|---|---|
{{Timeline
|inTime = Event
|inyyyymmdd = event 1 event 1 event 1 event 1 event 1 event 1 event 1 event 1
|inmmdd = event2
|inmmdd 00:00 = event 3
|in…… = ……
}}
|
|
| Effect | |
- When actually used, all time parts in a list should use the same time unit format.
- The event section on the right is automatically aligned, leaving a blank space on the left even if the content wraps too much.
- will appear directly in the order in the code, not automatically by date.
Periods
Periodin{{color|#bbb|+}}Period{{color|#bbb|+}}Time = Eent
| Code | Effect |
|---|---|
{{Timeline
|2019
|in2019dec30 = event 1
|in2019dec31 = event 2 event 2 event 2 event 2 event 2 event 2 event 2 event 2 event 2
|2020
|in2020jan1 = event 3
|in2020jan2 = event 4
}}
|
Lua error: bad argument #1 to 'len' (string expected, got nil). |
| Effect | |
| Lua error: bad argument #1 to 'len' (string expected, got nil). |
- Note that the time period in all time parts in the code should not be omitted, the actual effect will be omitted by default, if it is still displayed, see below period parameter.
Individual long-term misalignment
inPeriodinTime = Event
If period is not used: ininTime = Event
| Code | Effect |
|---|---|
{{Timeline
|2019
|in2019nov9 = event 1
|in2019nov10 = event 2
|in2019innov11~19 = event 3 event 3 event 3 event 3 event 3 event 3 event 3
|in2019nov20 = event 4
}}
|
Lua error: bad argument #1 to 'len' (string expected, got nil). |
| Effect | |
| Lua error: bad argument #1 to 'len' (string expected, got nil). |