add a listing of the user's presentations

[jberger]

Note that this was not possible when using the routing defined in a94b60c0f43bf0a840066957d8f7d4a1a16684b4 thus I have had to revert it in the best way I understand.

[jberger]

I think the solution to a94b60c0f43bf0a840066957d8f7d4a1a16684b4 is not to nest users under a conference (which we specifically discussed not doing) but rather to define a "current_conference" attribute on the app or some such. It could be detected (we already have that logic) or defined in the configuration (probably best).

Anyway I'm assigning it to you @jhthorsen , please take a look.

[jhthorsen]

I think we need to discuss this further on IRC, but I don't think the initial idea about having "/user/profile" will work. The reason why I think "/user/...." is a bad idea is that it's hard to connect the profile page to the conference you're looking at. I see that you suggest using "current_conference" (fetching the "current" conference from the database). The issue is that I don't think this will work for the next conference:

• A user visits http://mct.com/puppy-conference/ and register. All works nicely.
• A couple of months later, the same user register for http://mct.com/mojoconf2015
• The user is redirected to /user/profile, but where will the links in the navbar take the user? To puppy conference or mojoconf2015? And also, which theme will be used? puppy- or mojo-theme?

On the other hand, if we have /:cid/profile the user will still move between the same conference pages. Also, I'm suggesting the profile page has links to the other conferences that is known by the system, so you can move between the pages.

I know, right now this doesn't make much sense, but it's the only thing that makes sense (imo) regarding the data model we decided on, where we have global users and global conferences.

I'm suggesting these routes:

• GET / Redirects to the lastest conference. We can make this more clever later on by adding "domain" to the mix, so puppy-conference.com and mojoconf.com can have difference redirects.
• GET /:cid/ (cid = conference ID = mojoconf, puppy-conference, ...) Will display the main conference landing page
• GET /:cid/presentations Show the presentations for the given conference.
• GET /:cid/presentations/:url_name Show one specific presentation. This page can also have an edit button, if the logged in user owns the presentation.
• GET /:cid/profile Display the profile page for a user, where you can jump to submitted talks and other conferences in the system.
• GET /:cid/profile/presentations Show the presentations for a user. We can sort the conferences so we first have one table with the presentations for the current conference, and then (optionally) for all the other conferences. This page could also show a form for submitting a new presentation.
• POST /:cid/profile/presentations Create a new presentation.
• GET/POST /:cid/profile/presentations/:url_name/edit Edit a presentation.

(I think I've covered all the routes now)

[jberger]

First of all, the server is already doing a redirect of / to /<<current_conference>> so I'm not sure what's so hard about having there be an app default of current_conference. If there is a difficulty, it still isn't that hard since they will reach the login page via a specific conference's site, so the act of coming from that site can put a value in the session about which conference they are referring to.

Second, once /:cid is removed from the route, the resulting route GET/POST /user/profile/presentations/:url_name/edit Edit a presentation. will not be sufficient. Presentation url_names are not unique wrt the user and indeed many people give the same talk at multiple conferences.

[jberger]

Personally I don't think there should be a "submit a presentation" action under the user's profile page. As @jhthorsen suggests this is ambiguous, but why is it ambiguous? Because they are unrelated. You should submit a presentation from the conference page.

Links and styling can come either noting the originating site or the server's default conference.

[jberger]

After discussion on IRC, and seeing that ACT does /:cid/user/profile etc I will relent. I'm still not 100% convinced, but it does mean that lots of people disagree with me.

[jhthorsen]

I agree that a talk should be submitted from /:cid/presentations, and has nothing to do with the profile. The main point here is that I want /:cid/ in front of the routes, so don't change conferences or themeing on "random".

I do think /:cid/profile/presentations is a good idea. I'm also fine by replacing "profile" with "user".

[jhthorsen]

What do you think @jberger ?