-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add blog index section and introductory post #44
Conversation
Co-authored-by: Arminta Jenkins <michaela.iorga@nist.gov> Co-authored-by: Michaela Iorga <michaela.iorga@nist.gov> Co-authored-by: Wendell Piez <wendell.piez@nist.gov>
Open question, I am not sue how the sorting may work when we have more than one blog post or I need to worry about that for now, that is technically outside the scope of this issue for now. |
@aj-stein-nist, by any chance would the blog list be separated into a separate archetype and adjusted to include a link to an RSS feed? This may be more appropriate as follow up work. (Um, wow, not sure how I didn't pay attention and edit the comment and not post my own, haha.) |
Embarrassed to admit that I didn't know it was a blog post archetype, I am not opposed, but can also set it up with a separate issue, I am fine either way. Let me review and follow up and update with a comment. |
I suggest the latest post to be on top, meaning the blogs get published in reverse order, and the last ones get collapsed under [view more] with a redirect or page expand? |
Lessons learned from https://simplewriting.org/blog-vs-blog-post-whats-the-difference/: call the page OSCAL Blog Posts (we are publishing blog posts on OSCAL website. Might even be able to drop "OSCAL" from the title since two is implicit. |
My point was that I am not sure what the inherent order will be, I have to review the archetype and how it is configured now (it could be based on name but I think it is on the filesystem datetime stamp but I have to review). |
The reason I called the index page this is because it is the blog, and the blog contains the blog post. (And just to explain why I made it now: we need the index page for the section of the site or having more than one post will cause a directory re-org and alias fiasco.)
Yeah that's on me. I thought it would publish with the I am making this changes and some others we discussed over the phone. I will push it up soon. |
…ummary, as requested.
As requested, do this so that the distinction between release artifacts, what metaschema-xslt does, and what higher-level transformations that were in oscal-tools is more clear.
ba6c0f6
to
63dadc9
Compare
@iMichaela please re-review, written and verbal feedback included. |
Take feedback with wording improvements and mentioning of a simpler build process. Co-authored-by: Nikita Wootten <nikita.wootten@nist.gov>
I will add this as follow-up work (since I only see we are using the default archetype and not |
Remove more casual language that was not concise enough.
It is not exactly the same thing, but it can be considered redundant, so now remove it.
* Add blog section index. * Add edited blog post for usnistgov/OSCAL#1911. Co-authored-by: Arminta Jenkins <michaela.iorga@nist.gov> Co-authored-by: Michaela Iorga <michaela.iorga@nist.gov> Co-authored-by: Wendell Piez <wendell.piez@nist.gov> * PR feedback: correct blog index heading. * PR feedback: shorten title, stick to fall cleaning. * PR feedback: community->all, all is confusing. * PR feedback: switch from deep to fall cleaning in 1st para. * PR feedback: update changes list to include XSLT converter artifact summary, as requested. * PR feedback: add summary about oscal-tools and oscal-cat As requested, do this so that the distinction between release artifacts, what metaschema-xslt does, and what higher-level transformations that were in oscal-tools is more clear. * Take Nikita's feedback on changes list Take feedback with wording improvements and mentioning of a simpler build process. Co-authored-by: Nikita Wootten <nikita.wootten@nist.gov> * PR feedback: remove contraction. * PR feedback: add mention of v1.1.1 also. * PR feedback: be explicit and repeat mention of OSCAL repo Remove more casual language that was not concise enough. --------- Co-authored-by: Arminta Jenkins <michaela.iorga@nist.gov> Co-authored-by: Wendell Piez <wendell.piez@nist.gov> Co-authored-by: Nikita Wootten <nikita.wootten@nist.gov>
This PR closes #43 (formerly usnistgov/OSCAL#1911) and usnistgov/OSCAL-Pages #34 which existed at the time issue #43 was created.
Index:
First blog post: