Kars-T and me are working on creating content during the installation process of a Drupal 7 standard profile. We created a new profile called dsk (a straight copy of standard profile) and are having nodes and blocks created. We'll commit the first version this weekend, as a discussion starter. I'm thinking to create only content that you could create with core, i.e. blocks, menu items for primary links, nodes for article/page/forum content types. Let's collect more ideas in this thread.

Comments

aschiwi’s picture

aschiwi commented

Also, what texts will we use? It would make sense to use common HTML elements like headings, lists, tables but also to use texts that make sense and explain a little about Drupal. We can probably use existing texts from the docs.

aschiwi’s picture

aschiwi commented
Version: » 7.x-1.0-alpha1

Just tagged the first release!

eigentor’s picture

eigentor commented

O.K. tested the release.
I guess this is more a proof of concept (found 1 node with 1 comment and 1 block). What else gets configured in the profile? Things might not be visible, but still there.

I had a WSOD (White Screen of death) in the installation process after the Site configuration page. When I went to the start page, it went away. Still a bug.

The default theme now is Bartik out of the box. We should create the empty theme with some very basic styling that the designer can hack away right away now.

aschiwi’s picture

aschiwi commented

Ugh, I had already fixed that bug. Added a new release in which this is fixed.

I added text to the designer-starter-kit.txt that explains what it does. Adding the node with the comment, image, menu link and the block took a while (Thanks Kars-T!) and that is all we need to get the discussion started. We need to talk about what nodes should be created and what should be in them. I don't think too many other things should be configured, it should be as close as possible to the default installation profile. I'm thinking we should activate forum and add some forum nodes during the installation.

I have to say I wasn't in Prague when you guys discussed this. I was thinking an install profile that creates content designers can style would be a good way to start this thing.

artatac’s picture

artatac commented

sub

drupa11y’s picture

drupa11y commented

I guess especially for beginners it´s good to start with core and only a view essential modules & settings, but withoput any and only core no designer will be happy:

- different users & roles:
*admin
*agency (most important settings)
*chiefeditor
*editor
*clients
*visitor

modules I think are essential:

backup & migrate -> with this module you can easy import different settings & structures without always update the installation-profile or import different settings for users, roles etc.

admin
admin_menu

imce
imce_wysiwyg
wysiwyg

ctools
views
views_bulk_operations

CCK add-ons:
date
email
extlink
field_group -> very essential for creating a good & easy backend
link

functionality add ons:
colorbox
print
simplenews
webform

media add-ons:
plupload
media
media_gallery
rotating_banner

social-community add-ons:
follow
tweet or tweet-button
fb (Facebook for drupal)

As a designer or agency Ihave some minimum needs and I think for this these modules are necessary.

Besides a given content-structure:

* homepage with welcome message & teasers, maybe right sidebar with more teasers/blocks

* products or services page
* gallery-page & image-galleries

* contact - a page with a webform
* about
* legal

drupa11y’s picture

drupa11y commented

A good example is drupalgardens.com, you can export a complete site for local hosting & testing.
unfortunately without the layout-editor ;-(

eigentor’s picture

eigentor commented

@aschiwi: Here's the deal: You create five or six Nodes with a menu entry in the main menu and say four that are in the second level of the menu. One should be the contact form. Not sure if we should use the default core contact form (did this get better in Drupal 7 and is it now fieldable?) or Webform.

I will create text and content. I believe the best way to go now is a brochureware site. Actually we have been recently building tons of them that were pretty similar in structure.

aschiwi’s picture

aschiwi commented

Hi mori, thanks for your feedback! I'm surprised you're thinking to include so many modules. The reason I'm not thinking to include any or not many contrib modules is that it makes this package less maintainable and also you can't include everything that people want. You can always download those modules yourself, we can't deliver a full package for one single purpose. The Starter Kit is meant to get a designer started with Drupal. For me this means that we provide a Drupal that provides some content to get started and that consists of core elements and looks similar to what you get when you install the standard profile.
Concerning the text that gets delivered with the installation profile, yes it could be some fake text about some fake company, but it could also be helpful text about Drupal, theming etc.

drupa11y’s picture

drupa11y commented

@aschiwi: I am a designer and concepted a lot websites including the o2online-Portals from 2004-2006 and I guess I know the minimum requirements designers will have.

if you just want to launch a minimum package there´s no reason to make an extra distribution.
Then it´s better to create tutorials or features which can be installed or provide an "import-file" for backup and migrate.

As a designer I then would choose an export of drupal gardens, cause there´s already a structure, a frontpage and content which can be also exported for a local installation.

In conclusion: if you want to deliver a good "product" it´s really needed to spend some time on it.

Another issue is, what target audience do you have in mind?
Designers as Themers or Designers as clients, which need a site for their own?

Best way to find out what they want/need is to ask them on websites like t3n.de, dasauge.de, smashingmagazine.com etc.

Mostly they use wordpress for their blogs etc., that means your minimum product should be a complete replacement for wordpress and better an improvement concerning the functionalities and features provided.

aschiwi’s picture

aschiwi commented

How about we meet in IRC for an hour to talk about the next steps? Thursday, Feb 10th, 5pm CET in #drupal-design?

drupa11y’s picture

drupa11y commented

Good idea but I can´t on this day or before cause I am invited to an IGNITE TALK in Nürnberg this day and had to prepare my talk and presentation the next days until 10th. On friday 11th or the week after it would be no problem.

drupa11y’s picture

drupa11y commented

Neu: http://drupal.org/project/design

Hab´s aber noch nicht getestet.

aschiwi’s picture

aschiwi commented

@mori: I linked to design and styleguide modules in http://drupal.org/node/968824#comment-4054432, I totally think one of them should be included. I checked out both today, styleguide seems easier to understand, there's one page with all elements. Design module places elements grouped by "page" and "form" and some sub tabs but it's sort of the same approach, it shoes Drupal specific elements that need styling.