-
Notifications
You must be signed in to change notification settings - Fork 534
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
Build a site #15
Comments
@JasonMorgan Have we finalized the CMS/platform for the site? if it's WordPress, count me in :) |
@chetanpdeshmukh we have not but I'd love to hear your point of view! Are you joining the next subcommittee meeting and/or would you like to suggest something? |
@JasonMorgan I have decent exposure to WordPress for designing pages and keeping them light enough for speed and SEO. I am a newbie in cloud native world and the glossary project itself would be an asset for me to look at every now and then (can't contribute to the definitions, but wanted to be a part of this in some way). If this makes sense and helps the mission, would be happy to join the next subcommittee meeting on 17th :) |
mkdocs is another option for us. We can format and publish fairly easily with a GitHub action. |
Going off of @IdealUsrname's suggestion, I think GitBook makes a lot of sense for the glossary. Everything being in markdown already will make building the site out simpler. And the visual style that GitBook follows will be familiar to people who have had some experience going through documentation. |
Hey ! I'm a front end web developer . can I help you with the design or with anything else? Would love to contribute and learn
|
We've got a good set of definitions and the beginnings of a glossary. We should build out a simple site so we can view the glossary rendered with all the completed terms.
The text was updated successfully, but these errors were encountered: