Closed graphitefriction closed 8 months ago
The asciidoctor one is sharp. Let's go with a minor variations on that.
I can massage the language once the template is in, but I want to make sure Webtide is there as a link and state that the project is made possible by Webtide since we fully fund it. We should also do the additional thanks to companies like IntelliJ for their license contributions to the developers, and to the Eclipse Foundation, etc.
Something I noticed on the asciidoctor one was that docs seem to be under docs.asciidoctor.org which made me wonder if we should do the same. We have full control over jetty.org, so subdomains are certainly viable.
The primary logo should still be the jetty:// one and we should see about the webtide:// one scaling down to be akin to the Netify one.
We are @JettyProject on X/Twitter.
Thanks for that info. That's plenty to put together a PR.
I put something together, though it's far from perfect.
One thing to keep in mind is that when you are dealing with an element like a footer, the design and the content go hand-in-hand. Changing the content often requires the design to be changed because the goal is a tight fit. It doesn't flow like the article of the document. However, it should be straightforward for a designer to work with src/partials/footer-content.hbs and src/css/footer.css to achieve any design.
The footer for the site is global, i.e. it's displayed at the bottom of every page.
What content, such as images, text, icons, etc., do you want displayed in the footer?
For example, do you want (or are required) to use the footer currently on https://eclipse.dev/jetty/?
If not, the footer can be minimalist, such as the footers on these sites:
Or, it can be more complex, like:
In summary: