I’m glad for this proposal. I agree with the users’ journey being our first point of view, I have a friend that share her personal experience with project website.
>From her opinion she visit the blog page before visiting the get started page. Gathering these user stories will help us understand how individuals approach the project website for content. On Tue, 22 Feb 2022 at 10:02 AM, Nicolas Frankel <nico...@api7.ai> wrote: > Hello 👋 > > It's hard to agree or disagree with this proposal because we don't have a > solid analysis of the existing situation first. I think we need to really > take a step back. > > 1. Do we have a representative sample of users' journey? I assume it's a > no, then it should be our first step. A lot can be gleaned from Google > Analytics and the behavior flow page. For example, right now, the > majority > of people come to the site and their next step is to set the lang to > Chinese, then they go to getting started, then to "how to build". > That's an > issue IMHO. > 2. A website is not an email, people don't browse it linearly. Different > people will browse it differently. I'd advise to come up with a few > personas - the newbie, the dev, the ops, Then, we can model their > journey > on a 2D map. I've seen one DX person (a former colleague) do it in the > past, it's amazing. If you're interested, I can ask my colleague for > pointers, or persons to help us. > 3. Whatever we do, it's all based on assumptions. After a change, we > absolutely need to do A/B testing to validate/in- them. > > Nicolas > > On Mon, Feb 21, 2022 at 11:04 AM Anita Ihuman <an...@api7.ai> wrote: > > > This is a proposed structure I think the Project Docs should take. Please > > include other contents that you think are missing from this page. > > Also add your review. Thanks > > Project Documentation: > > *Overview* > > Apache APISIX is a cloud-native high-performing API gateway, that > delivers > > the ultimate performance, security, open-source and scalable platform for > > all your APIs and microservices. > > It provides hundreds of items such as load balancing, dynamic upstream, > > grayscale publishing, refined routing, current and speed limiting, > service > > degradation, service fuse, identity authentication, and observability. > > > > - *What is Apache APISIX* > > > > Apache APISIX is an open source, dynamic, high-performance, and scalable > > 7-layer proxy. It acts as a service bus that connects APIs and > > microservices in cloud-native architectures. > > > > - *The problem APISIX solves* > > - Help enterprises to solve the difficulties in the transformation > of > > traditional monolithic architecture, so as to achieve rapid > > iteration of > > business and products. > > > > > > - Apache APISIX handles traditional north-south traffic, as well as > > east-west traffic between services. It can also be used as a k8s > ingress > > controller <https://github.com/apache/apisix-ingress-controller>. > > > > > > - Easy to use: APISIX also consists of a built-in low-code dashboard > > that offers a powerful and flexible interface. You can write your own > > custom plugins or use custom load balancing algorithms. > > > > > > - Apache APISIX supports multi-platforms, languages and protocols. > > > > > > - *Features* > > > > Apache APISIX not only covers the traditional functions of NGINX, but > also > > deeply cooperates with Apache SkyWalking in observability, which greatly > > improves service governance capabilities. Some of the characteristics of > > the Apache APISIX gateway include; > > > > - Full Dynamic > > > > > > - Fine-grained routing > > > > > > - OPS friendly > > > > > > - Highly scalable > > > > > > - Security > > > > > > - Multi protocols > > > > > > - Multi-Language support > > > > *Getting started * > > > > - > > > > *Architecture* > > > > - requires a detailed description of the architecture diagram. > > > > > > - Core Concepts > > > > *Platforms* > > This will list the different ways to run and install APISIX on different > > platforms. > > > > - Kubernetes > > > > > > - Helm > > > > > > - Mac > > > > *How to Build* > > > > - > > > > *Plugins <https://apisix.apache.org/docs/apisix/how-to-build#>* > > > > - > > > > *API <https://apisix.apache.org/docs/apisix/how-to-build#>* > > *Release Management* > > This release guide already exists under resources, but I think it should > be > > under documentation. > > *CHANGELOG <https://github.com/apache/apisix/blob/master/CHANGELOG.md>* > > > > - > > > > *Others <https://apisix.apache.org/docs/apisix/how-to-build#>* > > > > - > > > > *Reference* > > > > - > > > > > > - *Highlight the existing sites that reference APISIX* > > > > *FAQ <https://apisix.apache.org/docs/apisix/FAQ>* > > > > - > > >
