Csdn content system architecture status quo analysis-services and sub-sites

I opened this topic "csdn Diary" early on, and want to share with you my work on csdn. From my perspective, I will help you interpret csdn. However, there are no reasons for this. Recently, Zheng Qiao talked with Han Lei about the future website content architecture of csdn. The current csdn channel (. net, Java ,......) in the future, how will the csdn Service (BBS, blog, Dev center...) be presented ...) how it will be organized. How to better provide services to csdn users, and how to make our commercial customers better promote their own technical products through csdn. All these seemingly abstract problems are actually very important. I am also scheduled to write a "csdn website content organization architecture development executable SOLUTION". Therefore, I would like to take this opportunity to start the "CSD Diary" topic. We will focus on the current content architecture of csdn in the near future, hoping to help you make better use of the csdn platform.

I made a diagram of the content organization structure of the current csdn website. We can see that the content architecture of csdn is separated into two relatively independent parts, namely, services and sub-sites.

Service (blue ring ),It mainly includes BBS (community), blog, wiki, chat, devcenter, and ypage. Users can participate in these services, create content and obtain the content they need, forming a good self-circulation system. From Alexa, we can see that the main traffic of csdn comes from this.

The content organization of this service model is very suitable for the development of csdn. According to the current plan, csdn will launch more service projects in the near future: Tag Page Content Aggregation service and technical dictionary service. Both services have been developed, in the internal test phase, the specific public test time has not yet been finalized. but it should be within this month.

Child station (outermost circle ),It mainly includes: news site ,.. Net Site, Java site, PM site, and SD site. according to the original plan, csdn will build a website group, with its sub-websites separated from csdn and an independent content system. Of course, csdn services can also be called. this development path is similar to that of traditional foreign media groups, such as CMP and CNET, and emphasizes vertical sub-brands. However, the current csdn sub-stations are much faster, and the content source "services" of each sub-station and csdn are in a relatively independent or mechanical combination. Sub-websites do not have the ability to create content independently, so they have never been recognized by everyone.

Recently, I have been wondering if the csdn sub-station policy will continue to develop? If we develop, how can we integrate sub-sites and services? If we do not develop sub-station strategies, what will happen to csdn's future content organization architecture?