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

Complete redesign of tessel.io #102

Open
11 tasks
Frijol opened this issue Sep 1, 2016 · 5 comments
Open
11 tasks

Complete redesign of tessel.io #102

Frijol opened this issue Sep 1, 2016 · 5 comments

Comments

@Frijol
Copy link
Member

Frijol commented Sep 1, 2016

What are we doing?

Re-implementation of the tessel.io website both to have both simpler, more maintainable code, and to better highlight the current state/goals of the project.

Primary goals

  • Clarify what the Tessel project is (not a business). Homepage primary objective should still show what Tessel is, but call to action should orient around getting involved with the project. (Changes to main page to guide more toward open source #6)
  • Current node.js implementation is overcomplicated, consider moving to a static (or otherwise simpler) implementation

Secondary goals

  • Fast page loading
  • Better handling of modules, particularly permalinks for ordering per module order links should be a variable #70
  • Highlight J5IK per Different order links? #90
  • Roll the hardware-modules repo into this repo (not useful for it to exist separately)
  • Show the project is not just for hardware people, it's for everyone to get involved in (including designers, web devs who don't have specific interest in microcontrollers, etc.)
  • Reconsider the "Trusted By" section
  • Would be great to be able to have links to educational material (ie Sparkfun's endeavors)

Implementation details

  • What architecture should we use to emphasize simplicity?
  • How do we create great support for redirects? (some JSON thing?)

How to get involved

We would really like help from designers, copy editors, and people who are good with usability.

  1. Get an account on Tessel Slack and join the #website-wg channel
  2. Message the channel with a brief message about why you're joining the Learning WG and what you're interested in working on
  3. Work away! Message in any relevant Slack channel if you'd like help or direction.
  4. Attend the regular Website WG meeting (to be scheduled) to see what others are working on, be part of the community, get help, and share your own progress

Other

Using hoodiehq/hood.ie#312 as an example of a great issue defining redesign of this type.

Some related issues which this redesign should include: #6 #15 #70 #90

How to join the Slack channel

In the Slack webapp or desktop client, click the word "CHANNELS".
screen shot 2016-09-07 at 12 28 29 pm

Search for "website" and the #website-wg channel should pop up. Click to join.
screen shot 2016-09-07 at 1 04 21 pm

cc @HipsterBrown @reconbot

@rwaldron
Copy link
Contributor

Some kind of "updates" or "releases" or "latest commits" page?

@Frijol
Copy link
Member Author

Frijol commented May 23, 2017

Re: improving visibility of contributor pathway #112

@Akshitaag
Copy link

Hii , I along with my teammate @Rahmeen14 would love to work on redesigning the tessel website as a part of RGSoC 2018.

@Rahmeen14
Copy link

Rahmeen14 commented Feb 18, 2018

Hi! Yes, we would love to contribute to the website to make it better. Both of us have been working together for over 7 months now and have built several projects in node. We can assure you of our sincere participation during the SoC

@sreshu
Copy link

sreshu commented Feb 26, 2018

Hi! Me and team partner @miniamisha would love to contribute in designing the website. Already versed with JS,HTML,CSS,MySQL and my team-mate has good experience with hands on python integration with hardware too. We are applying to solve tessel issues for application of RGSoC'18.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants