wearefairphone/community-portal

A Jekyll-based static site for informing about WeAreFairphone community activities

community-portal's Issues

Fill teasers

Currently most teasers are quite scarce on content. They should ideally explain the subject of a page and make the visitor interested in following the „read more” article linking to the forum.

Can anybody come up with texts? I'm currently not that creative at the moment, but would create the files.
You should be able to do that from within GitHub: https://help.github.com/articles/editing-files-in-your-repository/

If documentation is lacking, just ask and I'll add them.

Uniform layout

I want to use this issue to discuss our approach regarding the layout for the Landing Page.
The solution I started before I knew of this is mostly sticking to the old layout, while using Bootstrap 4 for ease of use.

In my opinion we should sketch out a few guidelines to use in a uniform layout and if possible stay close to the overall style of the Fairphone look and feel.

I'd like to hear your opinons and suggestions on this matter!

Align with duke1102/FairphoneAngel-LandingPage about design

https://github.com/duke1102/FairphoneAngel-LandingPage

Best navigation design

Breadcrumbs?
http://bradfrost.com/blog/web/complex-navigation-patterns-for-responsive-design/

Any other ideas?

Localization

How to deal with different languages?

Get inspiration from mozilla/activate.mozilla.community or learning.mozilla.org

https://github.com/mozilla/activate.mozilla.community
https://learning.mozilla.org/

Explore the Discourse API gem

See forum post

Apply new community logo

Would be handy if we could replace the star favicon with one with those two hands and a star.
If it is not recognisable, provide feedback, so Fairphone can offer an optimised version.

Fix navigation (look into former implementation)

Turn TODO section into GitHub issues

Ideally my brainstorm approach should be turned into proper GitHub issues, so people could take over some parts. Anybody have time to create a ticket for each unchecked item in the TODO section of README?

JSON imports should be in normal type instead of italic type

The forum posts that are displayed below a page should be in normal type. This way they better integrate with the whole page. Besides, italic type is used to emphasize certain information in the forum posts and that information is lost when everything is in italic type.

Github Pages

Need to publish on Github Pages.

According to docs there is a whitelist of plugins which could make this approach hard
https://help.github.com/articles/configuring-jekyll-plugins/#default-plugins

"WeAreFairphone" instead of "We Are Fairphone"

We generally use above's former version ("WeAreFairphone"), see Matrix network, for example.

The Fairphone colour guide

Do multiple language really make sense?

I was wondering whether it isn't a bit of a fraud if we say "hey, you can switch to your own language" and then link to a forum post that is entirely in English. 😁

Look into WeAreFairphone/Community_identity for design

https://github.com/WeAreFairphone/Community_identity

Pull data for community events from the page

From this page:
https://www.fairphone.com/en/community/events/?event-category=community-event

Forum posts or GH files as "content feeders"?

Should we, in general, use forum posts as the base for the portal's sub-pages, or rather write up the pages in md-files here on Github?

From my point of view, what speaks pro forum posts:

• Easily editable if we make them Wikis
• No new account for forum members

Pro md-files on Github:

• Easier to implement
• More emphasis on formatting (Wiki posts on the forum are often "untidy")

Document how to find and install Jekyll plugins

Preferred approach is looking https://rubygems.org/ for gems (= ruby packages) and add them to the Gemfile, then run bundler.

Alternatively a *.rb file can be placed in the plugin directory.

The documentation should go into the README.md

Think about recommending rvm in installation instructions

Need to recommend rvm in the installation instructions.

The installation instructions on their website are pretty straightforward, it shouldn't be too difficult.