-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
one-page-site? #2
Comments
Hm. One page site would make sense, but content you listed is already more than content for a single page. At least "link to...." sections are something that can get long for a single page. Some juicy citations are also something that should probably not go on the main page as it can eventually become a long list (I hope 😛 ) I agree with the rest. |
adding a few sentences for the home page in #3 i think step is to layout the mission statement in a nice way and have a prominent, large button linking to the documentation. and some visual thing, as soon as we have a logo. then the other single page things could go below the fold. link to could be link to the according packagist searches. and we might highlight some specific notable things if we want. general news should be covered by showing the latest tweets, to keep content maintenance effort low. |
Some github/twitter badges. (Maybe twitter badge is enough, no need for latest tweets: it might be hard to colorize twitter box, etc) |
to avoid duplication, i would suggest we limit the website as much as we can. it should explain what this is about and motivate people to dig into HTTPlug, then point them to the right resources. things i would see:
@HTTPlug
The text was updated successfully, but these errors were encountered: