-
Notifications
You must be signed in to change notification settings - Fork 2
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
🔃 Modernize, update site architecture #13
Conversation
Implicated by the site subdomain, and against the Wyoming DUNA naming policy
✅ Deploy Preview for whydrs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Pages should get organized (in a starting form) to address items from meeting: Intro to GitHubEditing pagesHow to change a page, and the decentralized management behind those updates. This area should walk people though how to make an update or do a larger PR, based on comments here. Service AccountsWe should detail exactly which (real and bot) accounts have which access in re WhyDRS/.github#7 |
Meeting recordings should implicate WhyDRS/Taking-Stock#7 Ideally just a page for each, then you can have the written resources, supplements, and transcripts below (ideally with |
I'm going to be honest here. This is marginally outside my wheelhouse, and I don't have things going perfectly just yet. Indeed, my final implementation will probably leave much to be desired. However, I'm going to get this working with some of the rudimentary primitives. That way we can have a solid intro for the community.1 Then, others can come to enhance more technical aspects moving forward. Footnotes
|
Some lingering links to setup with the blog authors depending on how we want to use other folder sources, which should be much less cluttered now that major SEC docs are in their own repos re https://github.com/orgs/WhyDRS/discussions/23#discussioncomment-11137487 |
There are some material basic items to configure such as page linking, preliminary design, and markdown formatting.1
In the spirit of open collaboration spearheaded by James, 🧠 I'll start preparing some of these changes as time allows in this
draft
PR.Once it has the main changes ready for discussion, I'll mark it as ready and see who might want to review info. 🤝
Footnotes
In an effort to remove the template starter pages and get the docs rolling. ↩