#248: New Fedora.next website
-------------------------+------------------------
Reporter: shaiton | Owner: webmaster
Type: defect | Status: new
Priority: blocker | Milestone: Fedora 21
Component: General | Resolution:
Keywords: fedora.next | Blocked By:
Blocking: |
-------------------------+------------------------
Comment (by duffy):
Ryan has been thinking about how we might approach Fedora.next with the
websites and me and him had a whiteboard session late last week to
brainstorm some ideas. We shared our ideas with mattdm yesterday and he
seemed to think the approach was a good one, so I drew up this diagram
last night to illustrate some of our whiteboard ideas:
[[Image(fedora-next-web_proposal-draft1.png)]]
Some random thoughts to clarify the proposal:
- We were initially thinking remaking www.fedoraproject.org into the
contributor hub. Then we worried about how we would redirect old links
from docs, articles, etc. Matthew pointed out how mozilla.org slowly over
time transitioned firefox stuff to getfirefox.com. We could do something
like that and have the www.fedoraproject.org full domain point to the
community hub, which i think would be more desirable.
- When you first visit the community hub, we were thinking you wouldn't
get any content unless you were logged in... kind of how twitter or
facebook behave when you're logged out. This would free up a lot of space
to help the fedoraproject.org transition from being the general site to a
commnunity hub / contributor-focused site.
- what would happen to join.fpo? We'd integrate some of the FAS
functionality into the contributor hub, so we'd have a new user onboarding
workflow there that would set them up with a new fas account and walk them
through applying to groups, etc. we'd like to handle password resets and
group join requests with this too and leave fas more for group maintainers
to use to manage their groups maybe.
- Re: the visual design in this proposal - none of this is anywhere near
what we'd want things to look like. The little mockups are more to give
you a sense of the general tone of the sites based on the inspiration
sites we listed. We're looking at reddit as a model of how to organize the
difference spaces in the hub - but unlike the reddit model, we were
thinking each of the hubs could have a different custom feel - e.g., the
design hub would be more graphics-focused, the developer hub might be more
data-focused, ambassadors may have a map and calendar, etc. So this
diagram is meant to illustrate that more than propose any sort of look and
feel.
- We're hoping with the new architecture bits we have in fedora infra now
like fedmsg we can keep these hub sites dynamic and engaging by pulling
data down from the bus.
- We're also hoping to integrate these hubs with hyperkitty to make
discussions on mailing lists more accessible.
- Matthew mentioned one of our current issues in collaboration across
groups - having to cross post messages to multiple mailing lists /
multiple team locations. We thought we could maybe have a model in the
community hub where you could break out a new hub space (the same way you
can break out a new subreddit on reddit) that are project-focused to help
allay that issue. Just a thought.
Okay, hope this makes sense. What do you think?
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/248#comment:7>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
--
websites mailing list
websites@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/websites
