Update website with project pages and documentation #8
Comments
|
Maybe the website can be converted to Github Pages with a custom domain for easier deployment |
|
Sounds good to me 👍 |
|
+1 |
|
indexing each unique project? I know what you mean but I think the current site is nice because it grouped projects.. I would even argue that reviewing the current list for updates/creates shouldn't be overlooked if/when it goes to gh-pages.
|
|
A small page + some introduction examples for each project under the reactphp namespace:
Yes that is a lot of pages but if we have one place for new users to start and reference the project as a whole is more accessible. The current frontpage would stay the same the idea is to add more pages. |
|
👍 |
Big 👍 for updating this, as I share the view that the current website makes the project look quite dead.
Big 👍 for making contributing to this as easy as possible and trying to eliminate any barriers.
👎 While this sounds like a good idea to me, I expect this to take a non-trivial amount of work to set up and maintain. Instead, I would vote to keep this as simple as possible and reference the individual project pages.
👍 IMHO this is quite spot on and adds no unnecessary duplication (single source of truth). After all, even the simple README.md for each component is often slacking behind, so I would rather invest time there. |
|
I took a few minutes to do a quick mockup: http://sorgalla.com/reactphp.github.io/ Please don't comment on the content, it's just some copy & paste for now. |
|
@jsor looking good! 👍 I have some ideas, will try and make a PR tonight |
|
Great! In case anyone is wondering, the repo is here: https://github.com/jsor/reactphp.github.io |
|
Looking good. I'd suggest taking the FAQ point about threading out though :) |
My bad. I should RTFM before replying. 🙃 |
|
Mine are content and design wise, but more as in adding content and I'll wrap them in different PR's while adding a screenshot with preview |
|
Updates: Removed the FAQ section, added footer and code example. |
|
On mobile the components look off.
|
|
By the way I do like the implied event loop in the logo 👍 |
|
@WyriHaximus Yes, as i said, this is just a quick mockup and nothing is fully worked out 😃 It's only about the general direction it is going, like the logo, colors, typography. If noone is having strong objections, i'm going to work it out. Regarding the logo: the R stands obviously for React, the red line is both a P (for PHP) and a symbol for the loop. |
|
@jsor hah sorry I'm jumping the gun a bit 😄 . Very well done! I have no objections to the style, colours and overall feel. |
|
I'm a big fan of your mockup and I think this is very good first step and very much worth working on 👍 I also do like your suggested logo (and its reasoning), but I'm not sure this is something we should change prematurely, so I'm having to 👎 this for now and would love to discuss this in a separate issue first. |
|
Development now happens in https://github.com/reactphp/reactphp.github.io. Preview at https://reactphp.github.io. |
|
Thanks @jsor! 🎉 Unfortunately, we now have two repos housing our website :) A) Can we merge the two repos into one? B) I guess we can mark this repo as deprecated and redirect people to the new repo instead? I think open A) is more appealing as it causes less confusion. What do you think? |
|
A) 👍 |
|
👍 This looks amazing. However, I would like to see a dedicated page with documentation and examples for each component. Bouncing people out to github for docs, creates a confusing and inconsistent user experience. |
|
Absolutely, but I think we should focus on the logo and colours first. |
|
We've just launch the new website via #11 http://reactphp.org/ so closing this |
One of the criticisms made against reactphp is the lack of documentation. Currently the website shows a small example on making a webserver while there is a lot more to the project. My suggestion is to add project pages for each component on the website and add simple getting started examples. This to make the learning curve easier.
The text was updated successfully, but these errors were encountered: