yzeng25 opened a new issue, #1303:
URL: https://github.com/apache/apisix-website/issues/1303

   ### Current State
   
   **Description of the current state/issue**:
   
   Blog are listing in a wrong order due to featured blogs.
   
   **Link to the page**:
   
   1. https://apisix.apache.org/blog/
   2. https://apisix.apache.org/blog/page/2/
   3. https://apisix.apache.org/blog/page/3/
   4. ...
   5. https://apisix.apache.org/blog/page/18/
   
   **Screenshots (if relevant)**:
   
   <img width="1920" alt="image" 
src="https://user-images.githubusercontent.com/36651058/187127980-ef708978-617e-4456-9924-5060d2dc7898.png";>
   
   <img width="1920" alt="image" 
src="https://user-images.githubusercontent.com/36651058/187128037-12b514b0-804a-4d6c-96af-d94cad6b1265.png";>
   
   <img width="1920" alt="image" 
src="https://user-images.githubusercontent.com/36651058/187128106-d804ed01-c70d-4a14-a86c-5051016f4b79.png";>
   
   
   
   ### Desired State
   
   **Description of the change you are proposing**:
   
   1. In the beginning page https://apisix.apache.org/blog/, it makes sense to 
have **latest** and **featured** blogs.
   2. In other pages (i.e. ~/page/2/ to ~/page/18/), it should have certain 
number of  **featured** blogs. Say there are 9 blogs in a page, then the range 
of the number of featured blogs is [0,9]. Can a page have no featured blog? IMO 
definitely yes. There is no need to make up featured blog for it.
   3. The modifications in `blog/en/config/picked-posts.json` and 
`blog/zh/config/picked-posts.json` should only apply to the first page, yet it 
is applying to **all** pages. In other words, you need to modify the scope of 
them.
   
   ### Would you like to fix this issue?
   
   No. Please assign another contributor


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to