I like the idea and would be happy to help with content and ideas about layout/design.
So my 1st pass thoughts:
1. Might worth to think about making web-site colour schema lighter. I think "dark mode" is good for visual observers, say if they read forum and do visual observation at the same time. The INDI with its remote/non visual nature seems to be different situation.
2. I can definitely prepare write up (probably in Research section) about INDIHUB.space network and how to use it/contribute your images to it.
3. Responsive design - this seems to be just a choice of UI/CSS framework with responsive design built in. Integrating forum might be tricky but I think doable. I think forum is its own thing and doesn't necessary have to look exactly like Web-site.
4. When I started looking into INDI - it was very clear that I can build a lot with it. However, it wasn't clear what exactly I can build. I think it would be nice to have some page where new INDI-users would land and see the full picture of all pieces connected, something like quick start guide. Say some graphics displaying mount, OTA with main camera, guiding scope with auto guiding camera, filter wheel, motorized auto-focuser, OTA flip caps.. - how it is all connected to computer/RPI with INDI-server and then how it is controlled via KStars/Ekos. Some high level view diagram but with reference that you can connect lots of devices available on the market. I see INDI as tool to make all astrophotography equipment to be Lego-pieces, where you can build different setups. Also, users should get understanding that things like imaging sessions planner, Go-To, plate-solving, polar alignment assistance, auto-guiding, meridian flip, auto-focus and etc - all these things are already solved and automated by INDI.
Thanks everyone for the great feedback. I will try to break the main page content to several blocks, each with its own text/image as following:
1. What's INDI?
INDI Library is an open source software to control astronomical equipment. It is based on the Instrument Neutral Distributed Interface (INDI) protocol and acts as a bridge between software clients and hardware devices. Since it is network transparent, it enables you to communicate with your equipment transparently over any network without requiring any 3rd party software. It is simple enough to control a single backyard telescope, and powerful enough to control state of the art observatories across multiple locations.
+ Open Source: Available for all to contribute to and re-use under the LGPL license.
+ Cross Platform: MacOS, Linux, and Windows* support.
+ Client agnostic: Drivers are written once for all supported clients. No need to update clients when a driver adds new features.
+ Distributed Control: With INDI server/client architecture, you can communicate with devices either locally or remotely transparently. INDI accommodates intermediate servers, broadcasting, and connection topologies ranging from one-to-one on a single system to many-to-many between systems of different genre.
* Windows server support is not available.
3. Device Support
Native support for numerous astronomical devices, including:
+ Cameras: DSLR, CCDs, CMOS, Web Cameras
+ Filter Wheels
+ Adaptive Optics
+ Weather Stations
+ Spectrographs & Receivers
+ Auxiliary & DIY devices.
4. Rich Clients
When a new device is supported by INDI, it is immediately available for control by any number of INDI clients. Clients are the software you use to communicate with your equipment (e.g. KStars or PHD2). With over 22 clients under Windows, MacOS, Linux, iOS, Android, and Web, you get the freedom to choose how to run your equipment using your favorite operating system and software.
Backed by a strong and vibrant community of professionals and amateurs alike from numerous backgrounds, the INDI project is community-driven and supported. Thousands of amateur and professional astronomers rely on INDI to power their equipment across the globe, join us today!
Ok, so the above is the first draft for what we should display in the first page (each paragraph a separate block with its own image..etc). Please feel free to revise to make it more intuitive especially for new users.
Jasem, I think this is some good content for the home page, and explains quite well what the INDI system is, what clients are, and what hardware is supported. So this answers lots of questions for most users right up front.