|
|
What's New On Dev2Dev
We've changed quite a few things here on Dev2Dev! In fact, this page is part of the new wiki that has just been launched. Here is a brief introduction to some of the new features that you'll see popping up on Dev2Dev over the next month as a result of the BEA / O'Reilly partnership.
Articles
The article display now includes links to a whole set of tools designed to allow you to join in the discussion. The following tools are now available on each article display page:
You can now easily mail the article URL, display a print-friendly version of the article, and join in the discussion. The blog link, pictured above, is pretty useful. It provides you with an easy-to-use link and blurb display of the article, which you can use to paste into any blog you may be writing. It also provides the all-important TrackBack URL that you can use.
The article discussion feature is something we've wanted for a long time, and our article listings now show relevant comment information too:
Register on dev2dev to join in the discussion.
Once you've read an article you particularly like, you can easily find more from the same source. Click on the author's name and you will be taken to the author's page that includes a biography as well as links to all of the articles and blogs they've written for dev2dev.
You can also easily find articles by the date they were published, by the role or skill level targeted by the article, or by the product or technology they feature:
Blogs
dev2dev now hosts blogs. If you are a member of dev2dev, and would like to have a blog account, please contact the editor about getting an account.
Keep your eye on the Editor's Blog for news from across the dev2dev site, and look at the blog page for a listing of all recent blogs from around dev2dev.
Every blogger has his own home page which lists his blog entries, and the RSS subscription address. We also have a host of other RSS feeds, listed on our RSS Feed Page.
Wiki
We have a wiki of course, and this page is simply a page that I created in the wiki. The wiki is divided into sections, called Webs. I'm going to reserve this, the Dev2Dev, for information, issues, updates and discussions about the dev2dev web site itself. Here is a snapshot of our current wiki front page:
This will change of course, as we (or you!) add content.
If you would like to contribute to the wiki, please check out the WelcomeGuest page. To get you feet wet, you can go and play in Sandbox, where your experiments won't interfere with the main text of the wiki site.
CodeShare
CodeShare, a collaborative project workspace for developers, replace the old Code Library. This revamped environment integrates tools for knowledge management, communication, code repositories (with SVN) and project administration to create a bidirectional collaborative workspace so that participants can share source code and best practices.
Read an article on some of the features of CodeShare, or go take a look yourself!
Reorganized Dev Centers
The Dev Centers have been reorganized a little, and you can expect to see some further reorganization in the future. For example, you'll now see a new XML Dev Center dedicated to all things XML, including StAX and XMLBeans; and Vertical Markets to discuss a number of areas such as telecommunications, goverment, finance, manufacturing and RFID. Dev Toolbox is for miscellaneous items, and the new Platform Admin role is for all you system administrators out there.
In addition to the reorganization, you can now listen-in on a particular Dev Center by subscribing to dedicated RSS feeds. For example, consider the WebLogic Server Dev Center. After the listing of articles, you'll see something like this:
Likewise, after the listing of blog entries you'll see something like this:
Using these feeds, you can subscribe to articles or blogs about WebLogic Server. We always ensure that articles are correctly tagged with the appropriate Dev Center categories (more than one, sometimes). If you maintain a blog on dev2dev, you'll notice that you can assign multiple categories on each blog entry too. Doing this will ensure that your blog entries will get routed to the correct Dev Center, and anyone subscribed to that Dev Center will be notified. Timely, on-topic information, streamed right to your desktop!
|
|