Skip to content
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

Clarifying WoT vs Thingweb #107

Closed
6 tasks done
egekorkan opened this issue Nov 15, 2024 · 3 comments · Fixed by #114
Closed
6 tasks done

Clarifying WoT vs Thingweb #107

egekorkan opened this issue Nov 15, 2024 · 3 comments · Fixed by #114
Assignees

Comments

@egekorkan
Copy link
Member

egekorkan commented Nov 15, 2024

We should do the following:

  • Join the Thingweb Community -> Join the Thingweb and WoT Community

  • Below that, add a new text saying something like: Thingweb is part of the wide W3C WoT community and ecosystem

  • 130+ Discord members text -> 130+ Members in the WoT CG Discord

  • Explanation about what is wot will in a documentation subpage: This can be a page to explain standard-compliance of Thingweb components.

  • Footer with Community Header -> Entire WoT Community (or something similar)

  • Social Media channels not owned by Eclipse Thingweb will get a superscript with an explanation below. They will be also separated with a horizontal line

Originally posted by @egekorkan in eclipse-thingweb/thingweb#8 (reply in thread)

@egekorkan
Copy link
Member Author

@benfrancis this issue is now addressed. Let us know what you think :)

@benfrancis
Copy link

@egekorkan Much better, thank you.

Again, I'm sorry if this makes the website a little less clean looking, but I think it was doing both Thingweb and the Web of Things a disservice to not make it clear that Thingweb is just one implementation of an open standard and part of a wider community.

@egekorkan
Copy link
Member Author

Thanks @benfrancis !

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 a pull request may close this issue.

2 participants