-
Notifications
You must be signed in to change notification settings - Fork 670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sponsor info #201
Sponsor info #201
Conversation
I think this is fair and clear. |
Devopsdays events aren't your standard trade show, so you won't be shipping your booth. Most events have sponsorships available that come with a simple six-foot table and a couple of chairs. | ||
|
||
Typical sponsor packing list: | ||
<ul> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might we prefer using Markdown instead of HTML? This being a specific case, yes, but I suppose it's a larger question of internal policy as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that using MD as much as possible is preferred.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I've added top-level nav for this info. (Yes, I know, this is heading in the direction of site redesign, but I field these questions multiple times a week and would like the answers to surface more naturally, pretty much now.) Input welcome (particularly from @mattstratton re: the nav change). |
I definitely am in favor of the nav change. I think it fits with the rest of the design. |
af361cc
to
0b2b8bb
Compare
Sponsor info Former-commit-id: 98d0a4b
Sponsor info Former-commit-id: 98d0a4b
Sponsor info Former-commit-id: 98d0a4b
This is the beginning of some general sponsor info for #85. Comments welcome.