Royale website requirements

Drawing from Managing your project website and other pages:

The website must

• satisfy the Apache branding requirements, in particular that certain links appear on the site's landing page, in whatever navigation structure the site uses. (Whimsy's Apache Project Website Checks tool periodically reviews all top-level project (TLP) websites to provide a report on how well they comply with that policy, and to identify issues that a project may need to address.)

  • "License" should link to: www.apache.org/licenses/

  • "Sponsorship" or "Donate" should link to: www.apache.org/foundation/sponsorship.html

  • "Sponsors", "Thanks" or "Thanks to our Sponsors" should link to: www.apache.org/foundation/thanks.html

  • "Security" should link to either to a project-specific page detailing how users may securely report potential vulnerabilities, or to the main www.apache.org/security/ page

  • "Privacy" should link to: privacy.apache.org/policies/privacy-policy-public.html.

  • All projects must feature some prominent link back to the main ASF homepage at www.apache.org. This may either be a featured link in your main navigation system or a text link in your Main homepage text. A best practice is to include a short sentence or paragraph on the homepage noting that this project is an Apache project, and is part of a larger community of developers and users.

The site also should

• explain what your project's product does
• pitch how your product solves a problem or creates a new opportunity
• invite people to get involved in the development team
• offer an easy way to download the latest builds of the product that you want the public to use
• provide documentation that will help people not part of the project understand how to get started with the product and how to keep going
• describe how the project team works, and its connection to the Apache Software Foundation
• explain how people can get in touch with the project to provide feedback or ask questions