ChiefWarrant
Supporting Member
Over time, the DIYC wiki has grown organically as new controllers, pixels, protocols, and display architectures were introduced. That growth is a good thing — but it has also resulted in duplicated content, outdated assumptions, and information that is spread across multiple pages without a clear “entry path” for newer members.
I’ve started working through some of the existing content with the goal of consolidating and modernizing information, particularly around controller selection, topology, networking, pixels, and power considerations. The intent is not to rewrite history or remove legacy information, but to organize it in a way that reflects how displays are actually built today while preserving historical context.
The purpose of this thread is to:
If you’re interested in helping, reviewing, or just providing perspective on what should (or should not) be consolidated, please reply here. Brian, if there’s a preferred process or boundaries for this type of effort, guidance would be appreciated.
Thanks to everyone who has contributed to the wiki over the years — this is about building on that work, not replacing it.
I’ve started working through some of the existing content with the goal of consolidating and modernizing information, particularly around controller selection, topology, networking, pixels, and power considerations. The intent is not to rewrite history or remove legacy information, but to organize it in a way that reflects how displays are actually built today while preserving historical context.
The purpose of this thread is to:
- Let Brian (and the admin team) know there is interest in a coordinated cleanup effort
- Identify who may want to help review, edit, or reorganize wiki content
- Provide a place to discuss structure, scope, and approach before changes are widely applied
- Avoid duplicated or conflicting edits by working from a shared direction
- Improving “entry point” pages for new members
- Reducing duplication across controller, protocol, and topology pages
- Clearly separating legacy approaches from modern practices
- Making the wiki easier to maintain going forward
If you’re interested in helping, reviewing, or just providing perspective on what should (or should not) be consolidated, please reply here. Brian, if there’s a preferred process or boundaries for this type of effort, guidance would be appreciated.
Thanks to everyone who has contributed to the wiki over the years — this is about building on that work, not replacing it.