Skip to content
This repository has been archived by the owner. It is now read-only.

[Community feedback] Website refresh — Website structure proposal #179

fdesbiens opened this issue Aug 26, 2019 · 4 comments

[Community feedback] Website refresh — Website structure proposal #179

fdesbiens opened this issue Aug 26, 2019 · 4 comments


Copy link

@fdesbiens fdesbiens commented Aug 26, 2019

An important part of the upcoming refresh of the Eclipse IoT website is a new information architecture. This PDF contains a proposal in the guise of a diagram, which is explained further in this Google Doc.

Please have a look at both, and let us know what you think by commenting on this issue!

Copy link

@kartben kartben commented Aug 27, 2019

This is great. I think the Testbeds are an important topic and while there is a "OSS project / sample repo" aspect to them, I think they are first and foremost a showcase of how companies are adopting Eclipse IoT, and building around it, so my suggestion would be to move the testbeds under "Adopters".

Copy link

@anitabunk anitabunk commented Aug 28, 2019

I like the "Adopters" section. Great to showcase that Eclipse IoT projects are used by industry and software players. As we are also integrating adopter logos on the individual project sites, this is a nice fit and strengthens one of the core messages of Eclipse IoT ("industrial grade IoT"), which we started using for several months now.

@chrisguindon chrisguindon pinned this issue Aug 29, 2019
Copy link
Contributor Author

@fdesbiens fdesbiens commented Sep 9, 2019

Thank you to all of those who provided feedback, either by commenting on this issue or directly to me.

I tweaked the structure diagram and updated the document to reflect the feedback.

The TL;DR is:

  • The testbeds subsection has been moved under Adopters
  • Use Cases is now a top-level section

@eclipsewebmaster Let's discuss and move on to the next phase.

@chrisguindon chrisguindon unpinned this issue Oct 9, 2019
@chrisguindon chrisguindon added this to In progress in Website Refresh Oct 9, 2019
Copy link

@chrisguindon chrisguindon commented Oct 9, 2019

+1 I think the next step is creating mock up based off the approved logo and color schedule and this new structure!

I will create an issue for this!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
No open projects

No branches or pull requests

4 participants