User Story:
As a frequent user of our platform, I want the option to view the customer panel of the payment provider for transparency and control over my subscription.

Acceptance Criteria:

• Users should have access to a customer panel provided by the payment provider.
• Users should be able to manage their subscription within the payment provider's panel, including canceling or modifying their subscription.

Additional Context:

Use of Stripe's billing customer panel. https://stripe.com/blog/billing-customer-portal

Related Issues/PRs (if applicable):

• #255

User Story:
As a frequent user of our platform, I want to see different package options prominently displayed on the landing page so that I can easily compare and choose the subscription plan that best suits my needs.

Acceptance Criteria:

• The landing page should feature a section displaying various subscription package options.
• Each package option should be clearly described with details about features, benefits, and pricing.

Related Issues/PRs (if applicable):

• #255

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• Lock file maintenance

Detected dependencies

asdf

.tool-versions

• ruby 3.3.5
• bun 1.1.29

bun

package.json

• @fortawesome/fontawesome-free 6.6.0
• @hotwired/stimulus 3.2.2
• @hotwired/turbo-rails 8.0.10
• @tailwindcss/typography 0.5.15
• autoprefixer 10.4.20
• daisyui 4.12.10
• postcss 8.4.47
• tailwindcss 3.4.13
• standard 17.1.2
• stylelint 16.9.0
• stylelint-config-standard-scss 13.1.0

bundler

Gemfile

• ruby 3.3.5
• rails '7.2.1'
• propshaft '1.0.0'
• pg '1.5.8'
• puma '6.4.3'
• jsbundling-rails '1.3.1'
• turbo-rails '2.0.10'
• stimulus-rails '1.3.4'
• cssbundling-rails '1.4.1'
• redis '5.3.0'
• tzinfo-data '1.2024.2'
• bootsnap '1.18.4'
• debug '1.9.2'
• factory_bot_rails '6.4.3'
• rspec-rails '7.0.1'
• web-console '4.2.1'
• listen '3.9.0'
• lookbook '2.3.2'
• annotate '3.2.0'
• brakeman '6.2.1'
• database_consistency '1.7.25'
• haml_lint '0.58.0'
• i18n-tasks '1.0.14'
• rubocop '1.66.1'
• rubocop-capybara '2.21.0'
• rubocop-factory_bot '2.26.1'
• rubocop-performance '1.22.1'
• rubocop-rails '2.26.2'
• rubocop-rspec '3.0.5'
• rubocop-rspec_rails '2.30.0'
• capybara '3.40.0'
• database_cleaner-active_record '2.2.0'
• faker '3.4.2'
• fuubar '2.5.1'
• selenium-webdriver '4.25.0'
• shoulda-matchers '6.4.0'
• simplecov '0.22.0'
• simplecov-cobertura '2.1.0'
• active_record_doctor '1.15.0'
• active_storage_validations '1.2.0'
• ahoy_matey '5.2.0'
• blazer '3.0.4'
• config '5.5.2'
• devise '4.9.4'
• dry-validation '1.10.0'
• goldiloader '5.3.1'
• good_job '4.3.0'
• haml-rails '2.1.0'
• omniauth '2.1.2'
• omniauth-google-oauth2 '1.2.0'
• omniauth-rails_csrf_protection '1.0.2'
• pay '7.3.0'
• pundit '2.4.0'
• rails-healthcheck '1.4.0'
• redcarpet '3.6.0'
• service_actor '3.9.3'
• service_actor-rails '1.0.0'
• stripe '12.6.0'
• valid_email2 '5.3.0'
• view_component '3.14.0'

docker-compose

docker-compose.dev.yml

• postgres 16.4-alpine
• redis 7.4.0-alpine

dockerfile

Dockerfile

• ruby 3.3.5-slim

github-actions

.github/workflows/build.yml

• docker/metadata-action v5
• docker/setup-qemu-action v3
• docker/setup-buildx-action v3
• docker/login-action v3
• docker/build-push-action v6

.github/workflows/lint.yml

• actions/checkout v4
• ruby/setup-ruby v1
• actions/checkout v4
• ruby/setup-ruby v1
• actions/checkout v4
• ruby/setup-ruby v1
• actions/checkout v4
• ruby/setup-ruby v1
• actions/checkout v4
• ruby/setup-ruby v1
• actions/checkout v4
• ruby/setup-ruby v1
• actions/checkout v4
• ruby/setup-ruby v1
• actions/checkout v4
• oven-sh/setup-bun v2
• actions/checkout v4
• oven-sh/setup-bun v2
• postgres 16.4-alpine
• postgres 16.4-alpine

.github/workflows/merge-gatekeeper.yml

• upsidr/merge-gatekeeper v1

.github/workflows/release-drafter.yml

• harm-matthias-harms/calendar-version v0
• release-drafter/release-drafter v6

.github/workflows/test.yml

• actions/checkout v4
• ruby/setup-ruby v1
• oven-sh/setup-bun v2
• codecov/codecov-action v4
• postgres 16.4-alpine

---

• Check this box to trigger a request for Renovate to run again on this repository

User Story:
As a frequent user of our platform, I want the option to subscribe to a premium membership plan so that I can access an enhanced set of features, receive exclusive benefits, and enjoy a seamless and uninterrupted experience.

Acceptance Criteria:

• #256
• #257
• #258
• #259

User Story:
As a potential customer, I want to easily access information about a specific feature on the landing page to better understand the product's capabilities and benefits.

Acceptance Criteria:

• A concise title and descriptive content are included to explain the feature's functionality and advantages.
• An image placeholder is associated to provide visual context.

User Story:
As a frequent user of our platform, I want to have the opportunity to test the product with a trial access before committing to a premium membership.

Acceptance Criteria:

• The platform should offer users the option to access a trial version of the product before subscribing.
• Once the trial period expires, users should be automatically enrolled into the selected premium subscription plan.

Related Issues/PRs (if applicable):

• #255

User Story:
As a website visitor, I want to see a captivating hero on the landing page to quickly understand the purpose of the website and be encouraged to explore further.

Acceptance Criteria:

• Placeholder for a headline and an informative subheadline
• A primary action button to encourage the user to test the product
• An image placeholder

User Story:
As a frequent user of our platform, I want the option to subscribe to a premium membership plan so that I can access an enhanced set of features, receive exclusive benefits, and enjoy a seamless and uninterrupted experience.

Acceptance Criteria:

• Users should be able to choose their desired premium plan and initiate the subscription process with clear instructions.

Additional Context:

The payments should be integrated with Stripe directly or over a payment gem, like https://github.com/pay-rails/pay

Related Issues/PRs (if applicable):

• #255