Difference between revisions of "User talk:Dragomir7"
Jump to navigation
Jump to search
m |
|||
| Line 24: | Line 24: | ||
::[[User:Supernutorcrazy|Supernutorcrazy]] ([[User talk:Supernutorcrazy|talk]]) 12:08, 7 March 2025 (+08) | ::[[User:Supernutorcrazy|Supernutorcrazy]] ([[User talk:Supernutorcrazy|talk]]) 12:08, 7 March 2025 (+08) | ||
:::Well, the issue is that users who come here tend to want to search bus services by theme, for example old CSS services, or old Nightrider services, for example, and not necessarily by time (because they might not easily recall which year a certain service was changed or withdrawn), if you remove the articles that you mentioned, then users would have a hard time specifically finding those services and have to look at each and every year article. I'd say retain the current format, unless you have a better suggestion that can address the concern above then share it here. | :::Well, the issue is that users who come here tend to want to search bus services by theme, for example by specific service number, or old CSS services, or old Nightrider services, for example, and not necessarily by time (because they might not easily recall which year a certain service was changed or withdrawn), if you remove the articles that you mentioned, then users would have a hard time specifically finding those services and have to look at each and every year article. I'd say retain the current format, unless you have a better suggestion that can address the concern above then share it here. | ||
:::If you do intend to create a bus change log that is visible on every year article, then my suggestion would be to use [https://en.wikipedia.org/wiki/Help:Transclusion transclusions], put the relevant content in one article then call it in the year article's section. Or alternatively, put the changes for each year in templates with a collapsible header (prevent clutter), put the relevant one in each year's article, then have a separate dedicated article that calls all of these templates (or otherwise, an article for every decade) such that those that want to look at the entire chronology can do so at one go without having to jump across articles. | :::If you do intend to create a bus change log that is visible on every year article, then my suggestion would be to use [https://en.wikipedia.org/wiki/Help:Transclusion transclusions], put the relevant content in one article then call it in the year article's section. Or alternatively, put the changes for each year in templates with a collapsible header (prevent clutter), put the relevant one in each year's article, then have a separate dedicated article that calls all of these templates (or otherwise, an article for every decade) such that those that want to look at the entire chronology can do so at one go without having to jump across articles. | ||
:::And of course, please do put the necessary articles under an appropriate section (two equal signs). [[User:Dragomir7|Dragomir7]] ([[User talk:Dragomir7|talk]]) 12:20, 7 March 2025 (+08) | :::And of course, please do put the necessary articles under an appropriate section (two equal signs). [[User:Dragomir7|Dragomir7]] ([[User talk:Dragomir7|talk]]) 12:20, 7 March 2025 (+08) | ||
Revision as of 12:22, 7 March 2025
History
Hi,
I was wondering what if for the history pages, what if we combined it into the pages like:
instead of transclude to the main page, with the main history page becoming chronological order?
— Preceding unsigned comment added by Supernutorcrazy, 03:46, 7 March 2025 (UTC)
- @Supernutorcrazy: I think that would be too much work, because most services' routes don't actually change that much across years so if you want to take snapshots every year there will be a LOT of duplication for services. The way the pages log the changes to each service right now is fine, if only a bit too colourful for my liking (I liked the old text-only version better, with at most some bus op logos).
- If you intend to log route changes, the most that you could do would be to follow what landtransportguru has on their page, but as a standalone article; combining it into each year article would make it way too cluttered; be mindful that this wiki doesn't only cater to buses or transport, after all. At most just put a link in the year article.
- Just my two cents. (Also you might want to consider signing your comments with four tildes "~".) Dragomir7 (talk) 12:00, 7 March 2025 (+08)
- @Dragomir7 I not saying to log snapshot for every year, but like what you pointed out like their page, while keeping the old history page for a consolidate of defunct service (reduce pages), with the rest into the individual page (no transclusion).
- The difference here in sgWiki yearly page provide a chronological order, and also can merged with other pages (for example, MRT/LRT, places of attractions etc.) because is sgWiki (singapore wiki) not bus wiki.
- Supernutorcrazy (talk) 12:08, 7 March 2025 (+08)
- Well, the issue is that users who come here tend to want to search bus services by theme, for example by specific service number, or old CSS services, or old Nightrider services, for example, and not necessarily by time (because they might not easily recall which year a certain service was changed or withdrawn), if you remove the articles that you mentioned, then users would have a hard time specifically finding those services and have to look at each and every year article. I'd say retain the current format, unless you have a better suggestion that can address the concern above then share it here.
- If you do intend to create a bus change log that is visible on every year article, then my suggestion would be to use transclusions, put the relevant content in one article then call it in the year article's section. Or alternatively, put the changes for each year in templates with a collapsible header (prevent clutter), put the relevant one in each year's article, then have a separate dedicated article that calls all of these templates (or otherwise, an article for every decade) such that those that want to look at the entire chronology can do so at one go without having to jump across articles.