Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Minimalist Portfolio - 11ty, SCSS, progressive enhancement

P
Dave•5,295
@dwhenson
A solution to the Minimalist portfolio website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


UPDATE:

Fixed some issues that were bothering me on this one. i) Fixed the textarea issue below - I had created in input with the type textarea - only took me a couple of hours to work that one out! 🤦‍♂️

ii) Fixed the project title not appearing in the title on each project page. Some hectic delving into 11tys pagination object was involved...

iii) Linked up all my other FEM projects so that each project actually links to a FEM project I did - just for fun... Only bookmark challenge remains outstanding.

Again, any feedback most welcome

Thanks

I learnt a lot about 11ty on this project. I used collections and pagination for the first time. It was difficult but I can see this being very useful. I think I could have hard coded this in about half the time, but making edits to this site is now a real breeze thanks to 11ty and nunjunks templating.

Using 11ty's pagination feature (and collections), adding projects from a markdown file updates the portfolio page and the pagination links and text automatically. I also inlined my CSS to improve performance. I split my CSS into 'critical', which appears on every page, and other page specific CSS is inlined on each page

I would very much welcome advice on the following issues:

Regarding 11ty, I spent a lot of time working out pagination. I thought that content that I put below the last --- in my .md files would appear in the template I referenced. This didn't happen. I suspect something to do with 11ty's data cascade, but I haven't understood what was happening yet.

One thing that has driven me crazy is styling the textarea on the form. I would like the text to wrap, at the moment it just carries on on one line, and I would like to user inputted text to start at the top (in the same location as the placeholder text). I moved the placeholder text, but cannot get the user text to start where I want it to.

Any other advice and suggestions would be gratefully received. Thanks!

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 Dave'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.