Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

Using AWS services and Vue.js

fetch, vue, node
Santiago Morales•370
@Aleroms
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am proud of the fact that this website uses AWS services such as AWS Cognito, Amplify, DynamoDB, Lambda and API Gateway. What I would do next time is have the username as key for Dynamo table because i messed up and my cognito key for access is email and so it f*cks up the table and sometimes if not done in the proper way it'll throw 403 forbidden error at me

What challenges did you encounter, and how did you overcome them?

well, it was hard to get cognito to work bcz the amplify doc didn't really help for vue, so i had to jerry-rigg and honestly my spagehtti code is only being help us by hopes-and-dreams. I couldn't get S3 to work properly so i removed that feature from the app - no file uploads. Lambda functions were hard cause I don't really know backend , i don't do Node. I am frontend guy in a lonely world. So I had to use ChatGPT most of the time and pray binary that the code would work.

What specific areas of your project would you like help with?

This project got me acting up bro. I swear, if you can get the app to work, bless up. I honestly just got tired of the project and want to walk away from it. At least, now, I can add super hot keywords to my resume.

W's in the chat.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Santiago Morales's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.