This looks pretty sad when you first get to the front page. :)

Commons page just asks 'What's going on?' without an answer. Sniff.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

geresy’s picture

FileSize
82.47 KB

this is how the front page looks, after i created some content and enabled some modules
would be nice to come with some menus and content, would make the debugging way easier.

Topcheese’s picture

How about something like a default notice with useful start info?

lisarex’s picture

We could use the same (or similar content) that was used in the prototype. I chose food because it's pretty universal (the drawback is you will feel hungry while working on Commons).

Alternatively we embrace the dummy content idea and tile things "I am a Wiki" but I think having a theme ties it all together for those working with Commons for the first time since default content will be users, nodes, topics etc.

Topcheese, I think your idea fits into the Onboarding task http://drupal.org/node/1578164

ezra-g’s picture

I sugget we stick with the interactive prototype content and keep a snack handy. In part, this helps compare the prototype to the final theme.

Topcheese’s picture

Lisa, thank you for the information. I looked at the Onboarding info, but haven't yet read all of the comments, so I'm probably not up to speed on this. The interactive demo I believe shows the anonymous view, and this issue shows the authenticated view. I was thinking of something along the lines of onboarding, but for the admin with something like Commons Dismissible Notices. Presumably the admin will be the "first" to access and setup the CMS to enable/disable defaults. Nothing fancy.

I'm already hungry and Drupal is a smorgasbord in which Commons is the dessert. I'm about to grub on it, so perhaps snacks should be added to the Commons optional list of items needed.

ezra-g’s picture

Seems like the action item here is to test exporting content and users from the interactive prototype with http://drupal.org/project/uuid_features.

ezra-g’s picture

Another option would be to use Migrate module.

lisarex’s picture

The interactive prototype screens are in Fireworks, so someone needs to first populate that content into a Commons database. This might be me.

juan_g’s picture

There is also one of the components of Moshe Weitzman's Devel:

Generate content
Accelerate development of your site or module by quickly generating nodes, comments, terms, users, and more.

lightsurge’s picture

@lisarex If you were to open up a demo platform to a limited few on drupal.org we could help by creating our own users and posting a few [decent imaginary, not lorem ipsummy] posts/comments. That would save you some tedium and some time and it might look a bit more varied and community-like?

ezra-g’s picture

Another path to working on this is good old fashioned user_save() and node_save() in the commons profile as an optional install step :).

lisarex created a starter spreadsheet of content and users to help with this effort:

https://docs.google.com/a/acquia.com/spreadsheet/ccc?key=0ArdfU8Fa1ufodF...

ezra-g’s picture

@lightsurge - Sorry I missed your post above. Thanks for volunteering!

I think lisarex's spreadsheet is helpful since it contains content from the interactive prototype. Certainly adding to that content would be helpful. My sense is that the biggest blocker to working on this issue has been the technical hurdles around exporting the default content, so I hope that a simpler approach (eg node_save()) will help make this task more accessible :).

gnuget’s picture

Assigned: Unassigned » gnuget

Oks,

i will use the approach of use user_save(), node_save()

i'm going to work on this, this weekend, so, i'm going to assign it to me.

lightsurge’s picture

That actually sounds more difficult to me than featurizing the content?

Example feature-exported content:
http://drupalcode.org/project/panopoly_demo.git/blob/refs/heads/7.x-1.x:...

lightsurge’s picture

ezra-g’s picture

@lightsurge, I believe default_content has some key limitations around handling author-specific content, users, and taxonomy terms which is why I suggested uuid_features (which had these abilities in D6), but since they're not in place for D7, a manual export seems like the fastest path here.

gnuget’s picture

Status: Active » Needs work
FileSize
7.25 KB

Oks.

I attached my initial work on this issue.

Some details about the patch:

- I added a Post, Wiki, Event and Group demo content.
- There is not a poll, idea, call for ideas, question and answer content types right now, so i didn't added that demo content.
- I tried to test my patch with a fresh version but seems to the build-commons.make file is broken, there is a patch who fails.:

>> Project og contains 7 modules: og_ui, og_register, og_field_access, og_example, og_context, og_access, og. og-7.x-2.x-dev downloaded.        [ok]                                                                                                   
Unable to patch og with fix-role-creation-on-feature-import-1800964-1.patch.                                                                                                      [error]
 >> Project oauthconnector contains 2 modules: oauth2_common, oauthconnector. oauthconnector-7.x-1.x-dev downloaded.                               [ok] 
 >> Project oauth contains 2 modules: oauth_common, oauth_common_providerui. oauth-7.x-3.x-dev downloaded.                                               [ok]

Well i set this issue as "needs work" because is still incomplete, i'll continue working on this.

Any thoughts about the patch, is really appreciated.

ezra-g’s picture

Thanks, gnuget! This is super helpful!

I've started testing and making some tweaks and will post a re-roll later today.

ezra-g’s picture

Status: Needs work » Fixed

I made some tweaks and committed. Thanks, gnuget!

The changes included:

- More specific variable names for the groups
- Adding group integration for the sample event
- Changing the dates on some of the sample content
- Tweaking the text in the install form.

I filed #1838702: Improve Default content shipped with Commons as a followup.

This has already been helpful in discovering other bugs - Thanks!

http://drupalcode.org/project/commons.git/commit/f183c03

Status: Fixed » Closed (fixed)

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

Anonymous’s picture

Issue summary: View changes

Updated issue summary.