Skip to content

Improve landing page and add screenshots/videos pages#88

Merged
johanmalm merged 1 commit intomainfrom
new-landing-page
Apr 1, 2026
Merged

Improve landing page and add screenshots/videos pages#88
johanmalm merged 1 commit intomainfrom
new-landing-page

Conversation

@johanmalm
Copy link
Copy Markdown
Member

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.

@Consolatis
Copy link
Copy Markdown
Member

Consolatis commented Mar 31, 2026

This seems to remove the reference to Openbox. I think Openbox inspired should keep being mentioned as IMHO its an important part of labwc.

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.

@jlindgren90
Copy link
Copy Markdown

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.

@johanmalm johanmalm changed the title [RFC] index.md: improve landing page Improve landing page and add screenshots/videos pages Apr 1, 2026
@johanmalm
Copy link
Copy Markdown
Member Author

This seems to remove the reference to Openbox. I think Openbox inspired should keep being mentioned as IMHO its an important part of labwc.

Good point. Have restored the first two paragraphs of the original page - which includes the 'inspired by Openbox'

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.

Good point 😄

Have restored the original feel. So the main addition now is the screenshots + videos.

Embedding the YT videos rather than simply linking them might be an issue in regards to GDPR.

Didn't know that, but good point. Will change to links.

@johanmalm
Copy link
Copy Markdown
Member Author

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.

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.
@johanmalm
Copy link
Copy Markdown
Member Author

Okay, how about this then? Ready for review/merge from my perspective.

@jlindgren90
Copy link
Copy Markdown

LGTM

@Consolatis
Copy link
Copy Markdown
Member

LGTM.

Landing page might feel a bit empty without a screenshot but we can adjust it later if it turns out that way.

@johanmalm johanmalm merged commit 0c44b8c into main Apr 1, 2026
@johanmalm johanmalm deleted the new-landing-page branch April 1, 2026 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants