aoepeople / aoepeople.github.io Goto Github PK

Use correct colors, fonts, shadows, buttons to fit the AOE design system

We are always hungry, and booking our lunch via aoe meals is so awesome, we should tell the world

If you check the website with Lighthouse, you will find some points that might be worth a look.
I have attached the report here as a PDF and list some points below.

OPPORTUNITIES

• #26 Properly size images: Serve images that are appropriately-sized to save cellular data and improve load time.
• #26 Serve images in next-gen formats

NAMES AND LABELS

• #28 Image elements do not have [alt] attributes: These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

MOBILE FRIENDLY

• #29 Does not have a tag with width or initial-scale: A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input.

CONTENT BEST PRACTICES

• #30 Document does not have a meta description: Meta descriptions may be included in search results to concisely summarize page content.

20220317_LighthouseFindings.pdf

We manage our releases with semanticore, and that is so awesome that we want to have a blogpost

We want a sub-page to feature our AOE Technology Radar.
The focus is our technology radar generator: https://github.com/AOEpeople/aoe_technology_radar - this is an active and by many people used Project, so it would be nice to show some background, information, etc. here

• Create a sub page
• Write some Technology Radar content

We learned about the roomba camera mod in our aoe weekly, and would love to have a small post about that

We have repositories which are automatically used and often kept up to date, such as AOEpeople/_preview-opensource.
There is no need to show these repositories, so we want some way to exclude them.

Possible usage: have a list of excluded repos, fetch 6+len(list) and filter out repos and display up to 6.

https://opensource.aoe.com/posts/

To improve SEO we need content meta tags

We want to define alt texts for images

Does not have a tag with width or initial-scale: A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input.

Extend the feed to provide more data such as

• Tags
• Authors
• Preview-Image

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @tailwindcss/typography to v0.5.13
• chore(deps): update dependency tailwindcss to v3.4.3
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update dependency ubuntu to v22
• chore(deps): update github artifact actions to v4 (major) (actions/download-artifact, actions/upload-artifact)
• chore(deps): update peaceiris/actions-gh-pages action to v4
• chore(deps): update peaceiris/actions-hugo action to v3
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

We use remix in our new frontends and would love to read a little about remix

Images are currently transported "raw".
We should (re-)encode them, resize them and support nextgen image formats.

Still a preview-feature, but so complicated we should blog about it

Resizing is currently not supported
gohugoio/hugo#5030

Serve assets (fonts, JS, ...) from static folder instead of foreign sources, like Google Fonts or CDNs

For some workloads, we need to connect dynamic pods with a static wireguard setup, so we run sidecar containers which set up the required VPN. This is so awesome, that we want to blog so everyone can learn

The layout is not responsive and can't be read properly on mobile devices.

TODOs

• Add "meta"-Tag for "viewport"
• Improve section "AOE People"
• Improve section "AOE Articles"
• Improve Footer
• Improve Detail Page

https://tailwindcss.com/docs/typography-plugin

The Day and Month value of dates on posting detail page are mixed up.
Example: https://opensource.aoe.com/posts/ and https://opensource.aoe.com/posts/should-you-upgrade-to-web3/ - on the detail page we have 2022-12-03, while on the listing page we have 2022-03-12. The correct value for both is 2022-03-12.

We want a sub-page to feature Flamingo and Flamingo-related projects.

• Create a sub page
• Write some Flamingo content
• Add a list of featured Flamingo Repositories/Projects

Define a cache policy for static content.

Needs investigation into the github hosted pages.