How award-winning sites are made: Torque Editions panning layout

Поділитися
Вставка
  • Опубліковано 26 гру 2024

КОМЕНТАРІ • 12

  • @atmx659
    @atmx659 Рік тому +5

    Thank you! Its very easy to learn with you, highly appreciate your work

    • @SuperHi
      @SuperHi  Рік тому

      You are welcome! Always open to requests for future vids too if there's anything you'd like me to cover?

  • @bingobongo5855
    @bingobongo5855 Рік тому +1

    once again awesome tutorial!
    i was wondering how we could match the image container () widths and heights to match different sized images (like if I have both landscape and portrait ones)?
    i also notice if I change the number of grid items, the containers become huge. what do I need to change?

    • @SuperHi
      @SuperHi  Рік тому +3

      Thank you! For the different images, you can use align-items: center (or start) on the container where you're adding display: grid;
      For the grid items, it really depends on the layout you're going for, be it making the items smaller, grid wider/taller or using a different layout.
      Options would be to make the images have a fixed height and/or width so they don't get too big, changing the grid-template-columns to fit more in or potentially not using a grid and instead using a flexbox or absolute positioning (which is what the Torque site uses!)

  • @hellothere8547
    @hellothere8547 Рік тому +1

    Brilliant video! What CMS would you recommend for static sites?

    • @SuperHi
      @SuperHi  Рік тому +3

      Generally I've found that for 75% of sites it's fine to just made the content in the HTML... it's cheaper to update content periodically than build a whole CMS around everything! If it's for a client, it really depends on the content and amount of moderation/features... the more custom the content, the more likely I'd build something from scratch using something like Next.js. If it was e-commerce, Shopify. If it were fairly straight forward, something like Contentful or Sanity would be a good choice, but generally I wouldn't build a CMS unless if content was being updated a few times a month.