The Design Initiative’s main goal is to develop a beautiful new theme for Drupal 8. The first phase of the initiative involves selecting the design. Designs will be sourced from the community via public submission and will be subject to peer review and the selection process. The initiatives main page is here: http://drupal.org/node/1089096

For our initiative to be successful we need to attract high quality designers and provide the best environment to support public submissions, design reviews and the selection process.

We have assessed both d.o and g.d.o and come to the conclusion that neither of these sites provides the right set of tools for our specific requirements. We need to remove the roadblocks for designers and portray an unwavering impression that we are fully supportive of their craft and sensitive to their requirements.

Additionally we do not want to drag this completely off-site to another domain which would result in siloing a small community and be harder to promote as a serious core initiative.

After careful assessment of the most popular design collaboration/review websites we concluded the only way to achieve this is to develop our own purpose built site. This site will be far more simple than the d.o issue queue or g.d.o and is 100% focused on iterative design development.

To meet the requirements of the Design initiative we propose the following (breaking it down to the most basic requirements):

  1. Establish our own site for the Design Phase of the initiative (25th June - 30th Sep).
  2. Host this site as a sub-domain of drupal.org (probably design.drupal.org).
  3. Use Bakery for single sign on.

We have prepared a technical brief for the site which includes a module list, which I have attached to this issue.

I will be heavily involved with day to day operations of the site and will take on the role of a site maintainer (I can commit several hours per day if required), and we are currently discussing administrative/site maintenance roles with several interested parties (TBC) to handle the module updates and other site maintenance.

Actual site building will be done by the Design Initiative team members who are all experienced Drupal professionals.

We need to have the site up and running by mid June and live on the 25th June, when we will officially launch the Design Phase of the initiative at Drupal Design Camp, Berlin. We've been prototyping behind the scenes so we could have this up pretty quickly, pending Infrastructure review and setting up the domain etc.

I am not sure how this process should work with infrastructure (actually setting up a sub-domain, bakery module, access etc) so we're definitely looking for some advice and guidance here.

CommentFileSizeAuthor
Design-Initiative-Technical-Brief.pdf65.08 KBJeff Burnz
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented
Issue tags: +Design Initiative

Tagging.

Bojhan’s picture

Bojhan CreditAttribution: Bojhan commented
Category: support » feature
Priority: Normal » Major

This is pretty major - especially considering the timeline on this one, can we get feedback?

Jacine’s picture

Jacine
she/her
Location New York
CreditAttribution: Jacine commented

subscribing.

Gerhard Killesreiter’s picture

Gerhard Killesreiter CreditAttribution: Gerhard Killesreiter commented

We've agreed that this can be set up as proposed as soon as there's a second technically able admin.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
CreditAttribution: webchick commented

Subscribing as well. Thanks a lot, Gerhard!

JurriaanRoelofs’s picture

JurriaanRoelofs CreditAttribution: JurriaanRoelofs commented

Hi.

I hereby volunteer as second sysadmin.

I have 5+ years experience in building/maintaining Drupal websites and LAMP servers and extensive experience in website performance analysis and improvement.

I will reserve plenty of time on this project, can basically work on it on a daily basis.

Some references of my work:
http://www.sooperthemes.com
http://www.sooperthemes.com/blog/joomla-15-drupal-61-performance-compari...
Currently building enterprise level websites with employer www.oneshoe.nl

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented

Jurriaan has been working on the Design Initiative for the past couple of months and we've been discussing him coming on board as the 2nd site maintainer, which I am very happy with.

Gerhard Killesreiter’s picture

Gerhard Killesreiter CreditAttribution: Gerhard Killesreiter commented
Status: Active » Reviewed & tested by the community

needs to be set up

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
CreditAttribution: webchick commented
Assigned: Unassigned » nnewton

Thanks, Gerhard! :D

Assigning to nnewton, per his request once this was approved.

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented

Oh my, thank-you so much, this is fantastic news. Looking forward to getting stuck in :)

mortendk’s picture

mortendk CreditAttribution: mortendk commented

ooh yeah baby tagging just because im \o/

JurriaanRoelofs’s picture

JurriaanRoelofs CreditAttribution: JurriaanRoelofs commented

Thanks for backing our project, I'm looking forward to create an awesome tool for Design&Drupal.

drupaltronic’s picture

drupaltronic CreditAttribution: drupaltronic commented

subscribing

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
CreditAttribution: webchick commented

Ping. :(

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented

What I can think of right now:
- LDAP accounts for the admins
- BZR branch of either pressflow-unbranded or plain drupal, and commit access to it
- A staging webroot & DB with that BZR checkout.
- A Jenkins job to bzr up staging every 5 minutes or so. (Triggering on BZR commits doesn't work well on non-util servers.)

What site builders need to know:
- http://drupal.org/node/844068, especially http://drupal.org/node/1029362
- What Drupal.org profile fields you want copied from Drupal.org. Don't add more on this site, the idea is you have one profile across *.drupal.org.
- http://groups.drupal.org/node/145354, featuring a white-on-transparent PNG with the wordmark and your site name.

When this launches:
- Staging's files and DB are put on the live copy. Fully expect staging to be replaced with copies of live at any time.
- Set up DB sanitization and dev sites. Be thinking about where personal or private information is stored in the database.

There is a lot of stuff to cover and new sites don't happen too often, so some things will be missed. The best thing to do is catch one of us in #drupal-infrastructure and work through the immediate blockers.

nnewton’s picture

nnewton CreditAttribution: nnewton commented

Hi All,

Would the site admins please post here marking themselves as admins and make sure their ssh key is attached to their account. Also if they would like a different name than their irc nick, please specify.

-N

nnewton’s picture

nnewton CreditAttribution: nnewton commented

Also can I get:

* It confirmed that the name will be design.drupal.org
* Info on any current site code in existence

Thanks

-N

Bojhan’s picture

Bojhan CreditAttribution: Bojhan commented

It will be design.drupal.org - that is correct.

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented

I am one of the site admins, my current VCS user name is fine and my public key is attached to my account.

We don't have any code to date - in the brief attached to this issue is a module list and basic outline of the site, this will probably change only in configuration, we probably don't need any more modules than are listed in the document: http://drupal.org/files/issues/Design-Initiative-Technical-Brief.pdf

Regarding Bluecheese, I have a copy but am not sure if its the most up to date version - we will likely need to add to it - whats the best practice here - modify it directly or should we subtheme it?

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented

Modify the theme directly. Overall, the goal is lowering long-term maintenance, and having subthemes would be more to maintain.

nnewton - be sure to include read access to vendors and read/write to bluecheese.

JurriaanRoelofs’s picture

JurriaanRoelofs CreditAttribution: JurriaanRoelofs commented

I'm the other site admin
-I just added a public key to my account, will this be the only key that I can use on d.o.?
-I would prefer my nick to be JurriaanRoelofs

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented

With regards to profile fields we want to keep it basic and only include a subset of the d.o "Personal information" fields:

Full name
My website
Country
LinkedIn profile
Facebook page
Twitter url
Bio

We would like to have User Pictures as well, if there are any issues with this please advise.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
CreditAttribution: greggles commented

If you are using a subset of d.o profile fields then you can synch them using bakery. Then people are not able to enter them on the design.d.o site, but instead enter them on d.o and it gets populated down. Ask me or someone familiar with bakery for tips as you set those up.

Drumm's vision is that there's only one user profile page, but the mechanics of making that happen are not super simple.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented

I would like to migrate user picture storage to Drupal.org at some point, but that's a separate issue. And actually using them on Drupal.org is yet another issue (documentation wouldn't want them, space is tight on issues, etc). Otherwise, that's all doable as we set up bakery. User pictures happen whenever we get those working across all the sites.

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented

I've started prototyping the site and have some questions:

1. We'll have some pages that are basically static content, should we build a module and hard code the content into tpl files - I see association.d.o has some pages like this, which I assume is done for performance.

2. Do we patch the main drupalorg_crosssite.module for our sites main navigation, or just add it to the version running on our site.

3. Should we sandbox the site for review, I have one set up but no code there as yet.

4. Can we use Pathauto?

whitefluffy’s picture

whitefluffy CreditAttribution: whitefluffy commented

Subscribing.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented

1. .tpl.php files are mostly for dynamic content mixed in. When layout makes a lot of grid divs and such, it can be nicer to edit. Most of the time, it ges cumbersome, so use a page content type for plain pages.

2. Patch drupalorg_crosssite, using drupalorg's issue queue. As much as possible, we want everything in consolidated places for management.

3. There will certainly be some time the site is in staging-only to get everything right.

4. Yes, pathauto is great.

JurriaanRoelofs’s picture

JurriaanRoelofs CreditAttribution: JurriaanRoelofs commented

Now that there are 2 site admins can we get a development environment on Drupal.org so that we can learn to work with bakery and if possible start development, or is this not the desired order of things?

nnewton’s picture

nnewton CreditAttribution: nnewton commented

LDAP Account Requests sent for jmburnz and JurriaanRoelofs
DNS name registered

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
CreditAttribution: webchick commented

Melissa was on our bi-weekly call and noted that once these requests are sent into OSL, there's not a lot we can do on the d.o side to usher things along. So we're in wait mode now.

nnewton’s picture

nnewton CreditAttribution: nnewton commented

I've re-pinged those tickets as they have not been serviced yet and might have been lost.

-N

nnewton’s picture

nnewton CreditAttribution: nnewton commented

These LDAP accounts have now been fulfilled. If they could try logging into util.drupal.org to confirm.

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented

I can login to util.drupal.org.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented
Status: Reviewed & tested by the community » Closed (won't fix)

Talking with Jeff about this at DrupalCon London, we decided to do this as features on Drupal.org itself, #1262116: Review drupal.org development site for the Design Initiative