This article is the 10th (end) of the Quick Create website series, and if you have not read the previous content, it is recommended that you click on the chapters in the following directory to read the other content before returning to this article. To access this catalogue, please click on: http://anb.io/blog/tag/wordpress-on-azure/
1. Website management platform WordPress and cloud computing Platform Azure Introduction (6-minute video)
2.1 Creating websites and Web site operations on Azure (13-minute video)
2.2 Domain binding operations and Azure load Balancing mechanism (12-minute video)
2.3 WordPress initialization and website management features (11-minute video)
3.1 WordPress Data import (12-minute video)
3.2 WordPress Multi-site support and Azure online Code Editor (14-minute video)
3.3 WordPress Multi-language support multisite Language switcher (15-minute video)
3.4 WordPress Theme Installation and configuration to beautify your website (15-minute video)
4.1 Why software is different from making a car, why software is bound to have bugs-building DevOps (11-minute video)
4.2 Finish – Application operations vs. launch satellites, telemetry (Telemetry) technology (13-minute video)
In the previous section (4.1), I showed you what it means to develop operational integration (DEVOPS). But I don't want you to be fooled by the words that sound tall, and feel like it's just the size of the website and the team. Any software products, websites need to connect the development team and users, we can not behind closed doors, we can not let the long channel into the user and development between the shield, any developers need to directly face the user, any software products need the most direct delivery to the user. This is the most efficient software development, is the most effective lean entrepreneurial model. In this section, I'll focus on the feedback link, and the more precise name should be called telemetry (telemetry).
Please read this article in conjunction with the video
Releasing an application is launching a satellite.
Again a tall vocabulary, Telemetry (telemetry). It feels like we're launching a satellite. In fact, when you publish your product, especially an Internet product, whether it's a website, an app, or an app, or even just a blog post, you've launched a satellite that's wandering around the vast internet, you don't know where it is now, how many people are watching it, I do not know where it is going to fly, or whether it has crashed into a deserted desert, and, fortunately, other space junk may be a target (Dos attack?). ）。
Telemetry Technology (Telemetry) is not a new technology in many industries, such as aerospace, wildlife protection, medical, and even law enforcement processes that are indispensable and long-lasting. We don't have to think of it as a sophisticated technique, and you can imagine the way you drive or ride a bike, your eyes get around you, your brain handles the best driving plan, and then you guide your hands and feet to react so that you can travel safely and reach your destination. This is the telemetry technology.
Telemetry and logging (Telemetry vs. Logging), you might think: OK, no problem, there's a lot of logging in my app. This is very good, stating that you have started your telemetry practice. But the logs are generally better. focus on the technical aspects of our developers tracking application performance, lower levels, more data about the application itself, rather than the user's perspective on how to use your app. The need for telemetry is more about how users use your app and how your app responds.
In other words, logs can help you prove known (confirming that the app is running according to the design), and telemetry can help you explore the unknown (find the user's real needs and refine your design).
Telemetry can help you answer 10 questions
The user's "real" demand is a jinshan, and we need to do is how to find this Jinshan. Telemetry is a metal detector in your hand that can help you answer these questions:
1. What are those features that are popular with users? I think the useful function, whether the user really feel useful?
2. Where did the users spend their time? How much time did they spend on each app page, and where they went, and what did they do in those times?
3. What devices does the user use to access my app? Model, screen size, resolution, using a keyboard or touch device?
4. My app offers so many options, does the user really use it? How do they prefer to use my app?
5. How does the user react when there is a problem with the application? How often do they encounter problems, and what are the problems they encounter?
6. Do I publish new features that users like? Has this new sharing function been used by everyone? Does this feature help me attract more new users?
7. Did the user click on the ad? On which app pages do they prefer to click ads? Which ads do they prefer to click?
8. Which users are more concerned about my app? Did they recommend my app to their friends?
9. Should I take the time to develop new features? Or do you want to improve performance and improve existing functionality? What is the next version to do?
10. Does my app help me move towards my business goals? Direction, right?
Real demand is Jinshan, false demand that is the trap, not only let you waste money, more wasted energy, if not timely identification of the true and false, it is equivalent to the hell of the high-speed rail.
How do I add telemetry capabilities to my app?
There are two types of methods, 1. Self-realization of all the monitoring point data collection, transmission and data analysis, presentation. Of course you have the best flexibility, but the energy you spend on it seems a bit too much. 2. Use of third-party services.
Looking at the top 10 questions, you should think that it's important to apply telemetry, but people who want to make a gold rush need to wear the jeans they get, but they don't have to build their own jeans. Here are a selection of jeans available in the market:
Data analysis focused on game applications
Focus on API monitoring and usage analysis of various internet public services such as OAuth, UserProfile, Search Engine, etc.
Data analysis focused on ad delivery
Originally a community-based testing service, it now provides a certain amount of online data analysis capabilities.
Of course, there are 2 important services that cannot be mentioned here, but also the services that bloggers use on this blog.
The benefits of using these third-party services are simple configuration and rich data analysis reports.
In WordPress, you can use the following two plug-ins to implement integration with Google Analytics or Azure Appinsight, which is the way bloggers use the site.
Google Analytics Dashborad for WP
(The code for the Azure application Insight plugin is open source and can be downloaded https://github.com/Microsoft/AppInsights-WordPress on GitHub)
Data analysis, report presentation
Of course, the above said so much, it is better to look at a few reports directly. So I intercepted some of this time to run this blog site in the process of the data generated by the report, to share, more importantly, these reports are missing to help me improve some of the way the operation.
First of all explain the background, Bo Master's article will be sent in several channels
1. ANB. IO This is the main station Http://anb.io
2. Blog Park http://www.cnblogs.com/ups216
3. CSDN http://blog.csdn.net/ups216
4. Subscription number Anb-io
In the past, I have made some adjustments based on these report data, and I have some experience
1. A list of articles is added to the top of all articles, and a link is placed so that the user can click on the link to enter the rest of the page and the clicks will be drained to the main station.
2. Added (video) words to the title of the article, only one change for each article more than 20% of the click-through rate
3. The headline is more eye-catching, the original title of this series is very technical, but you will find that starting from 3.2, the title began to grow longer and clearly appear "title Party" signs (I also hate the title party, but what to do also to do)
4. Release time adjustment, the beginning of several articles of the release time, and then I fixed at 11-12 noon a day to send between; because I found that most of the people who read my article use a PC to read, so the best reading time is actually the time to go to work at noon before and after dinner; You have to surf the internet after eating, and in the morning/evening in fact, more people will use mobile browsing, of course, the night before and after 11 o'clock hours there is a peak, it seems that programmers are missing a lot of owls.
5. The most wandering Blog park, whether in the blog park within the browser or click into the main station is the most, it seems that the audience is still very important.
6. Subscription number of the traffic is very small, my analysis is because the content of this series of articles is relatively strong, reading the subscription number on the phone, it is difficult to digest; Fast Track approach articles like # Friday # are good for reading and forwarding. It seems that the subscription number is relatively simple, easy to read digest articles, and not suitable for large articles of the technical category.
This is the end of the Quick Create site series. Hopefully this will not only help you understand the technology and knowledge behind some of the sites, but will also give you some insight into some of the relevant content (e.g., Application lifecycle Management, Devops,telemetry). The original intention of writing these articles is very simple, that is, I want to set up this site of the process of recording down, so that the same needs of friends can understand the process, do not seek advanced, just share.
Please pay attention to this blog subscription number Anb-io. Push content Weekly, have the technology also has the life, with you to do a have the sentiment program ape.
(VIDEO) "Quick Create Site" 4.2 End – Application operations vs. launch satellites, telemetry (Telemetry) technology