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
{{ message }}
This repository has been archived by the owner on Jul 21, 2019. It is now read-only.
The tricky thing about this is that event_link is a shortcode whose purpose is to link to internal pages.
I propose instead adding a new shortcode for cfp_link which will link to the appropriate value for the proposal page for the event, depending on if there is an offsite cpf_link, etc. We could also add a registration_link shortcode.
I think that might be less confusing. Use case example - for Chicago, we have an offsite proposal link for the menu to use, but we still have a "propose" page, and I might want to link to it. event_link is specific for generating links internally, you know?
I agree with @mattstratton that a fair number of events use the local "propose" page to explain things and then point people to their offsite CFP link. Offsite CFP links can vary so much that it doesn't make sense to assume the link will suffice for all desired explanations.
Expected behavior
When adding an outside URL to
cfp_link
in the event's yml file I expectevent_link page="propose"
to use it.Actual behavior
event_link
uses internal propose pageThe text was updated successfully, but these errors were encountered: