Skip to content

Add Full-Size Hackpad.V1 - #571

Merged
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main
Mar 13, 2025
Merged

Add Full-Size Hackpad.V1#571
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main

Conversation

@aryatajne28

Copy link
Copy Markdown
Contributor

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.

Check off the following to let the reviewers know you've done everything:
[X] I HAVE RAN DRC ON MY DESIGN WITH ZERO ERRORS (Silkscreen errors are okay)
[X] I HAVE BRANDED ALL MY PARTS (PCB, CASE) WITH MY HACKPAD'S NAME
[X] I HAVE MADE SURE MY 3D PRINTED PARTS DO NOT REQUIRE SUPPORTS (Text branding overhang is okay)
[X] I HAVE MADE SURE TO INCLUDE TOLERANCES (0.25mm)
[X] MY HACKPAD'S PCB IS UNDER 100mm x 100mm, I DO NOT HAVE MORE THAN 16X SWITCHES, 2X ROTARY ENCODERS, 1X OLED, 16X LEDS.
[X] IN MY FOLDER, THERE IS A README.MD FILE THAT CONTAINS THE FOLLOWING INFORMATION:

  • Full render including all the parts
  • A few sentences about the inspiration and challenges
  • BOM
  • Photos of the Schematic, PCB, and case

If you're unsure about the format, make sure to check out this example and follow the format there.

If this PR isn't a submission, that's okay too! Please remove the above boxes and explain what the pull request is for! If there's anything about this PR template that seems confusing, send a message in #hackpad in slack!

@vercel

vercelBot commented Feb 20, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

NameStatusPreviewCommentsUpdated (UTC)
hackpad✅ Ready (Inspect)Visit Preview💬 Add feedbackMar 13, 2025 0:32am

@Gamer153

Copy link
Copy Markdown
Contributor

Hey, you seem to have forgotten the pictures of the schematics and PCB, and I couldn't find a picture of the full assembled hackpad with all parts.

Also, a lot of the other approved requests have the images included as files directly, not through some Github link, so I think it'd be good if you add the pictures directly to your PR and README as files.

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thanks for this! On it right away!

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Hey @Gamer153, I have updated the images of the complete Hackpad and Schematic/PCB. I have added a folder of images separately, but while updating in README, it was still converting it into github links so I used CDN links from Slack. Hope this helps!

@Gamer153

Copy link
Copy Markdown
Contributor

Looks good!
Btw, if your image is in the repo on GitHub, you can add it directly in Markdown, and don't have to drag it in: e.g. for the pcb, instead of the link you could put this in your README: ![](img/PCB.png)

Also, according to this slack thread, you should put branding on everything if you're not printing it yourself.

@aryatajne28

aryatajne28 commented Mar 13, 2025

Copy link
Copy Markdown
ContributorAuthor

@Gamer153 I have updated the Branding on both of my Case parts as well as updated the Image links that way! Thanks for the heads up. Can you please check the README once, you will get the idea.

@Gamer153

Copy link
Copy Markdown
Contributor

I approve of this submission! Here's my own approved PR link: #443

@qcoralqcoral left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome job on this hackpad!! officially approved.!!!jhknfui842nf

fill out this form to get it:

https://forms.hackclub.com/hackpadv2

@qcoral
qcoral merged commit 6be5235 into hackclub:mainMar 13, 2025
@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thank you so much!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@aryatajne28@Gamer153@qcoral
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Add Full-Size Hackpad.V1 by aryatajne28 · Pull Request #571 · hackclub/hackpad · GitHub
Skip to content

Add Full-Size Hackpad.V1 - #571

Merged
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main
Mar 13, 2025
Merged

Add Full-Size Hackpad.V1#571
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main

Conversation

@aryatajne28

Copy link
Copy Markdown
Contributor

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.

Check off the following to let the reviewers know you've done everything:
[X] I HAVE RAN DRC ON MY DESIGN WITH ZERO ERRORS (Silkscreen errors are okay)
[X] I HAVE BRANDED ALL MY PARTS (PCB, CASE) WITH MY HACKPAD'S NAME
[X] I HAVE MADE SURE MY 3D PRINTED PARTS DO NOT REQUIRE SUPPORTS (Text branding overhang is okay)
[X] I HAVE MADE SURE TO INCLUDE TOLERANCES (0.25mm)
[X] MY HACKPAD'S PCB IS UNDER 100mm x 100mm, I DO NOT HAVE MORE THAN 16X SWITCHES, 2X ROTARY ENCODERS, 1X OLED, 16X LEDS.
[X] IN MY FOLDER, THERE IS A README.MD FILE THAT CONTAINS THE FOLLOWING INFORMATION:

  • Full render including all the parts
  • A few sentences about the inspiration and challenges
  • BOM
  • Photos of the Schematic, PCB, and case

If you're unsure about the format, make sure to check out this example and follow the format there.

If this PR isn't a submission, that's okay too! Please remove the above boxes and explain what the pull request is for! If there's anything about this PR template that seems confusing, send a message in #hackpad in slack!

@vercel

vercelBot commented Feb 20, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

NameStatusPreviewCommentsUpdated (UTC)
hackpad✅ Ready (Inspect)Visit Preview💬 Add feedbackMar 13, 2025 0:32am

@Gamer153

Copy link
Copy Markdown
Contributor

Hey, you seem to have forgotten the pictures of the schematics and PCB, and I couldn't find a picture of the full assembled hackpad with all parts.

Also, a lot of the other approved requests have the images included as files directly, not through some Github link, so I think it'd be good if you add the pictures directly to your PR and README as files.

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thanks for this! On it right away!

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Hey @Gamer153, I have updated the images of the complete Hackpad and Schematic/PCB. I have added a folder of images separately, but while updating in README, it was still converting it into github links so I used CDN links from Slack. Hope this helps!

@Gamer153

Copy link
Copy Markdown
Contributor

Looks good!
Btw, if your image is in the repo on GitHub, you can add it directly in Markdown, and don't have to drag it in: e.g. for the pcb, instead of the link you could put this in your README: ![](img/PCB.png)

Also, according to this slack thread, you should put branding on everything if you're not printing it yourself.

@aryatajne28

aryatajne28 commented Mar 13, 2025

Copy link
Copy Markdown
ContributorAuthor

@Gamer153 I have updated the Branding on both of my Case parts as well as updated the Image links that way! Thanks for the heads up. Can you please check the README once, you will get the idea.

@Gamer153

Copy link
Copy Markdown
Contributor

I approve of this submission! Here's my own approved PR link: #443

@qcoralqcoral left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome job on this hackpad!! officially approved.!!!jhknfui842nf

fill out this form to get it:

https://forms.hackclub.com/hackpadv2

@qcoral
qcoral merged commit 6be5235 into hackclub:mainMar 13, 2025
@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thank you so much!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@aryatajne28@Gamer153@qcoral
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add Full-Size Hackpad.V1 by aryatajne28 · Pull Request #571 · hackclub/hackpad · GitHub
Skip to content

Add Full-Size Hackpad.V1 - #571

Merged
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main
Mar 13, 2025
Merged

Add Full-Size Hackpad.V1#571
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main

Conversation

@aryatajne28

Copy link
Copy Markdown
Contributor

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.

Check off the following to let the reviewers know you've done everything:
[X] I HAVE RAN DRC ON MY DESIGN WITH ZERO ERRORS (Silkscreen errors are okay)
[X] I HAVE BRANDED ALL MY PARTS (PCB, CASE) WITH MY HACKPAD'S NAME
[X] I HAVE MADE SURE MY 3D PRINTED PARTS DO NOT REQUIRE SUPPORTS (Text branding overhang is okay)
[X] I HAVE MADE SURE TO INCLUDE TOLERANCES (0.25mm)
[X] MY HACKPAD'S PCB IS UNDER 100mm x 100mm, I DO NOT HAVE MORE THAN 16X SWITCHES, 2X ROTARY ENCODERS, 1X OLED, 16X LEDS.
[X] IN MY FOLDER, THERE IS A README.MD FILE THAT CONTAINS THE FOLLOWING INFORMATION:

  • Full render including all the parts
  • A few sentences about the inspiration and challenges
  • BOM
  • Photos of the Schematic, PCB, and case

If you're unsure about the format, make sure to check out this example and follow the format there.

If this PR isn't a submission, that's okay too! Please remove the above boxes and explain what the pull request is for! If there's anything about this PR template that seems confusing, send a message in #hackpad in slack!

@vercel

vercelBot commented Feb 20, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

NameStatusPreviewCommentsUpdated (UTC)
hackpad✅ Ready (Inspect)Visit Preview💬 Add feedbackMar 13, 2025 0:32am

@Gamer153

Copy link
Copy Markdown
Contributor

Hey, you seem to have forgotten the pictures of the schematics and PCB, and I couldn't find a picture of the full assembled hackpad with all parts.

Also, a lot of the other approved requests have the images included as files directly, not through some Github link, so I think it'd be good if you add the pictures directly to your PR and README as files.

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thanks for this! On it right away!

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Hey @Gamer153, I have updated the images of the complete Hackpad and Schematic/PCB. I have added a folder of images separately, but while updating in README, it was still converting it into github links so I used CDN links from Slack. Hope this helps!

@Gamer153

Copy link
Copy Markdown
Contributor

Looks good!
Btw, if your image is in the repo on GitHub, you can add it directly in Markdown, and don't have to drag it in: e.g. for the pcb, instead of the link you could put this in your README: ![](img/PCB.png)

Also, according to this slack thread, you should put branding on everything if you're not printing it yourself.

@aryatajne28

aryatajne28 commented Mar 13, 2025

Copy link
Copy Markdown
ContributorAuthor

@Gamer153 I have updated the Branding on both of my Case parts as well as updated the Image links that way! Thanks for the heads up. Can you please check the README once, you will get the idea.

@Gamer153

Copy link
Copy Markdown
Contributor

I approve of this submission! Here's my own approved PR link: #443

@qcoralqcoral left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome job on this hackpad!! officially approved.!!!jhknfui842nf

fill out this form to get it:

https://forms.hackclub.com/hackpadv2

@qcoral
qcoral merged commit 6be5235 into hackclub:mainMar 13, 2025
@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thank you so much!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@aryatajne28@Gamer153@qcoral
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add Full-Size Hackpad.V1 by aryatajne28 · Pull Request #571 · hackclub/hackpad · GitHub
Skip to content

Add Full-Size Hackpad.V1 - #571

Merged
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main
Mar 13, 2025
Merged

Add Full-Size Hackpad.V1#571
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main

Conversation

@aryatajne28

Copy link
Copy Markdown
Contributor

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.

Check off the following to let the reviewers know you've done everything:
[X] I HAVE RAN DRC ON MY DESIGN WITH ZERO ERRORS (Silkscreen errors are okay)
[X] I HAVE BRANDED ALL MY PARTS (PCB, CASE) WITH MY HACKPAD'S NAME
[X] I HAVE MADE SURE MY 3D PRINTED PARTS DO NOT REQUIRE SUPPORTS (Text branding overhang is okay)
[X] I HAVE MADE SURE TO INCLUDE TOLERANCES (0.25mm)
[X] MY HACKPAD'S PCB IS UNDER 100mm x 100mm, I DO NOT HAVE MORE THAN 16X SWITCHES, 2X ROTARY ENCODERS, 1X OLED, 16X LEDS.
[X] IN MY FOLDER, THERE IS A README.MD FILE THAT CONTAINS THE FOLLOWING INFORMATION:

  • Full render including all the parts
  • A few sentences about the inspiration and challenges
  • BOM
  • Photos of the Schematic, PCB, and case

If you're unsure about the format, make sure to check out this example and follow the format there.

If this PR isn't a submission, that's okay too! Please remove the above boxes and explain what the pull request is for! If there's anything about this PR template that seems confusing, send a message in #hackpad in slack!

@vercel

vercelBot commented Feb 20, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

NameStatusPreviewCommentsUpdated (UTC)
hackpad✅ Ready (Inspect)Visit Preview💬 Add feedbackMar 13, 2025 0:32am

@Gamer153

Copy link
Copy Markdown
Contributor

Hey, you seem to have forgotten the pictures of the schematics and PCB, and I couldn't find a picture of the full assembled hackpad with all parts.

Also, a lot of the other approved requests have the images included as files directly, not through some Github link, so I think it'd be good if you add the pictures directly to your PR and README as files.

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thanks for this! On it right away!

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Hey @Gamer153, I have updated the images of the complete Hackpad and Schematic/PCB. I have added a folder of images separately, but while updating in README, it was still converting it into github links so I used CDN links from Slack. Hope this helps!

@Gamer153

Copy link
Copy Markdown
Contributor

Looks good!
Btw, if your image is in the repo on GitHub, you can add it directly in Markdown, and don't have to drag it in: e.g. for the pcb, instead of the link you could put this in your README: ![](img/PCB.png)

Also, according to this slack thread, you should put branding on everything if you're not printing it yourself.

@aryatajne28

aryatajne28 commented Mar 13, 2025

Copy link
Copy Markdown
ContributorAuthor

@Gamer153 I have updated the Branding on both of my Case parts as well as updated the Image links that way! Thanks for the heads up. Can you please check the README once, you will get the idea.

@Gamer153

Copy link
Copy Markdown
Contributor

I approve of this submission! Here's my own approved PR link: #443

@qcoralqcoral left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome job on this hackpad!! officially approved.!!!jhknfui842nf

fill out this form to get it:

https://forms.hackclub.com/hackpadv2

@qcoral
qcoral merged commit 6be5235 into hackclub:mainMar 13, 2025
@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thank you so much!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@aryatajne28@Gamer153@qcoral
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' Add Full-Size Hackpad.V1 by aryatajne28 · Pull Request #571 · hackclub/hackpad · GitHub
Skip to content

Add Full-Size Hackpad.V1 - #571

Merged
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main
Mar 13, 2025
Merged

Add Full-Size Hackpad.V1#571
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main

Conversation

@aryatajne28

Copy link
Copy Markdown
Contributor

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.

Check off the following to let the reviewers know you've done everything:
[X] I HAVE RAN DRC ON MY DESIGN WITH ZERO ERRORS (Silkscreen errors are okay)
[X] I HAVE BRANDED ALL MY PARTS (PCB, CASE) WITH MY HACKPAD'S NAME
[X] I HAVE MADE SURE MY 3D PRINTED PARTS DO NOT REQUIRE SUPPORTS (Text branding overhang is okay)
[X] I HAVE MADE SURE TO INCLUDE TOLERANCES (0.25mm)
[X] MY HACKPAD'S PCB IS UNDER 100mm x 100mm, I DO NOT HAVE MORE THAN 16X SWITCHES, 2X ROTARY ENCODERS, 1X OLED, 16X LEDS.
[X] IN MY FOLDER, THERE IS A README.MD FILE THAT CONTAINS THE FOLLOWING INFORMATION:

  • Full render including all the parts
  • A few sentences about the inspiration and challenges
  • BOM
  • Photos of the Schematic, PCB, and case

If you're unsure about the format, make sure to check out this example and follow the format there.

If this PR isn't a submission, that's okay too! Please remove the above boxes and explain what the pull request is for! If there's anything about this PR template that seems confusing, send a message in #hackpad in slack!

@vercel

vercelBot commented Feb 20, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

NameStatusPreviewCommentsUpdated (UTC)
hackpad✅ Ready (Inspect)Visit Preview💬 Add feedbackMar 13, 2025 0:32am

@Gamer153

Copy link
Copy Markdown
Contributor

Hey, you seem to have forgotten the pictures of the schematics and PCB, and I couldn't find a picture of the full assembled hackpad with all parts.

Also, a lot of the other approved requests have the images included as files directly, not through some Github link, so I think it'd be good if you add the pictures directly to your PR and README as files.

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thanks for this! On it right away!

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Hey @Gamer153, I have updated the images of the complete Hackpad and Schematic/PCB. I have added a folder of images separately, but while updating in README, it was still converting it into github links so I used CDN links from Slack. Hope this helps!

@Gamer153

Copy link
Copy Markdown
Contributor

Looks good!
Btw, if your image is in the repo on GitHub, you can add it directly in Markdown, and don't have to drag it in: e.g. for the pcb, instead of the link you could put this in your README: ![](img/PCB.png)

Also, according to this slack thread, you should put branding on everything if you're not printing it yourself.

@aryatajne28

aryatajne28 commented Mar 13, 2025

Copy link
Copy Markdown
ContributorAuthor

@Gamer153 I have updated the Branding on both of my Case parts as well as updated the Image links that way! Thanks for the heads up. Can you please check the README once, you will get the idea.

@Gamer153

Copy link
Copy Markdown
Contributor

I approve of this submission! Here's my own approved PR link: #443

@qcoralqcoral left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome job on this hackpad!! officially approved.!!!jhknfui842nf

fill out this form to get it:

https://forms.hackclub.com/hackpadv2

@qcoral
qcoral merged commit 6be5235 into hackclub:mainMar 13, 2025
@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thank you so much!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@aryatajne28@Gamer153@qcoral
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add Full-Size Hackpad.V1 by aryatajne28 · Pull Request #571 · hackclub/hackpad · GitHub
Skip to content

Add Full-Size Hackpad.V1 - #571

Merged
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main
Mar 13, 2025
Merged

Add Full-Size Hackpad.V1#571
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main

Conversation

@aryatajne28

Copy link
Copy Markdown
Contributor

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.

Check off the following to let the reviewers know you've done everything:
[X] I HAVE RAN DRC ON MY DESIGN WITH ZERO ERRORS (Silkscreen errors are okay)
[X] I HAVE BRANDED ALL MY PARTS (PCB, CASE) WITH MY HACKPAD'S NAME
[X] I HAVE MADE SURE MY 3D PRINTED PARTS DO NOT REQUIRE SUPPORTS (Text branding overhang is okay)
[X] I HAVE MADE SURE TO INCLUDE TOLERANCES (0.25mm)
[X] MY HACKPAD'S PCB IS UNDER 100mm x 100mm, I DO NOT HAVE MORE THAN 16X SWITCHES, 2X ROTARY ENCODERS, 1X OLED, 16X LEDS.
[X] IN MY FOLDER, THERE IS A README.MD FILE THAT CONTAINS THE FOLLOWING INFORMATION:

  • Full render including all the parts
  • A few sentences about the inspiration and challenges
  • BOM
  • Photos of the Schematic, PCB, and case

If you're unsure about the format, make sure to check out this example and follow the format there.

If this PR isn't a submission, that's okay too! Please remove the above boxes and explain what the pull request is for! If there's anything about this PR template that seems confusing, send a message in #hackpad in slack!

@vercel

vercelBot commented Feb 20, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

NameStatusPreviewCommentsUpdated (UTC)
hackpad✅ Ready (Inspect)Visit Preview💬 Add feedbackMar 13, 2025 0:32am

@Gamer153

Copy link
Copy Markdown
Contributor

Hey, you seem to have forgotten the pictures of the schematics and PCB, and I couldn't find a picture of the full assembled hackpad with all parts.

Also, a lot of the other approved requests have the images included as files directly, not through some Github link, so I think it'd be good if you add the pictures directly to your PR and README as files.

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thanks for this! On it right away!

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Hey @Gamer153, I have updated the images of the complete Hackpad and Schematic/PCB. I have added a folder of images separately, but while updating in README, it was still converting it into github links so I used CDN links from Slack. Hope this helps!

@Gamer153

Copy link
Copy Markdown
Contributor

Looks good!
Btw, if your image is in the repo on GitHub, you can add it directly in Markdown, and don't have to drag it in: e.g. for the pcb, instead of the link you could put this in your README: ![](img/PCB.png)

Also, according to this slack thread, you should put branding on everything if you're not printing it yourself.

@aryatajne28

aryatajne28 commented Mar 13, 2025

Copy link
Copy Markdown
ContributorAuthor

@Gamer153 I have updated the Branding on both of my Case parts as well as updated the Image links that way! Thanks for the heads up. Can you please check the README once, you will get the idea.

@Gamer153

Copy link
Copy Markdown
Contributor

I approve of this submission! Here's my own approved PR link: #443

@qcoralqcoral left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome job on this hackpad!! officially approved.!!!jhknfui842nf

fill out this form to get it:

https://forms.hackclub.com/hackpadv2

@qcoral
qcoral merged commit 6be5235 into hackclub:mainMar 13, 2025
@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thank you so much!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@aryatajne28@Gamer153@qcoral
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add Full-Size Hackpad.V1 by aryatajne28 · Pull Request #571 · hackclub/hackpad · GitHub
Skip to content

Add Full-Size Hackpad.V1 - #571

Merged
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main
Mar 13, 2025
Merged

Add Full-Size Hackpad.V1#571
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main

Conversation

@aryatajne28

Copy link
Copy Markdown
Contributor

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.

Check off the following to let the reviewers know you've done everything:
[X] I HAVE RAN DRC ON MY DESIGN WITH ZERO ERRORS (Silkscreen errors are okay)
[X] I HAVE BRANDED ALL MY PARTS (PCB, CASE) WITH MY HACKPAD'S NAME
[X] I HAVE MADE SURE MY 3D PRINTED PARTS DO NOT REQUIRE SUPPORTS (Text branding overhang is okay)
[X] I HAVE MADE SURE TO INCLUDE TOLERANCES (0.25mm)
[X] MY HACKPAD'S PCB IS UNDER 100mm x 100mm, I DO NOT HAVE MORE THAN 16X SWITCHES, 2X ROTARY ENCODERS, 1X OLED, 16X LEDS.
[X] IN MY FOLDER, THERE IS A README.MD FILE THAT CONTAINS THE FOLLOWING INFORMATION:

  • Full render including all the parts
  • A few sentences about the inspiration and challenges
  • BOM
  • Photos of the Schematic, PCB, and case

If you're unsure about the format, make sure to check out this example and follow the format there.

If this PR isn't a submission, that's okay too! Please remove the above boxes and explain what the pull request is for! If there's anything about this PR template that seems confusing, send a message in #hackpad in slack!

@vercel

vercelBot commented Feb 20, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

NameStatusPreviewCommentsUpdated (UTC)
hackpad✅ Ready (Inspect)Visit Preview💬 Add feedbackMar 13, 2025 0:32am

@Gamer153

Copy link
Copy Markdown
Contributor

Hey, you seem to have forgotten the pictures of the schematics and PCB, and I couldn't find a picture of the full assembled hackpad with all parts.

Also, a lot of the other approved requests have the images included as files directly, not through some Github link, so I think it'd be good if you add the pictures directly to your PR and README as files.

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thanks for this! On it right away!

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Hey @Gamer153, I have updated the images of the complete Hackpad and Schematic/PCB. I have added a folder of images separately, but while updating in README, it was still converting it into github links so I used CDN links from Slack. Hope this helps!

@Gamer153

Copy link
Copy Markdown
Contributor

Looks good!
Btw, if your image is in the repo on GitHub, you can add it directly in Markdown, and don't have to drag it in: e.g. for the pcb, instead of the link you could put this in your README: ![](img/PCB.png)

Also, according to this slack thread, you should put branding on everything if you're not printing it yourself.

@aryatajne28

aryatajne28 commented Mar 13, 2025

Copy link
Copy Markdown
ContributorAuthor

@Gamer153 I have updated the Branding on both of my Case parts as well as updated the Image links that way! Thanks for the heads up. Can you please check the README once, you will get the idea.

@Gamer153

Copy link
Copy Markdown
Contributor

I approve of this submission! Here's my own approved PR link: #443

@qcoralqcoral left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome job on this hackpad!! officially approved.!!!jhknfui842nf

fill out this form to get it:

https://forms.hackclub.com/hackpadv2

@qcoral
qcoral merged commit 6be5235 into hackclub:mainMar 13, 2025
@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thank you so much!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@aryatajne28@Gamer153@qcoral
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); Add Full-Size Hackpad.V1 by aryatajne28 · Pull Request #571 · hackclub/hackpad · GitHub
Skip to content

Add Full-Size Hackpad.V1 - #571

Merged
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main
Mar 13, 2025
Merged

Add Full-Size Hackpad.V1#571
qcoral merged 17 commits into
hackclub:mainfrom
aryatajne28:main

Conversation

@aryatajne28

Copy link
Copy Markdown
Contributor

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.

Check off the following to let the reviewers know you've done everything:
[X] I HAVE RAN DRC ON MY DESIGN WITH ZERO ERRORS (Silkscreen errors are okay)
[X] I HAVE BRANDED ALL MY PARTS (PCB, CASE) WITH MY HACKPAD'S NAME
[X] I HAVE MADE SURE MY 3D PRINTED PARTS DO NOT REQUIRE SUPPORTS (Text branding overhang is okay)
[X] I HAVE MADE SURE TO INCLUDE TOLERANCES (0.25mm)
[X] MY HACKPAD'S PCB IS UNDER 100mm x 100mm, I DO NOT HAVE MORE THAN 16X SWITCHES, 2X ROTARY ENCODERS, 1X OLED, 16X LEDS.
[X] IN MY FOLDER, THERE IS A README.MD FILE THAT CONTAINS THE FOLLOWING INFORMATION:

  • Full render including all the parts
  • A few sentences about the inspiration and challenges
  • BOM
  • Photos of the Schematic, PCB, and case

If you're unsure about the format, make sure to check out this example and follow the format there.

If this PR isn't a submission, that's okay too! Please remove the above boxes and explain what the pull request is for! If there's anything about this PR template that seems confusing, send a message in #hackpad in slack!

@vercel

vercelBot commented Feb 20, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

NameStatusPreviewCommentsUpdated (UTC)
hackpad✅ Ready (Inspect)Visit Preview💬 Add feedbackMar 13, 2025 0:32am

@Gamer153

Copy link
Copy Markdown
Contributor

Hey, you seem to have forgotten the pictures of the schematics and PCB, and I couldn't find a picture of the full assembled hackpad with all parts.

Also, a lot of the other approved requests have the images included as files directly, not through some Github link, so I think it'd be good if you add the pictures directly to your PR and README as files.

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thanks for this! On it right away!

@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Hey @Gamer153, I have updated the images of the complete Hackpad and Schematic/PCB. I have added a folder of images separately, but while updating in README, it was still converting it into github links so I used CDN links from Slack. Hope this helps!

@Gamer153

Copy link
Copy Markdown
Contributor

Looks good!
Btw, if your image is in the repo on GitHub, you can add it directly in Markdown, and don't have to drag it in: e.g. for the pcb, instead of the link you could put this in your README: ![](img/PCB.png)

Also, according to this slack thread, you should put branding on everything if you're not printing it yourself.

@aryatajne28

aryatajne28 commented Mar 13, 2025

Copy link
Copy Markdown
ContributorAuthor

@Gamer153 I have updated the Branding on both of my Case parts as well as updated the Image links that way! Thanks for the heads up. Can you please check the README once, you will get the idea.

@Gamer153

Copy link
Copy Markdown
Contributor

I approve of this submission! Here's my own approved PR link: #443

@qcoralqcoral left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome job on this hackpad!! officially approved.!!!jhknfui842nf

fill out this form to get it:

https://forms.hackclub.com/hackpadv2

@qcoral
qcoral merged commit 6be5235 into hackclub:mainMar 13, 2025
@aryatajne28

Copy link
Copy Markdown
ContributorAuthor

Thank you so much!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@aryatajne28@Gamer153@qcoral