-
Notifications
You must be signed in to change notification settings - Fork 11
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
Implementation of the Get Involved pate #103
Merged
egekorkan
merged 2 commits into
eclipse-thingweb:master
from
SergioCasCeb:sergio-get-involved-page
Nov 8, 2024
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
--- | ||
sidebar_position: 1 | ||
slug: / | ||
--- | ||
# Get Involved | ||
|
||
:::info | ||
|
||
For the moment the Get Involved page is still under construction. For more information about Thingweb Community refer to our social media accounts located in the website footer. | ||
|
||
::: | ||
|
||
There are various ways to get involved via GitHub : https://github.com/eclipse-thingweb | ||
|
||
You can pick one of the Eclipse Thingweb components such as [node-wot](https://github.com/eclipse-thingweb/node-wot) or [playground](https://playground.thingweb.io) and start using them. Even better, you can contribute to their source code! Below are some examples of what you can contribute with: | ||
|
||
* node-wot: Create and contribute your own protocols bindings besides HTTP, CoAP, Websockets, ... | ||
* playground: Add tools that take Thing Descriptions and generate developer tooling for other systems | ||
* All components: Report any issue you encounter (and even better, provide a fix) | ||
|
||
## Licenses | ||
|
||
All Thingweb components are licensed with [Eclipse Public License v. 2.0](https://www.eclipse.org/legal/epl-2.0/) and [W3C Software Notice and Document License (2015-05-13)](https://www.w3.org/copyright/software-license-2015/). You can pick the one that suits your requirements (i.e. you only have to comply with one, not both). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
const sidebars = { | ||
getInvolvedSidebar: [ | ||
{ | ||
type: 'autogenerated', | ||
dirName: '.' | ||
} | ||
], | ||
}; | ||
|
||
export default sidebars; |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of playground I would now refer to td tools in both occasions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not see this change request. I will get it done tomorrow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mhh, maybe it does make sense to list all our tools ... what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Call today: In order to avoid maintaining two lists, we can simply link to the landing page tools section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the components list and added a link to the tools section on the landing page