Hi Alex, I’m not personally using Royale for anything besides SPAs. Our website has gone through a couple of iterations, but is currently a Wordpress site.
I know the biggest pain-point of our website has been updating content (by non-web-devs). None of the CMS solutions are perfect (we tried Drupal at one point and that was very painful). Editing raw HTML is also not really a good solution. Currently, we’re using Wordpress with the Elementor to update content. It’s the best solution we’ve had to date, but it’s still a little fiddly. It’s not bad for a corporate site, but not really a good solution for an open source project. It would be interesting to see if Markdown might be a better solution. It’s hard to know exactly what I’ll run into until I try, but I suspect it’ll work pretty well. I’m not sure if I understand exactly what you’re proposing. Are you suggesting a JIT compile of Royale to display? I do like the idea of a sandbox which would render Royale markup in real time. I seem to recall that someone started work on that a long time ago. Harbs > On Dec 5, 2021, at 7:36 PM, Alex Harui <[email protected]> wrote: > > Hi Harbs, > > No objection from me if you want to do that, but I'm wondering how often > markdown is being used on the sites that are hosting Royale apps, like the > one you are working on for your business. If you aren't using markdown, and > are just using some HTML around the Royale app, it might be better if the > Royale site does the same thing so the site source serves as a template of > how to integrate a Royale app in a production site. Then build out a Royale > app for the "Contact Us" or "Ask a Question" form of the site. Or if you are > really ambitious, a sandbox/playground/RoyaleFiddle. > > Just throwing out an alternative, and I am curious to know what integration > patterns folks are using around their Royale apps. > > My 2 cents, > -Alex > > On 12/5/21, 5:23 AM, "Harbs" <[email protected]> wrote: > > OK. I’ll hopefully start on this sometime this week. > > Once I make some progress I’ll probably try and coordinate with you on how > to best document it. > > If anyone has further thoughts, please let me know. > > Harbs > >> On Dec 5, 2021, at 2:57 PM, Andrew Wetmore <[email protected]> wrote: >> >> Excellent. We will need both maintenance and user-facing documentation, but >> once we have this in place Royale will be much stronger and more suitable >> to many more uses. >> >> On Sun, Dec 5, 2021 at 8:54 AM Harbs <[email protected] >> <mailto:[email protected]>> wrote: >> >>> Great. >>> >>> After spending some time looking at existing implementations, I think I’m >>> going to port the parsing code from >>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjonschlinkert%2Fremarkable&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123879886%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=bMEVqu1lVeMME1eoDB868%2FHHiyjspldgrNlWdGi3eYg%3D&reserved=0 >>> >>> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjonschlinkert%2Fremarkable&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123879886%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=bMEVqu1lVeMME1eoDB868%2FHHiyjspldgrNlWdGi3eYg%3D&reserved=0> >>> < >>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjonschlinkert%2Fremarkable&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123879886%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=bMEVqu1lVeMME1eoDB868%2FHHiyjspldgrNlWdGi3eYg%3D&reserved=0 >>> >>> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjonschlinkert%2Fremarkable&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123879886%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=bMEVqu1lVeMME1eoDB868%2FHHiyjspldgrNlWdGi3eYg%3D&reserved=0>> >>> >>> It’s well organized and the performance is very good. >>> >>> >>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.measurethat.net%2FBenchmarks%2FShow%2F8434%2F0%2Fmarkdown-performance-comparison%23latest_results_block&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123879886%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=GvD%2BIgtyklzjiMbQaapHK3bTMmV5%2FH2rO7h5rNRwgsM%3D&reserved=0 >>> >>> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.measurethat.net%2FBenchmarks%2FShow%2F8434%2F0%2Fmarkdown-performance-comparison%23latest_results_block&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=UDn632N9F8%2FqqSBE8osyGMTPvZaIIv9sWy9h%2BIRldIk%3D&reserved=0> >>> < >>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.measurethat.net%2FBenchmarks%2FShow%2F8434%2F0%2Fmarkdown-performance-comparison%23latest_results_block&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=UDn632N9F8%2FqqSBE8osyGMTPvZaIIv9sWy9h%2BIRldIk%3D&reserved=0 >>> >>> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.measurethat.net%2FBenchmarks%2FShow%2F8434%2F0%2Fmarkdown-performance-comparison%23latest_results_block&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=UDn632N9F8%2FqqSBE8osyGMTPvZaIIv9sWy9h%2BIRldIk%3D&reserved=0> >>>> >>> >>> Only Snarkdown is faster, but that implementation seems very bare-bones >>> and outputs directly to html. >>> >>> Here’s the approach that I’m considering: >>> >>> 1. Markdown gets parsed into nodes. >>> 2. We have a mapper class which maps nodes to corresponding IParentUIBase >>> components. This map will be customizable. >>> 3. We walk down the node tree and create and populate the components. >>> 4. I’d like to hook this into a Router for navigation. >>> >>> I’m probably going to do this with my daughter who is in school to serve >>> as a practice lesson in generating and using document trees. B-) >>> >>>> On Dec 5, 2021, at 1:17 AM, Andrew Wetmore <[email protected]> wrote: >>>> >>>> I would be happy to help with this. I started to build such a parser >>> myself >>>> a few months back, but got swamped with work. It would be an excellent >>>> demonstration of how adaptable Royale is. >>>> >>>> On Sat, Dec 4, 2021 at 7:07 PM Harbs <[email protected]> wrote: >>>> >>>>> I’ve been thinking about the website and I had an idea. >>>>> >>>>> The problems we have with the website currently: >>>>> >>>>> 1. You need to loging to Wordpress to make changes. >>>>> 2. It relies on external resources. >>>>> 3. There’s no way to make pull requests to improve the website. >>>>> 4. It doesn’t showcase Royale. If we could "eat our own dogfood”, that >>>>> would be great. >>>>> >>>>> Royale *can* be used to generate a website, but it’s not really great >>> for >>>>> writing or updating content. >>>>> >>>>> The best way (IMO) to write content is using markdown. We can create a >>>>> Royale app which loads markdown files to populate content. We can route >>>>> based on the URL to specific markdown files to determine which content >>> to >>>>> load. >>>>> >>>>> The content can be formatted by mapping markdown nodes to Royale >>>>> components. You could have multiple mappings in a single document so >>>>> multiple markdown files can be used to populate content in different >>> areas >>>>> (i.e. sidebar, footer, main content, etc.) >>>>> >>>>> I’m willing to volunteer to write the parser and mapper if others like >>> the >>>>> idea and are willing to participate in other aspects. There’s a couple >>> of >>>>> appropriately licensed projects that I can borrow code from for the >>> parsing >>>>> logic. >>>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmarkdown-it%2Fmarkdown-it&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Tg0uti7eYUyWcU1lfLPCKWG3RwfeKTo3KZj6TBW%2FCL4%3D&reserved=0 >>>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshowdownjs%2Fshowdown&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=tBcvqDuVYJG8oKQhUDufE6ftYSC1K5xvEnn0c15q8es%3D&reserved=0 >>>>> >>>>> Thoughts? >>>>> >>>>>> On Apr 18, 2021, at 2:52 PM, Andrew Wetmore <[email protected]> >>> wrote: >>>>>> >>>>>> Hi, all: >>>>>> >>>>>> I have created a wiki page [1] where we can scope out developing the >>>>> Royale >>>>>> website as built using Royale. I have suggested some requirements, some >>>>>> "nice to have" things and some things that are not required; however >>>>> these >>>>>> are just my ideas. Input from others until we reach consensus would be >>>>>> useful. >>>>>> >>>>>> Here is one specific point: there are a couple of abandoned efforts to >>>>>> build the Royale site using Royale. Do we use these repositories, or >>>>> create >>>>>> a new one for this effort? >>>>>> >>>>>> a >>>>>> >>>>>> 1. >>>>>> >>>>> >>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRoyale-project-site-built-with-Royale&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=GXBzRe%2FK0UsgloDomp0%2BOWAkc1tvDNCR%2BL8Ef49iSiw%3D&reserved=0 >>>>>> >>>>>> On Fri, Apr 16, 2021 at 12:29 PM Alina Kazi <[email protected]> >>>>> wrote: >>>>>> >>>>>>> Congrats Andrew. >>>>>>> >>>>>>> Yes we can add viewstates (includeIn), phone/tablet/desktop Numerator >>>>>>> denominator to adjust the view on different devices, common header and >>>>>>> footer and much more. >>>>>>> We'll be waiting for the wiki page tomorrow to get started. >>>>>>> >>>>>>> Thanks, >>>>>>> Alina Kazi >>>>>>> >>>>>>> On Fri, 16 Apr 2021, 7:29 PM Piotr Zarzycki, < >>> [email protected] >>>>>> >>>>>>> wrote: >>>>>>> >>>>>>>> Congrats Andrew! >>>>>>>> >>>>>>>> pt., 16 kwi 2021 o 13:31 Andrew Wetmore <[email protected]> >>>>>>> napisał(a): >>>>>>>> >>>>>>>>> Today my wife and I have appointments, a long drive from home, to >>> get >>>>>>> our >>>>>>>>> first COVID-19 injections. This will probably use up most of the >>> day, >>>>>>>>> leaving aside possible side-effects, so I likely will not have the >>>>> wiki >>>>>>>>> page about the web site ready to receive ideas and concerns until >>>>>>>> tomorrow >>>>>>>>> at the earliest. >>>>>>>>> >>>>>>>>> a >>>>>>>>> >>>>>>>>> On Thu, Apr 15, 2021 at 8:33 PM Maria Jose Esteve < >>> [email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> What dizziness! jajajaja >>>>>>>>>> >>>>>>>>>> Hiedra >>>>>>>>>> >>>>>>>>>> -----Mensaje original----- >>>>>>>>>> De: Andrew Wetmore <[email protected]> >>>>>>>>>> Enviado el: viernes, 16 de abril de 2021 1:29 >>>>>>>>>> Para: Apache Royale Development <[email protected]> >>>>>>>>>> Asunto: Re: Use Royale to build the Royale website? >>>>>>>>>> >>>>>>>>>> This is great. >>>>>>>>>> >>>>>>>>>> To start, I think I will create a wiki page so we can capture what >>> we >>>>>>>>> must >>>>>>>>>> have and what we would like to have in the website. For me, our >>>>>>> website >>>>>>>>>> must communicate useful and engaging information about our project >>>>>>> and >>>>>>>>> what >>>>>>>>>> one can do with Royale. I would also like to include some features >>> to >>>>>>>>>> demonstrate a little bit of what Royale can do--maybe viewstates to >>>>>>>>> manage >>>>>>>>>> what displays when, localization (at least some of the site), >>>>>>>> responsive >>>>>>>>> so >>>>>>>>>> it appears well on laptops and mobile devices, use of CSS, and >>> other >>>>>>>>>> stuff...and then we can use the website itself as a demonstration >>> of >>>>>>>>>> Royale's versatility. >>>>>>>>>> >>>>>>>>>> The Infra guidelines say a project's site should not be dynamic, in >>>>>>> the >>>>>>>>>> sense of using HTTP calls to get data that it then displays: the >>> site >>>>>>>>>> should be "flat". But we may find that Royale code compiled to >>>>>>>>> JavaScript >>>>>>>>>> can do lots of interestng things wiithout breaking the Infra rules. >>>>>>>>>> >>>>>>>>>> I will set up the wiki page tomorrow and let you all know that it >>> is >>>>>>>>>> available for adding ideas. >>>>>>>>>> >>>>>>>>>> Andrew >>>>>>>>>> >>>>>>>>>> On Thu, Apr 15, 2021 at 5:42 PM Alina Kazi < >>> [email protected]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> Great Maria and really its very good to show it in ApacheCon 2021. >>>>>>>>>>> >>>>>>>>>>> Great Idea Andrew, I would also love to contribute in any way I >>>>>>> can. >>>>>>>>>>> Also, If you have some design in mind. Share with us. >>>>>>>>>>> Create a source repository,so we can start with jewel basic flat >>>>>>>> theme >>>>>>>>>>> or any other option that community suggests. We start migrating >>>>>>>>>>> wordpress website step by step. Until we have virtual machine or >>>>>>>> other >>>>>>>>>> stuff ready. >>>>>>>>>>> >>>>>>>>>>> Alina Kazi >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Thu, 15 Apr 2021, 10:03 PM Maria Jose Esteve, < >>>>>>> [email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi guys, >>>>>>>>>>>> >>>>>>>>>>>> Andrew, I can help, I think the community has to make an effort >>>>>>> if >>>>>>>>>>>> we >>>>>>>>>>> want >>>>>>>>>>>> to get to ApacheCon 2021 😝 >>>>>>>>>>>> >>>>>>>>>>>> Have you thought about a redesign of the website or a >>>>>>>> "translation"? >>>>>>>>>>>> >>>>>>>>>>>> How could I contribute? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Hiedra >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -----Mensaje original----- >>>>>>>>>>>> De: Andrew Wetmore <[email protected]> Enviado el: jueves, 15 >>>>>>> de >>>>>>>>>>>> abril de 2021 1:51 >>>>>>>>>>>> Para: Apache Royale Development <[email protected]> >>>>>>>>>>>> Asunto: Use Royale to build the Royale website? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Hi: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> At the moment the Royale website depends on a private server >>>>>>>> running >>>>>>>>>>>> WordPress. I wonder if it is time to build and deploy it using >>>>>>>>>>>> Royale itself. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> We don't need the great strengths of Royale--dynamic display, >>>>>>>> subtle >>>>>>>>>>>> data-processing, and so on--to support the site. It is (as all >>>>>>>>>>>> projects sites are intended to be) a flat, relatively static >>>>>>>>>>>> website. That should mean that running our own website with the >>>>>>> aid >>>>>>>>>>>> of our own tool should be far from impossible. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> What is required? If I understand correctly, we would need Infra >>>>>>> to >>>>>>>>>>>> provide a virtual machine on which we could install and run a >>>>>>>> stable >>>>>>>>>>>> instance of Royale, and a repository of the site's source code in >>>>>>>>>>>> MXML >>>>>>>>>>> and >>>>>>>>>>>> AS files, just like a real Royale application.. Each time we >>>>>>>> updated >>>>>>>>>>>> a >>>>>>>>>>> page >>>>>>>>>>>> or a file in the website repository, Infra's automated tools >>>>>>> would >>>>>>>>>>>> set >>>>>>>>>>> off >>>>>>>>>>>> a build and deployment of the updated site. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Some time ago a proof-of-concept was partly built to do this very >>>>>>>>>>>> thing, so we have some resources to start from. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Benefits: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- Since it is a simple website, it should probably be an >>>>>>> exercise >>>>>>>>>>>> contributors and committers at many skill levels could help work >>>>>>>> on. >>>>>>>>>>>> >>>>>>>>>>>> -- It would give us a "brag" to point to. >>>>>>>>>>>> >>>>>>>>>>>> -- We would move over to open-source resources, rather than those >>>>>>>> of >>>>>>>>>>>> WordPress.. >>>>>>>>>>>> >>>>>>>>>>>> -- Infra has an efficient and stable CI process in place that can >>>>>>>>>>>> work with Royale's command-line to trigger builds and deployment. >>>>>>>>>>>> >>>>>>>>>>>> -- Other???? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Costs: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- Time to migrate the existing site into Royale assets. >>>>>>>>>>>> >>>>>>>>>>>> -- Other????? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> What do you all think of such a proposal? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> a >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> >>>>>>>>>>>> Andrew Wetmore >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Andrew Wetmore >>>>>>>>>> >>>>>>>>>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=fZXlbU%2F0GpiJVY8V75%2BLcrGGtsP3HZ0TQ%2BVAjC626EI%3D&reserved=0 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Andrew Wetmore >>>>>>>>> >>>>>>>>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=fZXlbU%2F0GpiJVY8V75%2BLcrGGtsP3HZ0TQ%2BVAjC626EI%3D&reserved=0 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Piotr Zarzycki >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Andrew Wetmore >>>>>> >>>>>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=fZXlbU%2F0GpiJVY8V75%2BLcrGGtsP3HZ0TQ%2BVAjC626EI%3D&reserved=0 >>>>> >>>>> >>>> >>>> -- >>>> Andrew Wetmore >>>> >>>> Editor, Moose House Publications >>>> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmoosehousepress.com%2F&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=LsllFc9B5ut3wZoqm3vMO3%2BVHb1Fi%2FL3RmSsLFTNnHE%3D&reserved=0> >>>> Editor-Writer, The Apache Software Foundation >>>> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache.org%2F&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=CvXE4RpgbIvvhcTsj%2FvHPYboNM3itwXu1YhYX6o1%2Bpw%3D&reserved=0> >>> >>> >> >> -- >> Andrew Wetmore >> >> Editor, Moose House Publications >> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmoosehousepress.com%2F&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=LsllFc9B5ut3wZoqm3vMO3%2BVHb1Fi%2FL3RmSsLFTNnHE%3D&reserved=0 >> >> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmoosehousepress.com%2F&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=LsllFc9B5ut3wZoqm3vMO3%2BVHb1Fi%2FL3RmSsLFTNnHE%3D&reserved=0>> >> Editor-Writer, The Apache Software Foundation >> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache.org%2F&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=CvXE4RpgbIvvhcTsj%2FvHPYboNM3itwXu1YhYX6o1%2Bpw%3D&reserved=0 >> >> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache.org%2F&data=04%7C01%7Caharui%40adobe.com%7Ce3e93b8995b14a9e479708d9b7f26ddf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637743074123889842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=CvXE4RpgbIvvhcTsj%2FvHPYboNM3itwXu1YhYX6o1%2Bpw%3D&reserved=0>> > >
