haml | HTML Abstraction Markup Language - A Markup Haiku

If I'm understanding the structure properly, it sounds like you would want to do something like the following:

• This could be used by any page.
• This would require the following query parameters:
  • id the photo's ID to delete by.
  • redirect where to redirect the user after the action is completed.

Now there will only be 1 route to handle the controller above.

For rendering a collection of images with a redirect url that allows you to set the following state for the partial:

• photos a collection of images to render.
• redirect_url this is passed as a query parameter to the centralized delete image controller.

This should be able to DRY up your implementation. Currently the only thing I see that couples the view with the deletion is the redirect URL. By abstracting that out and moving that essentially to a parameter for the partial will allow for re-use and flexibility.

You've already identified your coupling via @VARIABLE, here's a quick mock of how I would expect it to end up looking like:

You have the member download_qr action based on your output from rails routes. It means that you need to specify the plot instance :id for which you want to download the QR code /plots/:id/download_qr; see Rails guides for more information about member and collection routes.

Taking this into account, you need to add the :id parameter to your link_to as

I would nest the route:

I am not familiar with HAML but I expect that the content that depends on the if condition needs to be indented and would therefore try:

The application.html.erb file is the template for the whole Rails application. Alchemy pages have their own templates per page_layout stored in the app/views/alchemy/page_layouts folder.

Please read the guideline on how to create a page layouts and templates

https://guides.alchemy-cms.com/pages.html#page-templates

EDIT:

You are able to set the layout used in the admin page edit preview with the admin_page_preview_layout setting in the config/alchemy/config.yml.

https://github.com/AlchemyCMS/alchemy_cms/blob/main/config/alchemy/config.yml#L205

As nobody answered me (I'm very sad !), I didn't stop to search a method to make a comment in HAML file for Ruby, and I found something interesting : Just declare a line as Ruby code (with -) and add your comment in Ruby !

Example:

You can interpolate the variable with #{my_color}:

Just tell Capybara what you expect it to find on the page and maximum time to wait for that to appear. In your question you say that you're expecting the button to change from "Count" to "Edit" but then your code is checking for "Loose Count" so I'm not fully clear on exactly what visible change you're expecting, but assuming the latter you could just do something like