Just let me drop my thoughts about developer.gnustep.org. It is no technical challenge to have both: developer.gnustep.org and www.gnustep.org/developer and show the same content. Same for docs.gnustep.org
It is just a different URL/URI. And URLs should not really be typed in or human readable - they are a technical detail to organize The Web and locate resources. Search Engines, QR-codes, AI tools try to hide them completely for users because you search by content or advertisement. Important is the content and how information is grouped (and linked internally and externally). > Am 16.05.2025 um 04:41 schrieb Gregory Casamento <[email protected]>: > > Luke, > > On Thu, May 15, 2025 at 6:41 PM Luke Lollard <[email protected]> wrote: > 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. > > As I believe I made clear in my reply. I was speaking of the present and > what it has ALREADY failed to do. > > 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. :) > > I used AI and a small company which does this to do the assessment. Nowhere > in my discussion here did I say that AI should do it. So, yes, absolutely. > What I posted I wouldn't have put it up here if I didn't agree with it. > > 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. > > Understood. > > 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. > > Yes, agreed. > > > 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. > > Understood. I haven't looked at that thread, but will. > -- > Luke Lollard > Yours, GC > -- > Gregory Casamento > GNUstep Lead Developer / Black Lotus, Principal Consultant > http://www.gnustep.org - http://heronsperch.blogspot.com > https://www.patreon.com/bePatron?u=352392 - Become a Patron > https://www.openhub.net/languages/objective_c > https://www.gofundme.com/f/cacao-linux-a-gnustep-reference-implementation
