Maybe/app/views/layouts/issues.html.erb

<%= render "layouts/shared/htmldoc" do %>
  <%= drawer do %>
    <article class="prose">
      <%= tag.h2 do %>
        <%= yield :title %>
      <% end %>

      <%= tag.h3 "Issue Description" %>
      <%= yield :description %>

      <%= tag.h3 "How to fix this issue" %>
      <%= yield :action %>
    </article>
  <% end %>
<% end %>
New Design System + Codebase Refresh (#1823) Since the very first 0.1.0-alpha.1 release, we've been moving quickly to add new features to the Maybe app. In doing so, some parts of the codebase have become outdated, unnecessary, or overly-complex as a natural result of this feature prioritization. Now that "core" Maybe is complete, we're moving into a second phase of development where we'll be working hard to improve the accuracy of existing features and build additional features on top of "core". This PR is a quick overhaul of the existing codebase aimed to: - Establish the brand new and simplified dashboard view (pictured above) - Establish and move towards the conventions introduced in Cursor rules and project design overview #1788 - Consolidate layouts and improve the performance of layout queries - Organize the core models of the Maybe domain (i.e. Account::Entry, Account::Transaction, etc.) and break out specific traits of each model into dedicated concerns for better readability - Remove stale / dead code from codebase - Remove overly complex code paths in favor of simpler ones 2025-02-21 11:57:59 -05:00			`<%= render "layouts/shared/htmldoc" do %>`
			`<%= drawer do %>`
			`<article class="prose">`
			`<%= tag.h2 do %>`
			`<%= yield :title %>`
			`<% end %>`
Account Issue Model and Resolution Flow + Troubleshooting guides (#1090) * Rough draft of issue system * Simplify design * Remove stale files from merge conflicts * STI for issues * Cleanup * Improve Synth api key flow * Stub api key for test 2024-08-16 12:13:48 -04:00
New Design System + Codebase Refresh (#1823) Since the very first 0.1.0-alpha.1 release, we've been moving quickly to add new features to the Maybe app. In doing so, some parts of the codebase have become outdated, unnecessary, or overly-complex as a natural result of this feature prioritization. Now that "core" Maybe is complete, we're moving into a second phase of development where we'll be working hard to improve the accuracy of existing features and build additional features on top of "core". This PR is a quick overhaul of the existing codebase aimed to: - Establish the brand new and simplified dashboard view (pictured above) - Establish and move towards the conventions introduced in Cursor rules and project design overview #1788 - Consolidate layouts and improve the performance of layout queries - Organize the core models of the Maybe domain (i.e. Account::Entry, Account::Transaction, etc.) and break out specific traits of each model into dedicated concerns for better readability - Remove stale / dead code from codebase - Remove overly complex code paths in favor of simpler ones 2025-02-21 11:57:59 -05:00			`<%= tag.h3 "Issue Description" %>`
			`<%= yield :description %>`
Account Issue Model and Resolution Flow + Troubleshooting guides (#1090) * Rough draft of issue system * Simplify design * Remove stale files from merge conflicts * STI for issues * Cleanup * Improve Synth api key flow * Stub api key for test 2024-08-16 12:13:48 -04:00
New Design System + Codebase Refresh (#1823) Since the very first 0.1.0-alpha.1 release, we've been moving quickly to add new features to the Maybe app. In doing so, some parts of the codebase have become outdated, unnecessary, or overly-complex as a natural result of this feature prioritization. Now that "core" Maybe is complete, we're moving into a second phase of development where we'll be working hard to improve the accuracy of existing features and build additional features on top of "core". This PR is a quick overhaul of the existing codebase aimed to: - Establish the brand new and simplified dashboard view (pictured above) - Establish and move towards the conventions introduced in Cursor rules and project design overview #1788 - Consolidate layouts and improve the performance of layout queries - Organize the core models of the Maybe domain (i.e. Account::Entry, Account::Transaction, etc.) and break out specific traits of each model into dedicated concerns for better readability - Remove stale / dead code from codebase - Remove overly complex code paths in favor of simpler ones 2025-02-21 11:57:59 -05:00			`<%= tag.h3 "How to fix this issue" %>`
			`<%= yield :action %>`
			`</article>`
			`<% end %>`
Account Issue Model and Resolution Flow + Troubleshooting guides (#1090) * Rough draft of issue system * Simplify design * Remove stale files from merge conflicts * STI for issues * Cleanup * Improve Synth api key flow * Stub api key for test 2024-08-16 12:13:48 -04:00			`<% end %>`