dave2wave opened a new issue, #72:
URL: https://github.com/apache/pulsar-site/issues/72

   There needs to be a way for users to submit new content for these pages on 
these pages.
   
   The javascript files that contain this data are here - 
https://github.com/apache/pulsar-site/tree/main/site2/website-next/data
   
   - ? - 
[connectors.js](https://github.com/apache/pulsar-site/blob/main/site2/website-next/data/connectors.js)
 is this still live?
   - Ecosytem - 
[ecosystem.js](https://github.com/apache/pulsar-site/blob/main/site2/website-next/data/ecosystem.js)
   - Events - 
[events.js](https://github.com/apache/pulsar-site/blob/main/site2/website-next/data/events.js)
   - Resources - 
[resources.js](https://github.com/apache/pulsar-site/blob/main/site2/website-next/data/resources.js)
   - Meet the Community - 
[team.js](https://github.com/apache/pulsar-site/blob/main/site2/website-next/data/team.js)
   - Case Studies - 
[users.js](https://github.com/apache/pulsar-site/blob/main/site2/website-next/data/users.js)
   
   What is the proposed workflow?
   - for most of these pages it should start with an explanation with a link to 
create a PR at the bottom of the page.
   - for the team / community the PMC as whole should be responsible. Members 
of the PMC are PMC Members and not **PMCs**. PMCs are ambiguous, it could mean 
a group of people or more than one project management committee. The format of 
the Meet the Community section is another issue.
   


-- 
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: dev-unsubscr...@pulsar.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to