GWT dev team members blogs and way-of-work (WOW) advice ?

[Ed]

I like to propose the following idea:

A central place with:

1) Blogging by the GWT dev team members/contributors 

2) Background info of the GWT dev team members/contributors (what they do, where they work etc...)

These blogs contains GWT issues and how the blogger advice to use it, and how he uses it.

I think this info is very valuable as the GWT dev team member/contributors have many interesting info that should be shared.

It will creates a better understanding of current activities.

Besides the current GWT doc, I think their is a need for more in depth info on "How" to implement/use GWT.

Hopefully this safes duplicate forum posts

++ An example to realize the above is het hibernate blogging site: http://relation.to/Bloggers

 

Should I put this in the issue tracker?

Please feedback?

[Thomas Broyer]

Having a place to post doesn't mean you'll spend time to write those posts ;-)

A good place to share information (including links to blog posts) is the G+ community (there's an "How it works" section for these kind of posts).

[Ed]

Having a place to post doesn't mean you'll spend time to write those posts ;-)

As long as enough people read it, it's worth posting...

 

A good place to share information (including links to blog posts) is the G+ community (there's an "How it works" section for these kind of posts).

Could be, but the G+ GWT community is a-kind-of twitter feed, not  blog (links), 

Maybe it get's messy when mixing this and followers get confused a such they stop following.. 

[Thomas Broyer]

On Tuesday, June 4, 2013 12:20:11 AM UTC+2, Ed wrote:

Having a place to post doesn't mean you'll spend time to write those posts ;-)

As long as enough people read it, it's worth posting...

The question is not whether it's worth posting, but whether to write it in the first place (find the time, find the inspiration, etc.)

 

A good place to share information (including links to blog posts) is the G+ community (there's an "How it works" section for these kind of posts).

Could be, but the G+ GWT community is a-kind-of twitter feed, not  blog (links), 

Maybe it get's messy when mixing this and followers get confused a such they stop following.. 

With a bit of moderation, I think it can be "good enough": https://plus.google.com/communities/116543000751323604177/stream/f69153b3-9211-4a16-bba8-95c75994783c 

[Jens]

The official GWT documentation can be updated (its open sourced now) to add some more in depth information. This would already decrease the need of external how-to posts. 

IMHO having lots of blog posts for a given library somehow indicates that the library API is either too complex or documentation isn't good enough...well...or both.

-- J.

[Ed]

IMHO having lots of blog posts for a given library somehow indicates that the library API is either too complex or documentation isn't good enough...well...or both.

Not IMHO, for 2 reaons:

1) As a marketing tool. Blog posts and HowTo's are used a lot by TrendSetters and other interesting Software development websites. Blog posts shows activity, movement and exposure...

2) There many different kind of developers and there are developers that find easy things "very" difficult (I am often surprised by the forum questions). If you want these developers to use your product, and to motivate them you have to have all kind of HowTo's, blog posts (have a look at commercial products where they are more commercial driven and have this by default).

(you can make the most amazing product, but if nobody know about it, nor how to use it, it will never be a success)

[Joseph Lust]

Ed,

Just curious if there is a framework that you consider an exemplar in this respect? I've never seen that Hibernate blog in three years of doing Hibernate, and its CSS nearly made me cry. So curious what framework has a popular nexus of that sort that everyone rallies around.

I'm a huge proponent of building more popular support of GWT, but I think the primary bulwark is that it is a complex framework not amicable to trivial script kiddie demos. Probably the best thing we can do is build a kickass GWT showcase site and just let people say "how'd you do that" and let them get piqued so they can dig deeper and learn how it's done.

FWIW, every employer I've ever worked at blogs FB/G+/TW, so those community sites are not that usable by many enterprise devs.

Sincerely,

Joseph

[Ed Bras]

> just curious if there is a framework that you consider an exemplar in this respect?

No, I haven't got the silver bullet around here ;)...

> I'm a huge proponent of building more popular support of GWT

Totally agree... And yes, a kickass app would be great, but let's not forget the commercial side of the GWT framework like mentioned above, that is: making a product/framework that is awesome, is nice, but making sure people use it, is another thing... This is the risk of many technical driven products/framework... Many products/frameworks died slowly because of this...

Especially now that Google put GWT on it's "feet", how is this commercial aspect filled in?

I think you have to target two type of persons:

1) The dev people: Kickass app would be a good start... but still, dev people don't want to read these days and see something on their display within seconds, so there must be "something" to do this. Maybe let the kickass app contains severy modules that one can start with that has an associated HOWTO/blog/doc....

2) The decision makers. These are often the people that "hear" something about a product/framework and push it to the dev people on the floor (even if they don't like it, they must play/use it)... Let's not forget to get in "touch" with these people as they are very important IMHO.

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/wrgfnRDEAr8/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.