User:Supernutorcrazy/sgWiki Buses Improvements FAQ

I (Supernutorcrazy) have received significant criticism regarding the new format, primarily concerning layout and information presentation. This document aims to clarify the changes, inform all editors about the direction moving forward, and seek your understanding and cooperation.

1. Definition of Wikipedia

Many editors in sgWiki Buses are bus enthusiasts. However, Wikipedia is not merely an Excel tracking sheet. According to Britannica, Merriam-Webster, and Cambridge Dictionary, a wiki is an online encyclopaedia that allows visitors to edit, contribute, and correct information. More specifically, an encyclopaedia is a comprehensive collection of knowledge on one or multiple subjects.

The inclusion of deployment listings, bus advertisements, and other data is valuable, but we must consider how this information is presented to the public. Is it encyclopaedic? Does it provide meaningful insight? To improve and restructure the pages, I initiated this reorganisation effort.

2. sgWiki Buses Advertisement

After analysing past editing trends, I identified two main groups of editors: one focuses on bus advertisements, while the other handles both bus deployments and advertisements, primarily focusing on deployments.

The decline in sgWiki Buses can be attributed to several factors, even before my involvement in the reorganisation. The duty roster and fleet deployment were often inconsistent and inaccurate. Even when changes in bus fleets and deployments were observed, many editors failed to update them, leading to significant gaps in accuracy. Younger editors now constitute a larger portion of contributors, further exacerbating this issue. Ironically, the most accurate information on the site was the advertisement page, which contradicts the purpose of an encyclopaedia (as stated in Point 1).

This brings me to the second point - advertisement columns. I had initially removed it thinking that it was a hindrance, and least importance of all, due to it being functioning as an Excel tracking list. After some suggestions from editors, the whole advertisements columns had been consolidate into a single page – Advertisements on Buses. I hope this makes it easier for the groups of editors to just refer to a single page rather than bookmarking so many.

3. sgWiki Buses Deployment by Model

The new format merges the former deployment page with the existing one to simplify updates. Previously, new editors often failed to update both pages when making changes. The revised format allows them to edit everything in one place, with side-by-side columns serving as a reminder to update both simultaneously.

This format also integrates all buses into a single running order, regardless of the operator, and includes liveries for all buses. Considering that some models have large fleets, each table now lists only 100 buses, with sorting functionality implemented.

Concerns about long table cells spanning multiple rows and columns were also addressed. The new livery format aims to closely replicate actual bus liveries in the registration plate column.

Additionally, feedback regarding colour blindness was considered, leading to the replacement of background colours with images to denote operators.

Mobile view remains an area for improvement, as users must scroll extensively to find information. Since mobile browsers lack user-friendly search functions compared to desktops, I encourage editors to suggest and experiment with solutions to enhance usability.

4. sgWiki Buses Deployment by Service

The sgWiki Deployment by Service is being divided into multiple pages, each dedicated to a full or supplementary service. This restructuring allows integration with sgWiki Rails (Trains), creating a more comprehensive resource rather than a standalone page. Future expansions could include planning areas, tourist attractions, and more.

Each bus service page will include first/last bus timings, nearby amenities or attractions, and service history, making it a one-stop resource. A navigation bar has been implemented at the bottom of the page for quick access based on categories.

It has come to my attention that specific duty slots may consistently use particular bus models or capacity types, regardless of operator or permanent assignment. This information will be incorporated into the new service pages, and editors are encouraged to experiment with the best way to present it.

Some editors have pointed out that this approach resembles other websites like Land Transport Guru and Bus Interchange.net. However, with detailed deployment breakdowns and precise first/last stop information for each calling point, I hope sgWiki Buses will provide an even more comprehensive resource.

During this transition, accessing certain pages may require an extra click, as services are being shifted and reorganised. Editors are working towards integrating direct access once all services have been fully converted.

4.1. New Deployment Table

Let’s take a look at the new table format and the old format.

New Format

Depot	Fleet Size	Fleet
Woodlands Depot (WLDEP)	13	3 Single Deckers	9 Double Deckers	1 Articulated
		SMB1405U SMB1487H MAN NL323F	SG6035Z SG6115B SG6141A SG6143U MAN ND323F SG5435J SG5504T SG5505R SG5517G SG5539T SG5583P Volvo B9TL	SMB8016M MAN NG363F

Old Format

Direction 1	Looping at	Depot	Number of buses	Operator	Bus Package
Woodlands Interchange	Woodlands Centre Road	Woodlands Depot (WLDEP)	13		Woodlands

Fleet
SMB1405U SMB1487H 2 MAN NL323F (1 Euro V Batch 2 / 1 Euro V Batch 3) SG6035Z SG6115B SG6141A SG6143U 4 MAN ND323F (4 Euro VI Batch 1) SG5435J SG5504T SG5505R SG5517G SG5539T SG5583P 6 Volvo B9TL (6 WEG2 Batch 4) SMB8016M 1 MAN NG363F (1 Production Batch)

Comparing the old and new table formats:

• The first table has been removed and integrated into the infobox (top-right corner), altering how information is displayed.
• The new fleet count at the top highlights the total fleet size by capacity (Mini Bus, Single Decker, Double Decker, Articulated) from total fleet size. This eliminates the need for manual tallying.
• The removal of batch-specific counts was intended to improve consistency, particularly for services with no permanent fleet assignments. The new format ensures a more accurate count of high-capacity vehicles, rather than relying on vague statements like “Any Single & Double Decker buses.”
• Previously, some editors only updated the fleet count by model but neglected batch breakdowns, leading to inaccuracies. To address this, batches have been removed while still preserving model listings.
• Counting buses by model and batch has been identified as a hassle by some editors. I invite their feedback and suggestions to address this challenge effectively.

5. sgWiki Buses History Page (Service Changes/Route)

Users have provided feedback regarding the history pages and expressed a desire to revert to the original format. Bus enthusiasts are particularly interested in how defunct service pages will be handled, with concerns about potential deletion.

There is no finalised plan for defunct service history pages, though I agree that reorganisation is necessary. However, I want to assure everyone that no pages or information will be deleted until the transition is complete.

For non-defunct bus services, there may be plans to introduce a new chronological history page documenting all service changes, together with defunct bus services. Editors are encouraged to propose and experiment with this reorganisation.

6. Table-like Pages

Readers have criticised the heavy use of tables and suggested User Interface/User Experiences (UI/UX) improvements. Rather than merely complaining online, I encourage these readers to contribute directly to sgWiki and experiment with improvements.

sgWiki uses a traditional editing format, meaning editors are restricted to basic inline styling. Newer Cascading Stylesheet 3 (CSS3) features, such as classes and pseudo-elements, are unavailable, and JavaScript is also restricted. While existing JavaScript-based plugins (written by me) are still available, they are outdated and cannot be updated or modified.

As a result, some pages may appear outdated, and unfortunately, we are limited in how much we can modernised them. Even Wikipedia has more advanced functionality than sgWiki.

7. Conclusion

In summary, I hope this document clarifies the changes and future plans. If you have any questions or suggestions, please feel free to leave them on my talk page.