impress/app/views/outfits/edit.html.haml

- title(@outfit.name || t('.default_outfit_name'))
- if @outfit
  - open_graph type: 'openneo-impress:outfit', title: yield(:title),
    url: outfit_url(@outfit)
  - if @outfit.image?
    - open_graph image: absolute_url(@outfit.image.url)

!!! 5
%html
  %head
    %meta{charset: 'utf-8'}
    %meta{name: 'viewport', content: 'width=device-width, initial-scale=1'}
    %title
      - if content_for? :title
        = yield :title
        | #{t 'app_name'}
    %link{href: image_path('favicon.png'), rel: 'icon'}
    = stylesheet_link_tag 'fonts'
    = javascript_include_tag 'wardrobe-2020-page', defer: true
    = open_graph_tags
  %body
    #wardrobe-2020-root
Delete outfits/show page, point to the editor instead Now, like in DTI 2020, opening an outfit will go straight to the editor. I'm not 100% on whether this is actually like. the superior behavior? But I think it's good enough, and it's what the wardrobe-2020 code expects, so let's just roll with it for now! 2023-10-24 18:02:18 -07:00			`- title(@outfit.name \|\| t('.default_outfit_name'))`
			`- if @outfit`
			`- open_graph type: 'openneo-impress:outfit', title: yield(:title),`
			`url: outfit_url(@outfit)`
			`- if @outfit.image?`
			`- open_graph image: absolute_url(@outfit.image.url)`

Render wardrobe-2020 fullscreen Tada! No more layout! 2023-08-10 18:19:03 -07:00			`!!! 5`
			`%html`
			`%head`
			`%meta{charset: 'utf-8'}`
Add viewport meta tag to wardrobe page Oops, this was causing the page to render in a weird zoomed-out way on mobile! Note that, for most of the site, we intentionally haven't added this tag yet because most of our pages aren't especially responsively-designed; so we _want_ the device's best attempt to work with that, rather than trying to enforce something. 2023-10-12 14:39:37 -07:00			`%meta{name: 'viewport', content: 'width=device-width, initial-scale=1'}`
Delete outfits/show page, point to the editor instead Now, like in DTI 2020, opening an outfit will go straight to the editor. I'm not 100% on whether this is actually like. the superior behavior? But I think it's good enough, and it's what the wardrobe-2020 code expects, so let's just roll with it for now! 2023-10-24 18:02:18 -07:00			`%title`
			`- if content_for? :title`
			`= yield :title`
			`\| #{t 'app_name'}`
Render wardrobe-2020 fullscreen Tada! No more layout! 2023-08-10 18:19:03 -07:00			`%link{href: image_path('favicon.png'), rel: 'icon'}`
Fix typography on wardrobe 2020 page Add the green body color back in, and add the Delicious font! 2023-08-10 20:09:30 -07:00			`= stylesheet_link_tag 'fonts'`
Render wardrobe-2020 fullscreen Tada! No more layout! 2023-08-10 18:19:03 -07:00			`= javascript_include_tag 'wardrobe-2020-page', defer: true`
Delete outfits/show page, point to the editor instead Now, like in DTI 2020, opening an outfit will go straight to the editor. I'm not 100% on whether this is actually like. the superior behavior? But I think it's good enough, and it's what the wardrobe-2020 code expects, so let's just roll with it for now! 2023-10-24 18:02:18 -07:00			`= open_graph_tags`
Render wardrobe-2020 fullscreen Tada! No more layout! 2023-08-10 18:19:03 -07:00			`%body`
			`#wardrobe-2020-root`