Re: Yes, particularly Glade3

So it's not a great idea to do a wiki because that was tried in the past...Got it. So what I wanna do is get that website up and with a new face. People coming by this website have several issues I can name in this post. Table of Contents: 1. Readability 1.1. Front Page Readability 1.2. Headings 1.3. ARIA 1.4. Sidebars 2. Aesthetics 2.1. First Impression 2.2. Modern, LIVING 3. Documentation 1) Readability: How People View the Content Itself Covering the issues on the site involving content layout. 1.1) Front Page Readability: This is certainly an issue given the mess of a front page we're stuck with right now. If we switch to what php.net uses, it will be much easier to tell what should be considered as details, main text, etc. I'm sure Alexandre, who is usually the man up front with posting, will appreciate these aesthetics, as they will space things out a bit and people will be able to tell with less clutter what is translated as Portuguese and what is translated as English. (As a side note, I'm wondering as to whether or not Portuguese is the same in all countries, because even English isn't the same in other countries, but it's different compared to other languages. Usually just a misplaced 's' if you're American). 1.2) Headings Headings currently add to the clutter, which when, in Alexandre's case, is not his issue, but the layout of whatever or however the webpage is rendered. I'm considering this a CSS/theming issue rather than a misplaced <h1> or <h2> tag, which gets themed by either CSS or in CMS and blogs, the theme used. This theme is last century and generally ancient when it comes to Internet years; anything as far back as 2011 can be considered ancient just because even if it ain't broke, the Internet likes to fix the problems of consumers. Advances on the Internet are made quickly, and whether other devs outside of here like it or not, PHP is a monolithic beast, but it's not going anywhere. So, by fixing this issue by replacing themes, Alexandre's posts will become hella readable compared to what they are now. 1.3) ARIA This is accessibility, and is an issue on the PHP-GTK website that is one of the many beasts out there that I'm pretty sure is one of the beasts slain by the new php.net theme, assuming it follows HTML5 standards. This means any headings will be recognized by screen readers in the right order and will comply with ARIA standards (despite my own visual impairment, though not completely blind, is something I don't know anything about whatsoever). 1.4) Sidebars I'm pretty sure with the current php.net, you can ease the clutter with just one sidebar, whereas this looks like Drupal Garland hell. I'm pretty sure I haven't used two sidebars at all since I've been making websites as far back as my noob days as a third grader without any prior knowledge of programming other than HTML. 1.5) Uggghhhh-ly Font Again something solved in the wake of the new php.net. 2) Aesthetics How people see us in the era of the Internet as it stands. 2.1) First Impression I have noticed this when I visited the site in the past, before I showed up recently. to be honest, I didn't know it was "dead." I'm probably going to be sarcastic to others out there about that when I'm out in the wild/external sites asking for help and people all of a sudden go silent and say "What?" This is one of the biggest reasons I want to do this to the PHP-GTK website. I want to do this to clarify the fact that just because you cannot judge a book by it's cover, you CAN judge a website by IT's design, look at Facebook. One button moved and it's like a total war breaks out. We need to remove the '90s stereotype because honest to God my OCD is killing me (yes, a medical condition, people need to stop using it as an excuse) and it's because I can still see those gray lines. I have a similar issue with the way reddit is designed. 2.2) Modern, LIVING We are currently standing with most as a "dead" community. People who said we were dead are going to come here and think that just yesterday we were a living, breathing 1990's website, which we're the exact opposite. So that definitely will send a ripple for anyone who visits. Also, someone should check the Wikipedia page; it's hysterical. 3) Documentation This part I need you guys to decide for me, because a wiki is definitely out of the question after the last ordeal. I also don't want to have to just be like, "Okay, this is what we're doing!" on this one in particular, because it is, I believe, the second biggest thing other than the project's code itself. So, I can revise this section once you decide how we'll clean the docs relating to PHP-GTK. Again, it might not be the most important part of the project, but it should and needs to be done, and I can very easily get that accomplished given time (scheduling, man, it sucks). But, hey, I think we're finally going somewhere with this. --MGage-- > On Jun 22, 2015, at 2:37 PM, Ben Ramsey <ben@benramsey.com> wrote: > > On Mon, Jun 22, 2015 at 12:19 PM, Gage Morgan <gagemorgan@outlook.com> > wrote: >> >> As for the website, does anyone here think a wiki would fit? Anyways, I >> partially want to retheme the website because this one still uses the >> legacy theme. So, I started with the mailing list first because I tried IRC >> and it was like radio silence out there. I just thought this looked like a >> good place to kickstart, and now look, people! > > A re-theme would be great! > > I don't think we should look to host a wiki on the PHP.net servers, though.. > Anything that requires database access or filesystem access (storing files > to disk to serve as a database) can be problematic for portability and > security reasons. We used to have a wiki, for example, and it got clogged > up with spam, so the wiki was taken down. > > Maybe we could turn on the wiki for the GitHub repo and use that instead? > > Other than my reservations about storage on the server, I fully support > website redesign efforts, and I'll help where I can. > > Cheers, > Ben