Skip to content
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

Merged
merged 15 commits into from
Nov 4, 2024

Conversation

JFWooten4
Copy link
Member

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

  1. In an effort to remove the template starter pages and get the docs rolling.

Implicated by the site subdomain, and against the Wyoming DUNA naming policy
@JFWooten4 JFWooten4 added the enhancement New feature or request label Oct 1, 2024
@JFWooten4 JFWooten4 self-assigned this Oct 1, 2024
Copy link

netlify bot commented Oct 1, 2024

Deploy Preview for whydrs ready!

Name Link
🔨 Latest commit a31cdeb
🔍 Latest deploy log https://app.netlify.com/sites/whydrs/deploys/67283d2cb6315e00086e079c
😎 Deploy Preview https://deploy-preview-13--whydrs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@JFWooten4
Copy link
Member Author

Pages should get organized (in a starting form) to address items from meeting:

Intro to GitHub

Editing pages

How 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 Accounts

We should detail exactly which (real and bot) accounts have which access in re WhyDRS/.github#7

@JFWooten4
Copy link
Member Author

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 href-able md headings).

@JFWooten4
Copy link
Member Author

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

  1. I'm not sure how much we'll want to use the blog feature/option v. normal pages. Over time we can expand to have a whole host of sections. But for now I just want to document the basic participation info.

@JFWooten4 JFWooten4 marked this pull request as ready for review November 4, 2024 03:20
@JFWooten4
Copy link
Member Author

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

@JFWooten4 JFWooten4 merged commit a5152ee into WhyDRS:main Nov 4, 2024
4 checks passed
@JFWooten4 JFWooten4 deleted the docusaurus-global-config branch November 4, 2024 03:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant