Skip to content

Update homepage#298

Merged
mickhansen merged 4 commits intomasterfrom
update-homepage
Mar 12, 2026
Merged

Update homepage#298
mickhansen merged 4 commits intomasterfrom
update-homepage

Conversation

@nmoskaleva
Copy link
Collaborator

@nmoskaleva nmoskaleva commented Mar 2, 2026

Replace generic description of Idura Verify and Idura Signatures with links to integration guides, eIDs and products the user is likely to look for when they're just getting started.

QA: https://deploy-preview-298--criipto-docs.netlify.app/

@netlify
Copy link

netlify bot commented Mar 2, 2026

Deploy Preview for criipto-docs ready!

Name Link
🔨 Latest commit eea1eef
🔍 Latest deploy log https://app.netlify.com/projects/criipto-docs/deploys/69b274240e1a160008935a08
😎 Deploy Preview https://deploy-preview-298--criipto-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@nmoskaleva nmoskaleva marked this pull request as ready for review March 10, 2026 22:02
@nmoskaleva nmoskaleva requested a review from jlndk March 11, 2026 13:46
Copy link
Contributor

@jlndk jlndk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks incredible!!!!

Just a few small comments but otherwise it LGTM

href={`/verify/e-ids/${eid.href}`}
logoSrc={eid.src}
logoWidth={eid.width}
logoHeight={eid.height}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of setting an explicit width / height for each img you could consider adding a container with a fixed size and let the logo fill that instead?

That was way we don't have to define an explicit size for every img

Copy link
Collaborator Author

@nmoskaleva nmoskaleva Mar 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Trinurt made logos in different sizes so they look good all together... I don't think container will work in this case?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Trinurt made logos in different sizes so they look good all together...

@nmoskaleva Consider a more sustainable solution going forward, having to involve an additional person each time we add a logo is not ideal.

Also if the logo were made with specific sizes why does it need to be defined? The image it self would already have the size.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, I might have exaggerated. There is a default size, though :)

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jlndk The logic behind the tech logos is the same as for the eID logos. We want them to appear the same size when used side by side.

Therefore the logo size is fixed AND (@nmoskaleva ) they are placed in a container with a fixed height (matching the max allowed logo height) and flex width. The logos are top/bottom centered in the container.

This image is from the design system:
image

Copy link

@Trinurt Trinurt Mar 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nmoskaleva The correct fixed height of the logo container is 44 px. Please note that all the square solid logos are 38x38 px - also Kotlin. (Currently you have them at 40x40 px).

Forgot to mention I think the page looks really good and addresses the top concerns we have identified for the target group spot on 🙌

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PS. @nmoskaleva If it is a help I can make a SVG version of the tech logos where they are already in a container with a fixed height? Let me know if you would like me to make that

import MitIDErhvervLogo from './logos/eids/mitid-erhverv.svg';
import PersonalausweisLogo from './logos/eids/personalausweis.svg';

const eids = [
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be preferable if one could NOT forget to add this when adding a page to Verify

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right. Are you suggesting there is a way to automate it? @mickhansen

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not necessarily automate but at least type guard. We can explore it in the future, not a blocker for this PR.

import React, { ReactElement } from 'react';
import { LogoCard } from '../components/LogoCard/LogoCard';

import Auth0Logo from './logos/integrations/auth0.svg';
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

File and component names look like they should be Verify specific.

@mickhansen
Copy link
Collaborator

Homepage should probably have a TOC when it has contents below the fold with multiple headlines

@nmoskaleva
Copy link
Collaborator Author

I have to run now, but will address the rest of the comments by EOD 😬

Will be used on the updated homepage for improved navigation and UX.
@nmoskaleva nmoskaleva force-pushed the update-homepage branch 2 times, most recently from 4d53d3b to f9c81c5 Compare March 12, 2026 00:25
@nmoskaleva
Copy link
Collaborator Author

Homepage should probably have a TOC when it has contents below the fold with multiple headlines

Great point about below-the-fold content. But I'm worried a ToC might just elongate the page and push the content even further down. Also, it might be worth discussing with UX. Could we revisit this when I'm back?

@mickhansen
Copy link
Collaborator

Great point about below-the-fold content. But I'm worried a ToC might just elongate the page and push the content even further down. Also, it might be worth discussing with UX. Could we revisit this when I'm back?

@nmoskaleva We have a generic TOC component already, in the right hand side navigation.

Will be used on the updated homepage to display a list of integrations and eIDs for improved navigation and UX.
@mickhansen mickhansen force-pushed the update-homepage branch 2 times, most recently from 92e7177 to 5065d2a Compare March 12, 2026 08:02
Copy link
Collaborator

@mickhansen mickhansen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given what a vast improvement this is, we will merge as is and address the rest of the comments/ideas when Natalia is back

nmoskaleva and others added 2 commits March 12, 2026 09:06
Replace existing generic description of Idura Verify and Idura Signatures with links to integration guides, eIDs and products the user is likely to look for when they're just getting started.
@mickhansen mickhansen merged commit 0458547 into master Mar 12, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants