Open abangser opened 6 months ago
I am able to solve both problems locally on my laptop, and everything works as expected. However, when I deploy the application on Vercel, the page does not function as it does locally.
The application should function the same way on Vercel as it does when running locally.
The application on Vercel does not work as expected, despite working perfectly on my local machine.
Any guidance on resolving this discrepancy between the local and deployed environments would be greatly appreciated. Thank you!
Hey @Aditya-138-12 , do you have a branch I can pull down and see what you see when it comes to the diff?
Hi @abangser,
I've made the changes directly on the main branch of my forked repository. You can check out my fork and see the changes here:
Forked Repository: https://github.com/Aditya-138-12/Aditya-138-12-tag-app-delivery
Let me know if you need any further information or if there's anything else I can assist with.
Thank you! Aditya Saroha
Changes I have Made!!
Thanks so much @Aditya-138-12, I have just cloned locally and followed the readme and saw some things working great but other odd behaviour locally.
So I am curious on a couple of things:
Thanks again for working on this, it seems your changes have cracked the main issue we raised here, and I know we can iron out the other differences!
For debugging:
Hi @abangser
Thanks for cloning the repo and checking things out! I'm glad to hear that some parts are working well for you.
To answer your questions:
Deployment to Vercel: When I make a pull request on the repo, the deployment to Vercel is triggered automatically. I did raise a PR, but after noticing that the page was not working as expected with the changes made, I deleted the PR.
Behaviors on Vercel: On Vercel, subheaders are not linked, they are also invisible, the content becomes messed up, This might help identify if the oddities you are documenting match what I have seen.
If there's any specific part of the deployment process or behavior you'd like me to elaborate on, please let me know. I'm happy to help iron out these differences and get everything running smoothly!
Thanks again for your efforts and feedback. It's great to see progress on the main issue, and I'm confident we can resolve the remaining quirks together.
On the website we have a tab design.
This has been useful because we have a more web friendly view which differentiates from a single PDF.
However, it has created issues with anchor links to the tabs and within them.
Issue 1: URLs with anchors to the tabs do not actually open to the tabs
If you click on the table aspect
Investment
it will open the correct tab and change the URL tohttps://tag-app-delivery.cncf.io/whitepapers/platform-eng-maturity-model/#Interfaces
, however the page does not scroll to focus on the newly opened tab and should someone go directly to that link, the page opens from the top.Issue 2: Subheaders within the tabs do not anchor
Within the tabs there are anchor links (even have the 🔗 icon on them) for the subheaders. They are unique as they include both common info (e.g.
Level 1 - Provisional
) but also the unique descriptors (e.g.Level 1 - Provisional -- by request
for Operations).These also set the URL when the 🔗 is clicked on and it is copied for the user, but they remove the aspect details from the URL even if it was there. When these links are used directly, they do not open the right tab nor scroll to the right section.
This is a nice to have fix, and there is an option to just move back to a single long scroll page.