Start new webiste#300
Conversation
❌ Deploy Preview for startling-capybara-2231ea failed.
|
✅ Deploy Preview for stratumprotocol ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
fix redirects and attempt to fix specs rendering
|
@GitGab19 I've added the wizard, and for now I think it's in good shape. Perhaps @lucasbalieiro wants to take overall look at the codebase as well. I leave it to you guys from here. My next step will be proposing design update to sv2-wizard repo to ensure some sort of consistency between the new website and the wizard. Looking forward to hearing thoughts, bug reports and code reviews. This is done with AI Tools Replit, Claude and Codex, and with a lot of local user testing, so I don't think it's a first pass AI slop, I did fair share of reviewing on my end, I believe an actual developer with front-end experience should give it a look. On my end you can also take over this PR if you guys prefer. |
|
The last commit here 7f704e1 ensures compatibility with stratum-mining/sv2-wizard#10, that's why if you press Final output is Screen.Recording.2026-02-06.at.18.59.24.mov |
|
AI is getting a little scary 😂 one of my biggest issues with the previous implementation was how we handled the specs and used Rehype to parse them. Marked is much simpler and a better fit for our use case, and Rehype ended up being used in a very convoluted way. In the new implementation, spec syncing appears to be manual via updates to the |
restore spec submodule at src/specification
|
@lucasbalieiro The way it should work is:
I think you're right and right now was manual, which isn't something we want. I pushed a new commit, 2cb04d4 but would appreciate the review as it'll be vibe-coded and I don't mind you taking it over. I am pretty confident in the landing page, as I can read and understand that code, but /blog and /specification is already beyond my understanding. If you prefer I can do only a landing page in a new PR, and leave it up to you to implement blog and specs if it makes you feel more comfortable about the quality of code, or you just take a look at those sections after these pushes, make more comments and I can try to path them up. Just let me know which direction you'd like to go for? |
|
@pavlenex, I think you can go with vibecoding this, no issues on my side. I can build on top of it later if needed by suggesting commits to cherry-pick or proposing solutions in comments. just orient the AI to place the module under the new path from the commit you linked, it looks like it was trying to preserve backward compatibility by adding the submodule to I think it’s better for us to update the specs workflow instead of maintaining backward compatibility, as a follow-up PR there once we merged here. While you make the AI do this I’ll be reviewing the other repos where I was tagged about the new ui. But if the AI is having a hardtime doing the submodule, just ping me. I can do it by hand, with no problem |
|
I also think I can improve that workflow so that in the future, if we ever change the specification path in stratumprotocol.org again, we won’t have to clutter the specs repo with random PRs just to update it. I still need to test it first. if you can set up the submodule and make the website render from there, that would be a great step forward |
|
Thanks for pointers @lucasbalieiro, indeed my goal was to preserve backwards compatibility and not put too much pressure on specs, but I agree it's easier and cleaner to nest everything under /content. My main goal with this is to provide some foundation for uplifted branding so we can define a shared design system for SV2-UI and SV2-Wizard as well. Please when you're available next week, ping me on Discord so you me and @GitGab19 can jump on a quick call to agree on these moving parts. |
@pavlenex,I don’t think we need to change anything in the specs CI. We can ignore its arguments and hardcode the submodule path. Instead of using Updated name: Update submodule
on:
repository_dispatch:
types:
- update-submodule
jobs:
update:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
token: ${{ secrets.PAT }}
submodules: recursive
- name: Update module
run: |
git submodule update --init --recursive --checkout -f --remote -- content/specification
git config --global user.name "GitHub Action"
git config --global user.email "noreply@github.com"
git commit -am "deploy: content/specification - ${{github.event.client_payload.sha}}"
git push |
Specs restructure Create specification
3 participants
This PR replaced the old website with new redesign, better explanation of SV2 and more modern, slick desgin. Codebase for the new website is much cleaner than previous one which was nearly impossible to contribute or understand.
Screen.Recording.2026-02-06.at.18.59.24.mov
Preview https://deploy-preview-300--stratumprotocol.netlify.app/
To-do: