I am trying to determine if I want to use this distribution but after reading information on github, the government's site and on Drupal, I am still not clear about a few things. I downloaded the file and went through the list of modules and it looks like you have regular Drupal core modules plus a few more. So it appears that the distribution requires a whole lot more modules such as all those listed under Sylus' profile. That seems to be the most complete list of WET modules.....

My use case involves updating a Drupal 6 site to a Drupal 7 site and I am looking for the kind of functionality you have because it seems to be a good direction if you want to do work with governments in Canada.

My questions are:

1. Do I install the distribution instead of core and those modules listed in the core areas (required and optional) and add modules from the WET group as required? I always thought distributions were a complete package....

2. Is it accurate that you're moving away from Omega and towards Bootstrap in future versions?

3. Is there anyone on the team available for paid work on WET on a non-government site? Initially, I would pay for calls to get answers to questions to better understand if this is the right way to go.

4. Bootstrap worries me in that it's mobile first. Not appropriate for my use case. I need to know that it will work equally well for other devices.

Thanks!
Hélène

Comments

joseph.olstad’s picture

joseph.olstad
Primary language French
CreditAttribution: joseph.olstad commented

Hi Hélène,
Answer to question 1)
The distribution comes with the latest Drupal 7 core, there are also many contrib modules and custom modules included with the distribution, these are located under the profiles/wetkit/modules folder, the wetkit project does it's best to ensure that these contrib modules and custom modules play nice together and work with the wetboew themes and achieve the goals of the wetkit distribution (i18n compatibility, wetboew theme, out of the box functionality, etc) You can add modules but there is a recommended way and a non-recommended way. The recommended way to add your own modules or other contrib modules is to put them in the sites/all/modules folder this way it's easier to upgrade to future wetkit versions keeping prepackaged bundled stuff seperate from your stuff. With that being said, the wetkit distribution includes most of the modules that you'll ever need. There's only one wetkit download you really need, it's the release on the http://drupal.org/project/wetkit as this includes every other wetkit module for that version. If you have a problem with anything specific to wetkit post an issue in the issue queue that I am replying to.

answer to question 2)
Yes we're moving to bootstrap, so if you're starting fresh you can skip wetkit 1.x altogether and go straight to 4.x with that said aside from theme, there's a lot of similarities between the two but if starting fresh best to go straight to wetkit 4.x

answer to question 3)
I'll let someone else answer this

answer to question 4)
bootstrap works fine for other devices like computers. Using it on a desktop computer works as you'd expect. I cannot comment on your use case as I don't know anything about it.

sylus’s picture

sylus CreditAttribution: sylus commented
Status: Active » Fixed

Yeah pretty much just echoing what was said above.

As for point #3 we can most certainly answer questions tagged with support in our issue queue.

As for paid support that is not something we can offer as it outside of our purview. Nor can we recommend anyone as might show bias / host of other reasons.

In the near future we are looking at having office hours once a week to answer any questions which might help your use case.

I personally am actively looking at gitter for this type of collaboration.

Otherwise exactly what Joseph said above holds true ^_^

HJulien’s picture

HJulien CreditAttribution: HJulien commented

Thank you very much for the information. I will go through the list of modules in detail. One thing I noticed is that there aren't any login-specific modules such as login-toboggan or login destination. How is the login process handled from the WET perspective?

joseph.olstad’s picture

joseph.olstad
Primary language French
CreditAttribution: joseph.olstad commented

Hi HJulien, usually we install login_toboggan seperately, as well as honeypot for login perspective.

joseph.olstad’s picture

joseph.olstad
Primary language French
CreditAttribution: joseph.olstad commented

depends on the site, our intranet sites don't need login_toboggan for example.

wetkit is for both intranet and internet.

joseph.olstad’s picture

joseph.olstad
Primary language French
CreditAttribution: joseph.olstad commented

we're releasing 1.9 shortly and 4.0 , you'll want to try the new build , you can try the dev build out, it's very close to release.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

HJulien’s picture

HJulien CreditAttribution: HJulien commented

My upgrade from 6 to 7 has been very painful and time consuming :) and I'm just now getting back to this.

I'm still not sure WET is the way to go. There is a lot of overlap between my existing modules and the distribution and it seems that the latter has modules I will not require so I was thinking of just taking the modules I need. For example, I don't think I need the deployment modules. Is it potentially a problem to just take what I think I need?

My biggest concern right now is the theme. I see several of them are included but there aren't any images to see what they look like. I need to understand what makes them more accessible and better for government sites than other themes. Also, can I use a different sub-theme? Are there WET-specific dependencies between modules and themes?

Is there a chart somewhere that breaks down WET design/style features? Maybe the problem is that I don't know what the standards are WET is required to meet and how they're met - i.e. how much is attributed to modules and how much is the theme.

Looking at the different sites using WET according to the list here, I notice that many of the sites have minimal styling. The City of Ottawa site is the most styled but it's not clear that they all started with the same theme....

I need to find a way to customize any theme I end up choosing and I need to understand how easy it is to work with the ones included. It seems pretty hard to choose WET without knowing these details.

Thanks!
Hélène

sylus’s picture

sylus CreditAttribution: sylus commented

Hi there!

Honestly this distribution is meant for enterprise environments with medium to large organizations that have a lot of developers. We do support all of the themes from wet-boew.github.io and you can of course subtheme each of our themes.

However if you already have a site that you upgraded with your own customizations my strong recommendation might just be to go with the bootstrap base theme and customize off of that theme alone adding that to your existing site. It would be much more hassle then it is worth to pick and choose modules from this distribution and try to piece them together. This distribution is more meant as a starting point to begin with not as something to pick and choose from especially if you already have your own suite of modules. As a prime example if you use this distribution you are forced down the Panels + CTools pipeline with no exception.

Our 4.x version strongly uses the Bootstrap base theme with our own customizations in wetkit_bootstrap. Aside from that we simply just add the jQuery Framework that WxT provides which extends the base bootstrap foundation. Based on what I read above, I would first start trying to get your Drupal site working with the Bootstrap itself and once that is done then consider integrating with WET-BOEW.

The Bootstrap Base theme can be found here: http://drupal.org/project/bootstrap.

Documentation for the jQuery Framework for WET-BOEW can be found here : http://wet-boew.github.io