tuteng opened a new pull request #8898:
URL: https://github.com/apache/pulsar/pull/8898


   <!--
   ### Contribution Checklist
     
     - Name the pull request in the form "[Issue XYZ][component] Title of the 
pull request", where *XYZ* should be replaced by the actual issue number.
       Skip *Issue XYZ* if there is no associated github issue for this pull 
request.
       Skip *component* if you are unsure about which is the best component. 
E.g. `[docs] Fix typo in produce method`.
   
     - Fill out the template below to describe the changes contributed by the 
pull request. That will give reviewers the context they need to do the review.
     
     - Each pull request should address only one issue, not mix up code from 
multiple issues.
   
   
   
   ### Motivation
   
   This is an update after https://github.com/apache/pulsar/pull/8888, where 
`functions` should jump to `/functions-rest-api`,  `source` should jump to 
`/source-rest-api`, `sink` should jump to `/sink-rest-api`
   
   ### Modifications
   
   * Update route jump
   * Update markdown content render
   
   ### Verifying this change
   
   - [ ] Make sure that the change passes the CI checks.
   
   
![image](https://user-images.githubusercontent.com/1907867/101758422-4603be80-3b13-11eb-8cb8-358d30b96113.png)
   
![image](https://user-images.githubusercontent.com/1907867/101758522-63d12380-3b13-11eb-9f7e-00a0e095ef98.png)
   
   When release website, pulsar:version_number will be automatically replaced 
with the current pulsar version number
   
   
   
   ### Documentation
   
     - Does this pull request introduce a new feature? (yes / no)
     - If yes, how is the feature documented? (not applicable / docs / JavaDocs 
/ not documented)
     - If a feature is not applicable for documentation, explain why?
     - If a feature is not documented yet in this PR, please create a followup 
issue for adding the documentation
   


----------------------------------------------------------------
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.

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


Reply via email to