Remove old configuration form + New form for manual collection of the assertion/evidence

[tekrajchhetri]

Following our previous discussions, our goal was to offer users greater flexibility in configuring the UI components. The screenshot below showcases the initial implementation visible upon logging into the website. However, as we transition to a model-driven approach, this functionality is no longer relevant and will be phased out.

Another topic we discussed was the form for the manual collection of assertions and evidence. Here are a few questions to consider:

1. Should users be required to log in before accessing the form?
2. While we plan to align the form with the assertion/evidence model, are there any additional elements or features we should include on the form?

@satra @djarecka any suggestions?

[kabilar]

1. Should users be required to log in before accessing the form?

Yes, I think that any data being entered into the system should be associated with a registered user.

2. While we plan to align the form with the assertion/evidence model, are there any additional elements or features we should include on the form?

Where can I find the current assertion/evidence model?

[tekrajchhetri]

@kabilar the assertion/evidence model - https://brain-bican.github.io/models/index_assertion_evidence/