Great teamwork :) I am seeing the error with the downloads page coming from the first google search list, https://ozone.apache.org/downloads/ -> This says 404.
Valid link: https://ozone.apache.org/download/ Will this fix on its own with search indexes getting updated or should we fix this? On Wed, Feb 11, 2026 at 7:23 AM Siyao Meng <[email protected]> wrote: > Congrats on the launch of the new site! > > --- > > For the search issue, I can see *(blocked:csp)* for requests to * > algolia.net > <http://algolia.net>* in Chrome devtools. Looks > like Content-Security-Policy blocked the search from functioning. > > > https://support.algolia.com/hc/en-us/articles/8947249849873-How-do-I-fix-Content-Security-Policy-CSP-errors-on-my-site > > The current CSP header in the response looks like this: > > default-src 'self' data: blob: 'unsafe-inline' 'unsafe-eval' > > https://www.apachecon.com/ https://www.communityovercode.org/ https://*. > > apache.org/ https://apache.org/ https://*.scarf.sh/ ; script-src 'self' > > data: blob: 'unsafe-inline' 'unsafe-eval' https://www.apachecon.com/ > > https://www.communityovercode.org/ https://*.apache.org/ > > https://apache.org/ https://*.scarf.sh/ ; style-src 'self' data: blob: > > 'unsafe-inline' 'unsafe-eval' https://www.apachecon.com/ > > https://www.communityovercode.org/ https://*.apache.org/ > > https://apache.org/ https://*.scarf.sh/ ; frame-ancestors 'self'; > > frame-src 'self' data: blob: 'unsafe-inline' 'unsafe-eval' > > https://www.apachecon.com/ https://www.communityovercode.org/ https://*. > > apache.org/ https://apache.org/ https://*.scarf.sh/ ; worker-src 'self' > > data: blob:; > > > According to the doc linked above it is missing: > > connect-src https://*.algolia.net https://*.algolianet.com https://*. > > algolia.io > > > I then found Apache Infra doc here: > https://infra.apache.org/tools/csp.html > > Each additional host you add MUST have been pre-approved by VP Data Privacy > > ([email protected]), and SHOULD have an accompanying comment in the > > .htaccess file explaining why the CSP is changed and where permission was > > obtained. > > > > So it looks like we need to obtain approval from [email protected] before > we can add these CSP hosts. Interestingly the example it gives is algolia, > so there shouldn't be too much friction. > > I will send the email to ask for approval and raise a PR for it. > > -Siyao > > On Tue, Feb 10, 2026 at 1:07 AM Zita Dombi <[email protected]> wrote: > > > Great news!! :) > > > > The search function, I used keywords like "SCM", "Snapshot", "Ozone", all > > > "No results". What's the recommended keywords for searching? > > > > > > This is supposed to add the searching capability: > > https://github.com/apache/ozone-site/pull/328 > > but it looks like something is missing, it doesn't work for me either. > > > > Zita > > > > Sammi Chen <[email protected]> ezt írta (időpont: 2026. febr. 10., K, > > 5:08): > > > > > Awesome!!! > > > > > > I just used the new site, it's great! > > > > > > The search function, I used keywords like "SCM", "Snapshot", "Ozone", > all > > > "No results". What's the recommended keywords for searching? > > > > > > > > > On Tue, 10 Feb 2026 at 07:42, Wei-Chiu Chuang <[email protected]> > > wrote: > > > > > > > Hello community, > > > > > > > > I’m excited to announce that the *new Apache Ozone website > > > > <https://ozone.apache.org/> is officially live*! 🎉 > > > > > > > > The site is now powered by *Docusaurus*, giving it a more modern look > > > and a > > > > significantly improved documentation experience. Beyond visual > updates, > > > > we’ve *fully revamped the documentation structure* to make it easier > to > > > > navigate and more approachable. > > > > > > > > The new docs are organized by persona, including: > > > > > > > > - > > > > > > > > Users > > > > - > > > > > > > > Application developers > > > > - > > > > > > > > Administrators > > > > - > > > > > > > > Core Ozone developers > > > > > > > > Whether you’re just getting started, operating a production cluster, > > > > building applications on top of Ozone, or diving deep into system > > > > internals, the new documentation is designed to meet you where you > are. > > > > > > > > We’ve put extra care into clarity and onboarding, especially for new > > > users > > > > and administrators—while still preserving the depth needed by > > experienced > > > > contributors. > > > > > > > > Take a look, explore, and let us know what you think. This is just > the > > > > beginning, and community feedback will help us continue to improve. > > > > > > > > Happy exploring! 🚀 > > > > Wei-Chiu > > > > > > > > > >
