-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where are the files? #11
Comments
Hi @eslindsey The content is stored in a CMS; this repo is just the styling and some static pages. See for example here: website/responsive-child/style.css Lines 205 to 252 in 4d753b1
However if you'd like to find some icons and/or write some CSS in a pull request, it shouldn't take us long to style the rows to show which connectivity they use. N.B. some, such as Stageprofi, support multiple connectivity methods (USB and network). |
@peternewman I had intended to do the legwork and fix the page myself, but it's just as easy for me to contribute the information here for someone else to upload. I'll leave the choice of icon/styling up to whoever designs the website. Here is the info I've come up with:
Please note the Milford Instruments link leads to a "domain for sale" landing page. The reason I wanted this additional information was because I am looking for a single package network to DMX unit. Is there really only one such device on this entire list? And none that support serial? |
Given it's a rather dumb CMS, I should have just asked you to submit some HTML! I'm not sure we really go as far as having website design. Sadly Milford Instruments has been shut down. The 1-463 Milford unit is serial, as are the Renard Serial Protocol bits (well I think they can be either). If you want network to DMX, people generally buy a node that supports one of the DMX over Ethernet protocols listed further up the page. |
I'm trying to update https://www.openlighting.org/ola/ to add indicators for which devices are USB, Network, and Serial, but I don't see the source code anywhere.
The text was updated successfully, but these errors were encountered: