You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aluminum is our first six week development cycle. We need some way to reference cycles, so we're going to try naming them after elements from the periodic table. First up, A is for Aluminum!
Aluminum will focus on our goal of facilitating Open Source Docs contributions through Netlify CMS as a less technical alternative to writing docs directly in GitHub. We'll also be digging into long standing requests for the CMS.
How It Works
The development cycle will begin Monday, February 18th, and end Friday, March 29th. A release for the cycle will occur during the final week, allowing room for follow up patches.
What's Included
Support OSS Documentation Contributors #2093: Support OSS Documentation Contributors
Open source docs sites generally provide "Edit this page on GitHub" links throughout. This effort will allow Netlify CMS to be used instead of editing within GitHub, even if the contributor doesn't have write access to the repo.
Add sorting ability to list of entries #54: Add sorting ability to list of entries
Some kind of sorting needs to be provided in the CMS, even if it's just driven by config. As evidenced in the issue, this request seems simplistic, but is actually pretty complex for Git via API. But we got this 💪
Entry Card Customization #2019: Entry Card Customization
This one is requested often, and shouldn't be tough to implement, we just need to figure out the right configuration approach.
https://github.com/netlify/netlify-cms/issues/2092: We need guides.
Our current docs effort is centered around guides - entries focused on a specific aspect of Netlify CMS, or that cover an integration angle, like authenticating with XYZ library. This is sort of an umbrella issue, and a great place to get started contributing.
Contributing
If you want to commit to resolving an issue during this cycle, please comment and we can get your issue(s) added here! If you're looking for somewhere to start, check out our good first issue's, or our evergreen Priorities Issues board.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Aluminum is our first six week development cycle. We need some way to reference cycles, so we're going to try naming them after elements from the periodic table. First up, A is for Aluminum!
Aluminum will focus on our goal of facilitating Open Source Docs contributions through Netlify CMS as a less technical alternative to writing docs directly in GitHub. We'll also be digging into long standing requests for the CMS.
How It Works
The development cycle will begin Monday, February 18th, and end Friday, March 29th. A release for the cycle will occur during the final week, allowing room for follow up patches.
What's Included
Open source docs sites generally provide "Edit this page on GitHub" links throughout. This effort will allow Netlify CMS to be used instead of editing within GitHub, even if the contributor doesn't have write access to the repo.
Some kind of sorting needs to be provided in the CMS, even if it's just driven by config. As evidenced in the issue, this request seems simplistic, but is actually pretty complex for Git via API. But we got this 💪
This one is requested often, and shouldn't be tough to implement, we just need to figure out the right configuration approach.
Our current docs effort is centered around guides - entries focused on a specific aspect of Netlify CMS, or that cover an integration angle, like authenticating with XYZ library. This is sort of an umbrella issue, and a great place to get started contributing.
Contributing
If you want to commit to resolving an issue during this cycle, please comment and we can get your issue(s) added here! If you're looking for somewhere to start, check out our good first issue's, or our evergreen Priorities Issues board.
The text was updated successfully, but these errors were encountered: