/pheature-symfony-pre-example

POC about Pheature Flags Symfony bundle

Primary LanguagePHP

Pheature Driven Symfony Example

Welcome to our Symfony Toggle example, In this app we will explain how to use Pheature Flags library in an example ecommerce-like Symfony Web App.

In the following lines we will define the initial description of the ecommerce and also we will define a short of user-stories.

  • This is example app, every detail in the context, definition, and|or user-stories is fictional and created for learning purposes

Requirements

  • PHP >= 8.0
  • yarn
  • composer

Install

git clone git@github.com:kpicaza/pheature-symfony-pre-example.git
cd pheature-symfony-pre-example
git submodule update --init --recursive
composer update
yarn
yarn build
yarn run encore production
docker compose up --build -d
docker compose run php bin/console doctrine:migrations:migrate
docker compose run php bin/console app:create:admin # user: test@example.com, password: pheature

Open browser in http://127.0.0.1 you can see the website, or access to admin area in http://127.0.0.1/admin/login?role=developer

Context

We are going to build a small ecommerce website for a local amigurumi artisan.

To reduce the time to market, we will iterate over the program updating and adding the required use cases:

  1. First iteration:

We will build a landing page with a few requirements:

In that case we will use in-memory toggle implementation to use release toggles.

  • It should show the arstisan's logo.
  • It should show the artisans's commercial name.
  • It should show some amigurumi pictures.
  • It should show contact information.
  1. Second iteration:

In order, to make our website looks like a real e-commerce, the first we need is to create some kind of catalog.

The catalog should show a list of available products. To be able to show products the thing we need are the products itself. A product should have at least a name, picture, and price.

To create the products, we will need an authentication system for content editors, and an administration panel where manage the products.

  • It should have content editor users
  • It should have products
  • It should have a backoffice to add products
  • It should have a catalog that shows available products
  1. Third iteration