-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Wording & project description (aka README) #2
Comments
I wonder how long we can keep the trend going of our Issue #s in this project matching the same Issues in the iojs.org project ... So far we're 2 for 2! |
lol. The next issue # is a PR: nodejs/iojs.org#3. Probably not going to happen unless we force it to :P |
Closing, the README seems up to date. |
alexandrtovmach
pushed a commit
that referenced
this issue
Jul 15, 2019
aymen94
pushed a commit
that referenced
this issue
Jun 27, 2023
* feat: introduce dynamic rendering of pages * major: full dynamic pages and plain next.js (#2) * chore: do not resort blog posts * fix: sort by post date * chore: apply code-review changes Co-authored-by: Brian Muenzenmeyer <brian.muenzenmeyer@gmail.com> Signed-off-by: Claudio Wunder <cwunder@gnome.org> * chore: some code review changes --------- Signed-off-by: Claudio Wunder <cwunder@gnome.org> Co-authored-by: Brian Muenzenmeyer <brian.muenzenmeyer@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I stole this title from nodejs/iojs.org#2 but in this case the issue concerns the contents of the README specifically.
I assume we'll be bringing over much of the existing node/iojs.org README content in some form as this project evolves to include concepts such as "project structures" and "publishing".
For now mostly I'm requesting a proof read of the initial content I added and for us to get in some glaring omissions:
These can be broad summaries linking to the relevant CONTRIBUTING and GOVERNANCE files, which also still need to be added.
The text was updated successfully, but these errors were encountered: