# Open Source Design website Review

**URL:** <https://discourse.opensourcedesign.net/t/open-source-design-website-review/773>\
**Category:** Open Source Design meta\
**Created:** [November 4, 2018, 1:35pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-website-review/773 "2018-11-04T13:35:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cameralibre](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/cameralibre/32/82_2.png) [@cameralibre](https://discourse.opensourcedesign.net/u/cameralibre)\
**Post date:** [November 4, 2018, 1:35pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-website-review/773/1 "2018-11-04T13:35:22Z")

</div>

From the session at the Summit!

_ **This post is a wiki, you can edit it! - click on the ‘📝 Edit’ icon at the end of the post** _

First impressions: ok, it’s a design site, but this site is boring! where is the color, the fun, the animation?

- **Events** & **Summit** should be the same

- **Goals** could be the **Manifesto** - or the manifesto could be on the front page - or would that be too much content?

- The landing page should direct people to where they want to go, so maybe the manifesto should be suggested but not forced upon the reader.

- OSD is people! if newcomers want to find us, they need to find and engage with the forum. We could add a **Call to action: Join the forum!**

- **Articles** and **Resources** (and possibly **Projects** ) could be the same: links to resources, tools, articles, frameworks

- It’s great starting the resources page with **FREE STUFF FOR YOU!** (noun project, free fonts etc). That way the benefits are immediately apparent and experienced.

- The **Learn to Code** , and **Learn to Design** sections should start with a good article about ’ _Why_ You Should Learn to Code / _Why_ You Should Learn to Design’

- **DESIGNING.MD** - encourage projects to have design-specific contributing instructions, maybe provide a template?

Keeping the events etc up to date is a lot of work! Can we do it on Open Collective and embed them on the website?

We could also embed our tweets?

Maybe we could have a 2-sentence intro to the forum on the front page, ie. _‘In our forum you will find [Events](link to Events category on the forum), and you can [Introduce Yourself](link to intro thread) to the community…etc etc’_

Proposed navigation links: **Manifesto** - **Resources** - **Jobs** - **Events** - **Forum**

We had some mockups from @elioqoshi, where are they? 😉

@AnXh3L0@elioqoshi @tereza @jan are up for working on it! Anyone is welcome to join. 🙂

---

<div class="post-metadata">

**Author:** ![jan](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/jan/32/8_2.png) [@jan](https://discourse.opensourcedesign.net/u/jan)\
**Post date:** [December 5, 2018, 7:13pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-website-review/773/2 "2018-12-05T19:13:24Z")

</div>

One thing we also just talked about in the call was that it needs to be very easy to contribute to the site and run it locally to test it.

- 1 repository (ideally no separation of events and jobs as this always caused problems during the years. People don’t know how to pull it in, and we don’t know where issues are)
- Easy instructions for installing any dependencies, ideally only 1 command
- 1 command to get it running / compile it
- Hint that people can also edit the site using Github’s built-in editor

---

<div class="post-metadata">

**Author:** ![eupiteco](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/eupiteco/32/592_2.png) [@eupiteco](https://discourse.opensourcedesign.net/u/eupiteco)\
**Post date:** [December 29, 2018, 5:49pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-website-review/773/3 "2018-12-29T17:49:05Z")

</div>

Is there a branch going on to make these changes? I’ll be glad to participate. Things I can help to achieve:

- Making a one-script-install, compile and run averything. Electric Books does it with shellscript in a great way, I like their approach.
- Discuss/improve the mockups.
- Help with the programming part once we all agree on the visual mockups.