-
Notifications
You must be signed in to change notification settings - Fork 137
Improve workshop page UX by separating current status from history #2340
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
Open
Walpurga03
wants to merge
2
commits into
bitcoinops:master
Choose a base branch
from
Walpurga03:feature/workshop-history-toggle
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| <!-- | ||
| This include renders a collapsible <details> section. | ||
| Usage: Pass 'title' and 'content' as parameters. | ||
| --> | ||
| <details> | ||
| <summary><h2 style="display:inline">{{ include.title }}</h2></summary> | ||
| {{ include.content | markdownify }} | ||
| </details> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,66 @@ | ||
| --- | ||
| type: pages | ||
| layout: default | ||
| --- | ||
| <link rel="stylesheet" href="/assets/css/main.css"> | ||
|
|
||
| <div class="localization"> | ||
| <a href="/en/workshops/">en</a> | ||
| </div> | ||
|
|
||
| <h1 class="post-title">Workshops</h1> | ||
|
|
||
| {% if content != ""%} | ||
| <div class="post-content"> | ||
| {{ content }} | ||
| </div> | ||
| {%- endif -%} | ||
|
|
||
| <!-- Info: Show message if no workshops are currently scheduled --> | ||
| <p><strong>Currently, no workshops are scheduled. We are evaluating potential future workshop topics and formats based on community feedback and technical developments in the Bitcoin ecosystem.</strong></p> | ||
|
|
||
| <!-- Include: Show previous workshops in a collapsible section --> | ||
| {% include functions/details-list-workshops.md | ||
| title="Previous Workshops" | ||
| content=" | ||
| <div id='taproot-workshop'></div> | ||
| <h3>Workshops #3, #4 and #5 - Schnorr and Taproot Seminars</h3> | ||
| <ul> | ||
| <li>San Francisco, September 24 2019</li> | ||
| <li>New York, September 27 2019</li> | ||
| <li>London, February 5 2020</li> | ||
| </ul> | ||
| <p><em>Schnorr signatures</em> and <em>Taproot</em> are proposed changes to the Bitcoin protocol that promise greatly improved privacy, fungibility, scalability and functionality.</p> | ||
| <p>Bitcoin Optech hosted two seminar format workshops which included a mixture of presentations, coding exercises and discussions, and gave engineers at member companies an understanding of how these new technologies work and how they can be applied to their products and services. The workshops also provided engineers an opportunity to take part in the feedback process while these technologies are still in the proposal stage.</p> | ||
| <p><a href='/en/schorr-taproot-workshop/'>All material from the workshops</a> is available on this website, so engineers can learn about the schnorr/taproot proposals at home.</p> | ||
| <h3>Workshop #2 - Paris, November 12-13 2018</h3> | ||
| <p>Bitcoin Optech held our second roundtable workshop in Paris on November 12-13 2018. The format was the same as the first workshop in San Francisco.</p> | ||
| <p>In attendance were 24 engineers from Bitcoin companies and open source projects.</p> | ||
| <h4>Topics</h4> | ||
| <ul> | ||
| <li>Replace-by-fee vs. child-pays-for-parent as fee replacement techniques</li> | ||
| <li>Partially Signed Bitcoin Transactions (<a href='https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki'>BIP 174</a>)</li> | ||
| <li><a href='https://gist.github.com/sipa/e3d23d498c430bb601c5bca83523fa82'>Output script descriptors</a> for wallet interoperability</li> | ||
| <li>Lightning wallet integration and applications for exchanges</li> | ||
| <li>Approaches to coin selection & consolidation</li> | ||
| </ul> | ||
| <h4>Thanks</h4> | ||
| <p>Thanks to Ledger for hosting the workshop and helping with organization.</p> | ||
| <h3>Workshop #1 - San Francisco, July 17 2018</h3> | ||
| <p>Bitcoin Optech held our first roundtable workshop in San Francisco on July 17 2018:</p> | ||
| <ul> | ||
| <li>Topics were discussed in a roundtable format in which every participant had an equal opportunity to engage.</li> | ||
| <li>Each topic had a moderator and notetaker. The moderator was responsible for a brief introduction of a topic and keeping discussion on track and on time.</li> | ||
| <li>To make sure that participants were comfortable to speak freely, notes and action items were distributed to participants but not beyond. Participants were free to share discussion details internally at their companies and publicly, but did not attribute any particular statement to a given individual (Chatham House Rules).</li> | ||
| </ul> | ||
| <p>In attendance were 14 engineers from SF Bay Area Bitcoin companies and open source projects.</p> | ||
| <h4>Topics</h4> | ||
| <ul> | ||
| <li>Coin selection</li> | ||
| <li>Fee estimation, RBF, CPFP best practices</li> | ||
| <li>Optech community and communication</li> | ||
| </ul> | ||
| <h4>Thanks</h4> | ||
| <p>Thanks to Square for hosting the workshop and Coinbase for helping with organization.</p> | ||
| " | ||
| %} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 think the addition of the Current Status saying that we currently don’t plan any workshops is a great improvement. I don’t think the Previous Workshops section need to be hidden, it seems alright to me to just list them under a second section at the same level as Current Status, i.e.:
Current Status
Not planning anything at this time.
Previous Workshops
Workshop 3–5
Bla
Workshop 2
…
Could you explain why you think it would be better to hide the old workshops, @Walpurga03?
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.
In my view, displaying old workshops that happened long ago gives your website an outdated or neglected impression. A streamlined first impression with less but more current content often looks more professional and inviting.
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.
Im still share Murch's opinion of listening them under the current status as is without hiding