UX is definitely not my strong suit so please guide me to have something usable

I will check more tonight, but looks good 👍
Maybe you could add a few more advanced parameters, which otherwise might prevent the feed from being added (e.g. timeout, SSL):

Furthermore, maybe we should have a checkbox for adding #force_feed

There is a minor layout glitch in at least one theme:

If you want feedback, here is mine, as the original issue creator.

I like the dedicated "Add a feed" page. 🙂
The option to create a new category directly from this page is not necessary in my opinion, bu it's really not a problem.

I find the "Subscription management" page a bit misleading now, because the only action is the creation of a category, which is rarely used.
It's also immediately under the "Subscription management" header, and not clearly separated from the feeds. (It was in some kind of titled box before. Did you change that because it was taking too much space?)

• Maybe add a link/button to the feed creation page? Or maybe even a simple line of text indicating there is a dedicated page to subscribe to a feed? (I know it's also in the left menu, but I think it would help to see it on the page, especially for long time user that expect to find the feed subscription button here)
• Maybe add a legend or some kind of header to the category creation? I think it would be better to have something like "Add/Create a new category" instead of just the watermark in an isolated text input. It could stay all on one like if you think it's better.
• Maybe add some kind of separation (a simple <hr/> ?) between the new category input and the feeds list.

Sorry for the lengthy feedback. I might be a bit too nit-picking, but it could be the only chance I get in 5 years, so I hope you forgive me. 😀

Thank you for your work.

@Alkarex I do not have this problem on my machine. I am using FF on Arch. Even on smaller screens, there is no such thing.
I do not want to include more fields since they are not required to work. Basically, I've only moved the original form in its own page. This new page is only meant to add the feed. Once it's done, you are automatically redirected to its configuration where you can tweak the feed configuration.

@mlaily I hear you. I've moved the category creation in the feed creation page where I've separated the 2 forms. I've also renamed the page to show that there is one page to create the elements.
I've also added a small information box containing a link to the new page.

I like your changes.

Something seems broken when adding a feed though.

172.17.0.1 - - [02/Jun/2020:19:14:25 +0000] "GET /i/?c=subscription&a=add HTTP/1.1" 200 2672 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0"
[Tue Jun 02 19:14:34.139830 2020] [php7:notice] [pid 18] [client 172.17.0.1:41786] PHP Notice:  Undefined variable: Minz_Request in /var/www/FreshRSS/app/Controllers/feedController.php on line 166
[Tue Jun 02 19:14:34.139936 2020] [php7:error] [pid 18] [client 172.17.0.1:41786] PHP Fatal error:  Uncaught Error: Class name must be a valid object or a string in /var/www/FreshRSS/app/Controllers/feedController.php:166\nStack trace:\n#0 /var/www/FreshRSS/lib/Minz/Dispatcher.php(119): FreshRSS_feed_Controller->addAction()\n#1 /var/www/FreshRSS/lib/Minz/Dispatcher.php(47): Minz_Dispatcher->launchAction('addAction')\n#2 /var/www/FreshRSS/lib/Minz/FrontController.php(84): Minz_Dispatcher->run()\n#3 /var/www/FreshRSS/p/i/index.php(48): Minz_FrontController->run()\n#4 {main}\n  thrown in /var/www/FreshRSS/app/Controllers/feedController.php on line 166
172.17.0.1 - - [02/Jun/2020:19:14:33 +0000] "POST /i/?c=feed&a=add HTTP/1.1" 200 336 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0"

Thank you. I'll look at it

@mlaily it's fixed.

I did some more testing.

As I said, I like it like that. The only thing I find strange is that validation (popup messages for an invalid url, an empty category name...) is done on the subscriptions page, and not the page where the inputs are now...

Good catch! I didn't noticed before. I'll look into it

@mlaily it's fixed!

That was quick! :) Everything looks fine by me.

@aledeg For the layout bug, try with Pafat theme in English.

or Blue Lagoon

To solve the bug and simplify the UI, I think you could consider dropping one of the icons (e.g. the one for import/export, and keep only the one to add a new feed).

For the additional fields, it can also wait for another PR, because it is not something we have now anyway. The reason for exposing timeout and SSL (and #force_feed) at subscription time is that otherwise it is not possible to add a feed that needs those parameters without changing global parameters, because adding the feed will fail before allowing the user to change those parameters.

See this example of feed that takes 30s to load http://test.alapetite.fr/slow.rss.xml.php and try to add it to FreshRSS (which, by default, has 15s timeout)

Minor: Maybe "Add" instead of "Create" for the button label:

(It took be a couple of seconds to understand where I should click to proceed with adding the feed)

@Alkarex I've removed the import button and change the action button text. For the other fields, I'll rework it when they are available.

@aledeg The other fields are already available, but currently only from a feed configuration page (so we have the text, parameters, etc.)

Ok, I'll look into it tomorrow.

@Alkarex I've added timeout and ssl. I could not find the force option.

The feed attributes were not applied / used before loading. Fixed by 52ba7ff

@marienfressinaud Do you want to have a look at the new UI?

I don't have a lot of time this week to spend on the review but it's a nice improvement and I trust you for the rest of the review :)

@marienfressinaud the idea is to keep the layout from the add page and the layout from the update panel with the same fields and headers organization. For sure, the add page is a skimmed version of the update page but I find that hiding elements will be counter-intuitive.