You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just made a blocker event for the next hackathon. Due to the requirement to have a wiki page for every event, this was way more involved than it should have been.
Hackathon pages are usually created by copy+pasting previous hackathon pages and then editing stuff. I didn't want to create an empty page lest people add something to it that needs to be merged into the proper page later. But since we're not sure yet sure about dates and stuff, I wasn't about to edit the whole thing. So now, our wiki contains a page with mostly wrong data, and a bold notice on the top that the data is wrong.
Even without my self-imposed decision to put content into the page, it was just super annoying. Instead of being
login to mos
fill out event form
my workflow was
login to mos
fill out event form
realize that I need a wiki page
open the wiki
try to create the page
realize I wasn't logged in to the wiki
remember my wiki password after a few tries
login to the wiki
create the page
go back to the event form
Not to mention fishing my wiki page changes out of the developer console because of CSRF protection (or sth), and because I logged in in a different tab.
Personally, I was against the wiki page validation change for this reason. I don't like this workflow in general - for me, blocking time in the calendar comes first. Once I have a timeslot, I can plan around availability of things/people at that time, and make a page accordingly.
I also strongly prefer the "make an event, click the event to get to the wiki 404 page that offers you to create the page, create the page" workflow to the "create the page, then hope you don't have a typo when you put the page name in the event creation form" workflow.
I understand that some people like to make pages first, and the validation guards against people having typos in wiki pages, but there should be an "I know what I'm doing, let me create the event without a wiki page" escape hatch.
My proposal would be a checkbox that gets hidden by JS when the page loads, and unhidden when that validation message appears. Or to just revert the validation, and look for other ways to make typos in wiki page links obvious, like displaying them differently in the calendar or sth. Or have suggestions while typing the wiki page name instead of validation.
The text was updated successfully, but these errors were encountered:
I just made a blocker event for the next hackathon. Due to the requirement to have a wiki page for every event, this was way more involved than it should have been.
Hackathon pages are usually created by copy+pasting previous hackathon pages and then editing stuff. I didn't want to create an empty page lest people add something to it that needs to be merged into the proper page later. But since we're not sure yet sure about dates and stuff, I wasn't about to edit the whole thing. So now, our wiki contains a page with mostly wrong data, and a bold notice on the top that the data is wrong.
Even without my self-imposed decision to put content into the page, it was just super annoying. Instead of being
my workflow was
Not to mention fishing my wiki page changes out of the developer console because of CSRF protection (or sth), and because I logged in in a different tab.
Personally, I was against the wiki page validation change for this reason. I don't like this workflow in general - for me, blocking time in the calendar comes first. Once I have a timeslot, I can plan around availability of things/people at that time, and make a page accordingly.
I also strongly prefer the "make an event, click the event to get to the wiki 404 page that offers you to create the page, create the page" workflow to the "create the page, then hope you don't have a typo when you put the page name in the event creation form" workflow.
I understand that some people like to make pages first, and the validation guards against people having typos in wiki pages, but there should be an "I know what I'm doing, let me create the event without a wiki page" escape hatch.
My proposal would be a checkbox that gets hidden by JS when the page loads, and unhidden when that validation message appears. Or to just revert the validation, and look for other ways to make typos in wiki page links obvious, like displaying them differently in the calendar or sth. Or have suggestions while typing the wiki page name instead of validation.
The text was updated successfully, but these errors were encountered: