-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Merge policies repo into larger repo #764
Conversation
Signed-off-by: NPDebs <[email protected]>
✅ Deploy Preview for ols-bebatut ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Thanks @NPDebs I have doubts about the structure. For example,
@yochannah what do you think? |
I hadn't thought that deeply about the structure. Since the goal was to put the resources in one place, I mostly just cloned the policies repo and copied the files into a new directory. No folder reshuffling, |
yes the goal was to put the resources in one place, but maybe good to organize it where it fits best |
True. 💯 |
Agreed. I think, probably, some of this might need to go under the Open Seeds or training pages sub-folders, and for other groups of pages we might want an index page of some sort. Tagging @iramosp in case she has anything she wants to add (maybe not, I know you're busy with Nebula!) |
Signed-off-by: NPDebs <[email protected]>
Signed-off-by: NPDebs <[email protected]>
Signed-off-by: NPDebs <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The structure looks clear to me. I'll wait for Bérénice to approve.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
Some comments
- The template for cohort calls should be in the cohort GitHub repo
- All policies related to Open Seeds would be better in the Open Seeds folder and linked to them from the menu
- Each document here could be a proper page (only need have the metadata on the top)
- If documents are page, email addresses and links to website could be done using Jekyll variables (easier to update - many are currently outdated)
policies-procedures-and-docs/cohort-procedures-and-templates/video-facilitator-guide.md
Outdated
Show resolved
Hide resolved
policies-procedures-and-docs/cohort-procedures-and-templates/speedblog.md
Outdated
Show resolved
Hide resolved
policies-procedures-and-docs/cohort-procedures-and-templates/microgrants.md
Outdated
Show resolved
Hide resolved
policies-procedures-and-docs/cohort-procedures-and-templates/graduation-guide.md
Outdated
Show resolved
Hide resolved
policies-procedures-and-docs/cohort-procedures-and-templates/Cohort-call-facilitator-Guide.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Bérénice Batut <[email protected]>
Co-authored-by: Bérénice Batut <[email protected]>
Co-authored-by: Bérénice Batut <[email protected]>
Signed-off-by: NPDebs <[email protected]>
Signed-off-by: NPDebs <[email protected]>
Signed-off-by: NPDebs <[email protected]>
Signed-off-by: NPDebs <[email protected]>
Signed-off-by: NPDebs <[email protected]>
_includes/default-header.html
Outdated
<a class="navbar-item" href="{% link openseeds/cohort-procedures-and-templates/cohort-call-facilitator-guide.md %}"> Cohort Call Facilitator Guide </a> | ||
<a class="navbar-item" href="{% link openseeds/cohort-procedures-and-templates/expert-guide.md %}"> Expert Guide </a> | ||
<a class="navbar-item" href="{% link openseeds/cohort-procedures-and-templates/graduation-guide.md %}"> Graduation Guide </a> | ||
<a class="navbar-item" href="{% link openseeds/cohort-procedures-and-templates/microgrants.md %}"> Microgrants </a> | ||
<a class="navbar-item" href="{% link openseeds/cohort-procedures-and-templates/speedblog.md %}"> Speedblog </a> | ||
<a class="navbar-item" href="{% link openseeds/cohort-procedures-and-templates/video-facilitator-guide.md %}"> Video Facilitator Guide </a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea
Signed-off-by: NPDebs <[email protected]>
I have indeed, and intend to fix them. 🙏🏽 |
Fixed! Next on the agenda:
|
Update: Along with some minor adjustments, Then, I filtered to include docs in |
Yaaay, my new filter worked! 🎉 🕺 |
For some reason, the |
Of course it worked! 😭 |
Thanks a lot @NPDebs for that work! |
And the record for the fastest debug time goes to @bebatut. Thank you! ❤️ |
This PR fixes issue #760.
As mentioned by Yo, it makes sense to have these assets located in one central repository.
Changes made:
All the resources currently housed in the policies-procedures-and-docs repo have been migrated to the main repo, where the majority of website assets are located.
Note for reviewers:
After this is thoroughly reviewed and merged, we should consider archiving the policies repo first and only delete when we have seen that this system works.
Thank you!