(PR) Administrator : Redesign of the backoffice

[Soulou]

No description provided.

[Soulou]

PR Following #85

[Soulou]

Using the same kind of table as the countries, here is the elections panel :

(Of course coloured buttons are clickable ;-) )

[Soulou]

I'm currently working on the tags management part. I'm thinking to the internationalization. How do we handle that ? (database models and BO functionnalities)

[Soulou]

@barodeur @NebJ How do we must manage the tags, what I imagine:

A candidate must be able to choose among different tags. These tags are attached to a specific election from the admin backoffice ? (Candidates can't create their own tags ?)

[NebJ]

Correct @Soulou! The tree of tags is static for an election and is defined by the association "election_tags". So a candidacy can only add/edit/remove propositions for the existing tags. Let me know if it's understandable.

[Soulou]

Sorry @NebJ I haven't replied as fast as I must have done it. Yes it's completely understandable, I've done it this way.

[Soulou]

Here's my view to manage tags.

You can filter the view, '+' and '-' are here to add child tag and remove tag, it's completely working. Of course it's improvable, I'm only a JS beginner =)

[Soulou]

I assume there are only three levels from the root to the leaves, I'm not sure it's true but I think it is a good idea to keep things like that, it becomes really complex if the tree is deeper. (my interface doesn't allow 4th-level tags)

[Soulou]

I don't remember : why does a candidacy may have several candidates ?

[Soulou]

New view : candidates

[Soulou]

I think this feature can be merged in develop, then push on staging @barodeur @NebJ Are you ok with this ?

[NebJ]

Yep go for it and then ping @edschlum 👍

[Soulou]

ping @edschlum http://staging.voxe.org/new_admin

[edschlum]

Ok.

Just tried it. If I understand :

• there's nothing new here, except a FULL redesign on the server side, right ?
• it is still the view of the Admin. I haven't seen anything regarding the candidate part, right ?

I may have some ideas :

• I think the UI is not really convincing. For the admin part, the UI of the current BO in production is not too bad, it just has to be updated with the solutions to the problems that we met a lot of times : there was no confirmation status on anything we do on it, there's no flexibility, etc ..

But the UX (you know with the OSXpanel-like approach for the tags) was not that bad in terms of UX. I even would say, for an Admin, it was pretty good. Moreover, in the current admin, I can't add any pictures to the tags, I can't modify a tag, I can't move a tag...

What about the candidate side ? because these guys will be clients, so they need to have something easy and clear. They should be able to add proposals to the tags the admin has set for an election, with metadata and so on.

Tell me how we can help :)

[Soulou]

I completely agree on the point that there is nothing really new. One of the goal of this redesign is to be more accessible and maintainable. Because for the moment that's really difficult for someone to contribute without spending a huge amount of time.

Everything is not complete please open an issue per functionality. That's true that drag'n drop would be welcomed for instance.

The candidate side is on /backoffice, there's no link from the front end for the moment, because @barodeur is switching the technology of it. A candidate is able to add its propositions, we'll show you later. (In the train for Paris)

Edourd Schlumberger [email protected] a écrit :

Ok.

Just tried it. If I understand :

there's nothing new here, except a FULL redesign on the server side, right ? it is still the view of the Admin. I haven't seen anything regarding the candidate part, right ?

I may have some ideas :

I think the UI is not really convincing. For the admin part, the UI of the current BO in production is not too bad, it just has to be updated with the solutions to the problems that we met a lot of times : there was no confirmation status on anything we do on it, there's no flexibility, etc ..

But the UX (you know with the OSXpanel-like approach for the tags) was not that bad in terms of UX. I even would say, for an Admin, it was pretty good. Moreover, in the current admin, I can't add any pictures to the tags, I can't modify a tag, I can't move a tag...

What about the candidate side ? because these guys will be clients, so they need to have something easy and clear. They should be able to add proposals to the tags the admin has set for an election, with metadata and so on.

Tell me how we can help :)

—
Reply to this email directly or view it on GitHub.