You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@pekko.apache.org by "jrudolph (via GitHub)" <gi...@apache.org> on 2023/02/13 10:46:33 UTC
[GitHub] [incubator-pekko-sbt-paradox] jrudolph opened a new issue, #26: Figure out how to organize community documentation
jrudolph opened a new issue, #26:
URL: https://github.com/apache/incubator-pekko-sbt-paradox/issues/26
(as @pjfanning mentioned in https://github.com/apache/incubator-pekko/issues/92#issuecomment-1407728069):
We should have links to community information like:
* Downloads
* Developer Resources
* Community
* we will need to create the pages for these items to link to
We probably would put all of this information on the main homepage and just link from the documentation to the main page for this kind of information?
How do we deal with download links since they will be different for each subproject. I guess we would add those to the project documentations?
--
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: notifications-unsubscribe@pekko.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko-sbt-paradox] jrudolph commented on issue #26: Figure out how to organize community documentation
Posted by "jrudolph (via GitHub)" <gi...@apache.org>.
jrudolph commented on issue #26:
URL: https://github.com/apache/incubator-pekko-sbt-paradox/issues/26#issuecomment-1448003976
The question is more about how it should look like than how to achieve the desired result.
--
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: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko-sbt-paradox] pjfanning commented on issue #26: Figure out how to organize community documentation
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #26:
URL: https://github.com/apache/incubator-pekko-sbt-paradox/issues/26#issuecomment-1427728952
We might be able to repurpose the main branch of https://github.com/apache/incubator-pekko-site
That repo is temporarily being used to publish the pekko.apache.org site manually (by commits to the asf-site and asf-staging branches) - but we could start using the main branch to build pages for the web site that are not related to the existing code repos. We can then also add a publish-to-rsync CI action.
--
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: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org