New website#302
Conversation
✅ Deploy Preview for stratumprotocol ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@lucasbalieiro here we go again :) |
|
Why don't we have logos for every company @pavlenex? |
didn't want to give too much credits to those who announced they'll adopt things, until they do, if you know where to find all these logos and feel strongly feel free to push a commit |
Improve translation Add Spanish language
|
Ok, after a call with @lucasbalieiro and @GitGab19 here's the plan:
|
|
@pavlenex Will a Thai language added as well? |
|
@SirMentos-apt I favored languages which unlocks a big chunk of the audience. If a language was niche for mining, I pushed it down the list unless we had clear demand signals. If you'd like to help with a Thai translation - that would be awesome! https://github.com/pavlenex/stratumprotocol.org/blob/main/locales/en.txt here's a reference file :) |
Co-authored-by: Mohamed Emad <hulxxv@gmail.com>
Co-authored-by: Mohamed Emad <hulxxv@gmail.com>
|
@pavlenex, the submodule is still misconfigured. It looks like For comparison: in the current In your fork, GitHub treats the contents as regular files, which confirms the submodule isn’t set up correctly. I pushed a commit on top of my fork that fixes the configuration and initializes the submodule properly. You can cherry-pick it here: 
With the correct configuration of the submodule, after you cherry-pick my commit you will probably have some issues wit the rendering of the specification. It will be solvable by fetching the data of the submodule: # if clonning for the first time
git clone --recurse-submodules <repo-url>
# if already cloned use
git submodule update --init --recursive |
|
Thanks for reviewing @lucasbalieiro, I've cherry picked on bf29949 and simplified the workflow 87389db I think complexity around worfklow was Codex overriding Claude, trying to harden security, but over-engineering it. Let me know if it's okay now. |
lucasbalieiro
left a comment
lucasbalieiro
left a comment
There was a problem hiding this comment.
ACK on specification, blog, and the submodule workflow. This approach could introduce issues later because most of the work runs client-side at runtime.
For now it’s acceptable given the small number of spec and blog pages. Adding server-side rendering would increase complexity without clear benefit and would effectively bring us back to the previous architecture.
We should validate performance on smartphones to ensure it doesn’t become a bottleneck.
|
Thanks for the review @lucasbalieiro! The only thing remaining is to test how sv2 specs workflow works in practice, and if it updates the website and rebuilds it properly as soon as there's a change in specs, however the only way to test this last step is to merge a PR, then merge stratum-mining/sv2-spec#176 and fingers crossed 🤞 @GitGab19 We should be good to go with above plan if you agree. |
|
ACK. I'll take a look at the PR on |
|
@GitGab19 Oh, right, let's then first look at stratum-mining/sv2-wizard#10 then proceed with this PR and then specs PR to avoid having to push things on this repo in in case there are problems with how wizard is rendered, we probably needs to be bumped as well. |
|
@pavlenex I added a commit to get the newer version of the I don't know why but the netlify preview didn't update, but on your website it seems so. |
GitGab19
left a comment
GitGab19
left a comment
There was a problem hiding this comment.
Green light on my end, we can merge this one and try the spec update workflow.
|
I missed your commit @GitGab19 sorry, i did the same, just tested and indeed it updated. netlify probably caches things. |
5 participants
This PR is cleaner continuation of #300.
Screen.Recording.2026-02-09.at.11.06.52.mov
I realized that once website is deployed on GitHub pages not on Netlify preview, there were some structural change and optimization changes that had to be done.
I believe feedback from #300 has been addressed.
The main goal of the website redesign, for the context, isn't just to have a single source of truth where we miners and pools can lear the basics, but for it to become single source of truth for our upcoming brand and UI guidelines, that will all be re-used first for SV2-Wizard and then be used for our application interface - SV2-UI.
I've been heavily depending on Codex/Claude/Replit to come up with a final output, but I've done my fair share of testing both locally and on an actual domain: https://pavle.org
If anyone has any high-level feedback on design, key communication points or technical explanations, feel free to leave a comment, but since my goal is to publish this live by Thursday so we unblock the progress on Wizard and the App, I'd appreciate mostly concrete code reviews and suggestions.
This is just a first pass, in the future we should add dev docs and several other things.
Note1: that when you click "start mining" the pop-up window looks messed up slightly, but this is because this PR is built on top of the Wizard redesign stratum-mining/sv2-wizard#10 once that one is merged, things will be coherent. If anyone wants to test that one as well, here's what you need to do in your local dev enviroment when you have local sv2-wizard
Note2: both Claude and Codex ran some security improvements for the website, which may've been an overkill, but things work both locally and on GitHub pages so I've left them with those.
Note3: When it comes to perforamnce, I've tried to optimize it as much as possible. https://pagespeed.web.dev/analysis/https-pavle-org/kvbxv9hb4g?form_factor=mobile Netlify preview performance is slower for some reason, mostly due to their own caching, but on github pages, which is where we will be deploying this, it works good.
