Greg, On Thu, May 15, 2025 at 09:36:25AM -0400, Gregory Casamento wrote: > The website has a very retro aesthetic. While this may appeal to long time > users, what it is going to FAIL to do is to attract new developers.
One comment: it has _already_ failed to accomplish this. > We should redesign it to have a more modern look... but aside from that there > are several issues. > > 1. Outdated Visual Aesthetic > 2. No Mobile Optimization > 3. Header & Navigation > > Content issues: > 4. Unclear Value Proposition > 5. Modern Use Cases Missing > 6. Developer Engagement Is Weak I agree with these major points, though how to resolve these issues may be best left to the creativity of humans. :) > No clear download section where the user doesn't have to dig. Just brought this up in the "Website Structure" thread. Maybe a "Downloads" section on the top makes more sense. > GNUstep needs the binding with swift to be useful to developers. This is a huge undertaking, and I think outside of the scope of this discussion. Maybe that could be part of a larger thread on the next major technical steps for the project. > > In the case we think subdomains are of use, I would rather gather a > > documentation site. E.g. docs.gnustep.org with different kind of > manuals > > as well as reference documentation. > > > > > > docs/deveveloper/dev whatever. Same thing. > > See my reply to Riccardo. I think they are slightly different, and we > could ultimately use both to accomplish the goal of attracting and > educating new developers. > > Part of the impasse here may be that no one but Ethan is really > contributing to the developer.gnustep.org site. Ethan opened a thread > not too long ago about this, and received zero responses. > > > We also need a better theme for the generated documentation. I would happily > contribute to the developer site, but I don't know sphinx. My way of > contributing is documenting the source. :) Before we can touch that, we must work on the content. Please see the "Wiki Updates" thread. -- Luke Lollard
