bhasudha commented on PR #6638:
URL: https://github.com/apache/hudi/pull/6638#issuecomment-1250195788

   > Can you share some screenshots here.
   > 
   > IMO main things to have as tags.
   > 
   > **tag1**
   > 
   > * how-to (tutorial, recipes, show case how to use feature x)
   > * case-study. (some company talking about their use-case)
   > * deep-dive (technical articles talking about Hudi internal design/impl)
   > * architecture (broader ones talking about data architectures etc)
   > 
   > **tag 2** you can then tag individual features - clustering, compaction, 
etc.
   > 
   > **tag 3** you can then add the use-case - ingestion, etl, .. (or skip if 
it applies in general)
   > 
   > Please add a section like this to README and we then land this, this way 
we can review all future entries for accuracy/ to be inline with this
   
   Done. Please take a look. 
   
   The site would look like this with tags.
   
   
   <img width="1415" alt="Screen Shot 2022-09-17 at 9 51 12 PM" 
src="https://user-images.githubusercontent.com/2179254/190887259-4d132474-0763-48c2-ba03-7413242588fb.png";>
   <img width="1440" alt="Screen Shot 2022-09-17 at 9 51 37 PM" 
src="https://user-images.githubusercontent.com/2179254/190887263-ea1b6818-2bda-4fe6-9b53-7ddd7915168d.png";>
   <img width="1439" alt="Screen Shot 2022-09-17 at 9 51 55 PM" 
src="https://user-images.githubusercontent.com/2179254/190887265-35aaf835-aba4-4003-a337-e10f72b02511.png";>
   <img width="1475" alt="Screen Shot 2022-09-17 at 9 52 09 PM" 
src="https://user-images.githubusercontent.com/2179254/190887266-c89566c3-653f-4e1e-b656-1ec1953e0795.png";>
   <img width="1479" alt="Screen Shot 2022-09-17 at 9 52 21 PM" 
src="https://user-images.githubusercontent.com/2179254/190887267-7936a983-2aa9-48ac-a8b0-0083ac2cf973.png";>
   
   


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