Howdy, Hopefully my fellow Americans aren't too sleepy from feasting on turkey.
There was a thread regarding GNUstep PR earlier this year, which spawned another conversation. In one of those, Greg requested that Steven and I work on a concept for a website redesign. This is now online with GitHub Pages: https://haihige.github.io/gnustepwebsite/ Please note that this rough draft is more about the structure and content of the website than the look. The source is on GitHub, and the site can still be viewed while navigating the directories on GitHub: https://github.com/haihige/gnustepwebsite The overall concern of this (to steal a line from Steven): Everything you need; nothing you don't. - Home page: clearly, quickly describe what GNUstep is, and direct readers to the other pages for more details. - About: the least developed section, but this would contain general information about GNUstep's features, architecture, history, etc. - Gallery: showcase solid examples of software created with GNUstep. - Blog: a place for news and developer posts. - Community: how to contribute and help out. - Docs: guides, educational resources, documentation, etc. I think the Docs section is the most important, and eventually the largest, part of the website. What happened to the original plan? The thought was to update the wiki first. Riccardo was very helpful, answered many questions that I had, and was instrumental in getting me access. However, after reviewing the wiki with Steven and discussing with Greg, we came to the conclusion that it wasn't worth it for now. The wiki was slow and unstable (often not loading at all), making it difficult to work with. There was lots of broken and unorganized information; essentially with no clear structure. There's definitely some good information on the wiki (so we shouldn't delete it), but it doesn't seem like many are interested in maintaining it. One of the current issues with the website and wiki is that many links are external and now broken. Instead, I propose we bring as much information as possible directly into the GNUstep website (see `/docs/developer/articles` and `/blog/articles`). The focus is on providing and preserving educational resources for Objective-C and Cocoa. Why move to internal resources? - A user can pull down the whole repo and have these resources offline. - We can own them, continue to improve them, and ensure that they stay with us; instead of becoming a burden of dead links. - archive.org leaves a not-so-great impression on visitors: it's often slow to load and if the information isn't still live on the Internet, some may think that it isn't valuable any more. But, for some things it may still be necessary. There are a ton of great resources from the peak of the Objective-C Cocoa era (2000-2015). Many of these have been archived on archive.org or GitHub. If you think this is heading in the right direction, pull requests are welcome. :) -- Luke Lollard
