Improve landing page and add screenshots/videos pages#88
Conversation
|
This seems to remove the reference to Openbox. I think Just a personal opinion: This somewhat reads like an advertisement to me rather than an explanation of the project and core philosophy behind it. I am very much a fan of organic growth, spreading by word of mouth rather than trying to convince people to use something or throwing buzzwords around. I like the original version better. No issue with addition of the screenshot page though. Embedding the YT videos rather than simply linking them *might* be an issue in regards to GDPR. Curious about opinions of @tokyo4j and @jlindgren90. |
|
Agree with keeping the reference to Openbox. It feels like the old description was more focused on "doing one thing well" whereas the new is more about (as it says) "virtually everything [...] being configurable." Maybe it reflects the project's direction having evolved a bit as it has gotten more popular. Not a judgment (good or bad), just an observation/impression. |
Good point. Have restored the first two paragraphs of the original page - which includes the 'inspired by Openbox'
Good point 😄 Have restored the original feel. So the main addition now is the screenshots + videos.
Didn't know that, but good point. Will change to links. |
I guess I was soul searching a bit and trying to reflect that the narrative might change a bit with time. Anyway, I think it's a good pointer and have found a middle ground 😄 |
Leading with limitations ("does not support...") frames the projects
defensively instead of communicating value. Whilst operating within
limits is often fundamental for good Engineering design, it feels more
appropriate to unpack this at the gh repo README.md rather than on the
website index page.
854dc0d to
ba4b985
Compare
|
Okay, how about this then? Ready for review/merge from my perspective. |
|
LGTM |
|
LGTM. Landing page might feel a bit empty without a screenshot but we can adjust it later if it turns out that way. |
Leading with limitations ("does not support...") frames the projects defensively instead of communicating value. Whilst operating within limits is often fundamental for good Engineering design, it feels more appropriate to unpack this at the gh repo README.md rather than on the website index page.