Change Details

As a **Engineer** i want to break our current parser by functionality. I expect to have two parsers, current and structured contents one, where functionality will be bound to the use case itself and both can have their different lifecycles. **Acceptance Criteria** * Repo created with the necessary code for Structured Contents **TODO** [ ] Review Structured Contents Main API code [ ] Create a repository for the new code [ ] Copy code adn unit tests, without removing, from parser to structured contents for: [ ] Infobox [ ] Sections

As a **Engineer** i want to break our current parser by functionality. I expect to have two parsers, current and structured contents one, where functionality will be bound to the use case itself and both can have their different lifecycles. **Acceptance Criteria** * Repo created with the necessary code for Structured Contents **TODO** [ ] Review Structured Contents Main API code [ ] Create a repository for the new code [ ] Copy code adn unit tests, without removing, from parser to structured contents for: [ ] Infobox [ ] Sections **Do not delete the branches** Demo ticket

As a **Engineer** i want to break our current parser by functionality. I expect to have two parsers, current and structured contents one, where functionality will be bound to the use case itself and both can have their different lifecycles. **Acceptance Criteria** * Repo created with the necessary code for Structured Contents **TODO** [ ] Review Structured Contents Main API code [ ] Create a repository for the new code [ ] Copy code adn unit tests, without removing, from parser to structured contents for: [ ] Infobox [ ] Sections **Do not delete the branches** Demo ticket