https://github.com/planet42/Laika is another one I got recommended.
On Wed, Nov 23, 2022 at 9:20 AM Matthew Benedict de Detrich < [email protected]> wrote: > So I found https://github.com/47degrees/sbt-microsites which is used in > the Scala community, there may be others as well. The nice thing > about sbt-microsites is that it would integrate with sbt if that's > something to aim for. > > On Wed, Nov 23, 2022 at 9:15 AM Matthew Benedict de Detrich < > [email protected]> wrote: > >> I will also ask around what is used in the Scala community for site >> generators >> >> On Tue, Nov 22, 2022 at 1:52 PM Claude Warren, Jr >> <[email protected]> wrote: >> >>> I think that we might want to look at pellican ( >>> https://infra.apache.org/asf-pelican.html) to build the pekko.apache.org >>> site. I think we can probably figure out how to merge the paradox stuff >>> into it. >>> >>> On Tue, Nov 22, 2022 at 10:47 AM PJ Fanning <[email protected]> >>> wrote: >>> >>> > For v1.0.0, the changes fall under these headings: >>> > * rename Java/Scala packages starting `akka.` to `org.apache.pekko.` >>> > * rename modules with names containing `akka` to use `pekko` instead >>> > * `alpakka` becomes `pekko-connectors` >>> > * change the config names to use `pekko` prefix instead of `akka` >>> prefix >>> > * possibly, also support reading `akka` prefix configs as a fallback >>> > * still need to work out if and how we could support mixed clusters of >>> > Akka and Pekko instances (remote/cluster modules) >>> > * there may be a need to change the default port numbers used in >>> > remote/cluster modules >>> > * the license header discussion appears not yet to be resolved causing >>> > much uncertainty about which path to take with the headers >>> > * it may be better to push on and leave the headers alone and come >>> > back to this later (any new files will get the default Apache header) >>> > * some existing files that don't have Lightbend copyright headers >>> > may need to be given a header (probably the default Apache header) >>> > * update the groupId for maven publishing from `com.typesafe.akka` to >>> > `org.apache.pekko` >>> > * a lot of the doc updates will need to be done as part of the code >>> > changes because the Paradox build type checks >>> > * notwithstanding this, there will be some residual doc changes that >>> > will need to be made to replace Lightbend with Apache and Akka with >>> > Pekko >>> > * change the styling on the generated docs so that they don't look >>> > exactly like the Akka docs >>> > * publish the website >>> > * start publishing nightly builds so that downstream modules can start >>> > using pekko modules instead of akka modules >>> > * update markdown docs for Github (README, Contributing, etc) >>> > * Fix broken CI builds - many are working but some others could need >>> > significant work to get running >>> > >>> > Some changes have happened in incubator-pekko git repo but we have >>> > about a dozen other git repos to look at too. >>> > >>> > The list above is not ordered and much of the work can happen in >>> parallel. >>> > >>> > I may have missed some items - please feel free to highlight any >>> > errors or omissions. >>> > >>> > >>> > On Tue, 22 Nov 2022 at 11:22, Claude Warren, Jr >>> > <[email protected]> wrote: >>> > > >>> > > I would like to propose 1 monster change. >>> > > >>> > > Do all the renaming and adding headers in one fell swoop. >>> > > >>> > > There seem to be several changes that need to be made across the >>> entire >>> > > codebase (renaming akka to pekko for example). >>> > > >>> > > I would like to see a list of all the large scale changes that need >>> to >>> > > occur. >>> > > >>> > > Then we can plan to make one massive change to lift and shift the >>> Akka >>> > > codebase to Pekko. >>> > > >>> > > This would be a planned move. My impression right now is that there >>> are >>> > a >>> > > bunch of "smaller" changes to complete the lift and shift but that >>> they >>> > are >>> > > not coordinated. This proposal is to coordinate that and encompass >>> it >>> > as a >>> > > single change (though perhaps multiple pull requests). >>> > > >>> > > Thoughts? >>> > > >>> > > Claude >>> > >>> > --------------------------------------------------------------------- >>> > To unsubscribe, e-mail: [email protected] >>> > For additional commands, e-mail: [email protected] >>> > >>> > >>> >> >> >> -- >> >> Matthew de Detrich >> >> *Aiven Deutschland GmbH* >> >> Immanuelkirchstraße 26, 10405 Berlin >> >> Amtsgericht Charlottenburg, HRB 209739 B >> >> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen >> >> *m:* +491603708037 >> >> *w:* aiven.io *e:* [email protected] >> > > > -- > > Matthew de Detrich > > *Aiven Deutschland GmbH* > > Immanuelkirchstraße 26, 10405 Berlin > > Amtsgericht Charlottenburg, HRB 209739 B > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > *m:* +491603708037 > > *w:* aiven.io *e:* [email protected] > -- Matthew de Detrich *Aiven Deutschland GmbH* Immanuelkirchstraße 26, 10405 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen *m:* +491603708037 *w:* aiven.io *e:* [email protected]
