ansible-community / community-website Goto Github PK

We need an image or two that clearly maps out the main projects in the Ansible ecosystem. Ideally, this image has clickable links to each of the projects so readers can hop directly there. Something like the Saltstack getting started image.

When the proposed new community site is up, we will need to redirect some Ansible.com pages to the new site. Note: docs.ansible.com redirects are covered in a separate issue.

Pages to redirect:

• https://www.ansible.com/community

Implement the "Ecosystem" section from the wireframe issue #57

This should result in a file such as template/homepage-something-band.tmpl along with the associated themes/ansible-community/sass/_homepage-something-band.scss definition.

Design the docs landing page based on personas:

• use ansible/jinja2 for quick prototyping
• and links from docs.ansible.com to this prototype site for community feedback
• add links from prototype site to docs.ansible.com so reviewers can quickly get back to the existing site.

The site is using some styling from https://www.ansible.com/hubfs/css/styles.min.css

We should replace whatever classes the site pulls in from that "ansible.com" css with either bootstrap or custom scss. First preference is to use bootstrap and keep main.scss fairly lightweight and manageable.

To resolve this issue:

• Identify which elements / attributes are formatted by the "ansible.com" css.
• Remove "ansible.com" css from

  community-website/themes/ansible-community/templates/base_helper.tmpl

  Line 126 in 23b7e11

  <!-- Ansible.com css -->

• Format the identified elements / attributes with bootstrap or custom scss.

Fosstodon is an instance of Mastodon - our Ansible Mastodon presence is on Fosstodon (cf. my Email address is on Gmail)

Implement the top-level "Automation Powered by People" section from the wireframe issue #57

This should result in a file such as template/homepage-something-band.tmpl along with the associated themes/ansible-community/sass/_homepage-something-band.scss definition.

Grab the bullito svg here: https://github.com/ansible/logos/blob/main/ansibull-community/ansibull-community.svg

Note that we can implement the nav/menu bar separately.

We will need a way to test changes to the community site without impacting the existing published site (when it exists :-).

T

Media queries and breakpoints will ensure that the site looks nice and behaves as expected on all devices, including mobile displays.

Content on the homepage should be "stacked" in each section as per the wireframe. Additionally we might choose to hide "no display" certain elements like the clipboard button on mobile (nobody is going to pip install ansible in a terminal on their phone).

Add posts to the site.

We need to come to an early consensus on what we require from this new site. This should be in a format easy for community members to comment on or add items to (potentially hackmd?)

MVP = Minimum viable product

NOTE: This is not designing wireframes but more a set of important components or characteristics that must be in the new site. Some items may not be part of the first deployment of the new site. This is an iterative process.

The Ansible community site requires some icons. The purpose of this issue is to create SVG icons that represent the following:

– Automate
– Agentless
– Extensible
– Collections
– Open-source
– Ecosystem

We would also like a community AWX logo if there isn't one already.

The new icons should go into this directory: https://github.com/ansible-community/community-website/tree/main/images

Follows up on #94

In templates/homepage-blogs.tmpl there is <h2><a href="{{ post.permalink(lang) }}">{{ post.title(lang)|e }}</a></h2>

h2 is set as a workaround because, for some reason, Nikola pushes the heading down a level. h3 becomes h4 and so on. Investigate this and fix.

Add the tabbed menu bar from wireframe issue #57

Note that this issue is the lowest in the order of priority. Please do not start working on this until all other wireframe issues are complete.

Once we have reasonable consensus on the website, We need to provide ways people can give us feedback that doesn't only depend on gitub.

Implement the "Blogs" section from the wireframe issue #57

This should result in a file such as template/homepage-something-band.tmpl along with the associated themes/ansible-community/sass/_homepage-something-band.scss definition.

Implement the "Contribute" section from the wireframe issue #57

This should result in a file such as template/homepage-something-band.tmpl along with the associated themes/ansible-community/sass/_homepage-something-band.scss definition.

The site currently uses a set of custom scss files (sass resources) that provide font and colour styling along with some classes for other elements.

The objective of this issue is to review the custom scss with the following objectives:

• Identify redundant / unnecessary styling. If we should just be using bootstrap then we should drop custom styling.
• Ensure custom scss is well-structured, both with a forward-looking view of maintenance as well as to prevent any unexpected behaviour. Custom scss should be "clean" and minimal.

Sass resources are in this directory and compiled to css when the site builds:

https://github.com/ansible-community/community-website/tree/main/themes/ansible-community/sass

Compiled stylesheets are included in the site here:

We have community details in a number of places. We should review and determine what should go on the community site:

• https://docs.ansible.com/ansible/latest/community/index.html
• Existing Ansible.com community details
• stuff for matrix and github and wiki pages etc

Create a homepage for the Ansible community site that incorporates #20

One of the key things that we hear from other community teams with lots of experience is to use what folks are familiar with and stick with familiar frameworks to avoid too much customization.

For the Ansible community site we should limit the ansible-community theme to the index page as much as possible and use something like bootstrap for the posts and pages.

https://themes.getnikola.com/v8/bootstrap4-jinja/

Identify, define, and design any other subpages on the website.

Note the main page and the docs landing page are covered in other issues.

https://github.com/codespell-project/codespell

Hello all,

I think title says it all. We need to decide what is the proper issue for this project ideally before taking any contribution.

In an earlier chat CC-BY-SA (https://creativecommons.org/licenses/by-sa/4.0/) was brought up as a possibility.

What is the group opinion on that ?

Our site should be accessible to all users.

• Consider accessibility during design and implementation of the wireframe
• Find open accessibility testing tools we can apply to the new website
• Complete WCAG assessment for the homepage
• Complete WCAG assessment for blog posts

add the Ansible logo or word brand to the site menu navigation

Footer doesn't span full width and looks centered from the left margin.

Once the site is complete, we need to redirect docs.ansible.com to the new domain and new docs landing pag(es).

We need a central web presence for the Ansible community. This web presence will be based on persona-based journeys that guide the reader in two ways:

To find the information they are looking for
To guide them along an 'experience' journey from new user through more advanced user, to community participant, all the way to community/contributor leader.

Steps identified so far to accomplish this idea:

• #7
• #19
• #20
• #21
• ansible-community/community-team#165
• #22
• #8
• #9
• #10
• #11
• #12
• #13
• #23
• #14
• #15
• #16
• #17
• #18
• ansible-community/community-team#179
• #6
• ansible-community/community-team#191

Since this is a community website, we want community involvement as soon as possible.

We need to:

• Set up a website WG in all the normal places
  • ansible-community/community-team#184
  • Ansible WG calendar (if needed)
• Announce in:
  • Bullhorn
  • Reddit
  • Possibly as a docs banner?
  • matrix room(s)
  • social media
  • mail lists

Implement the "Contribute" section from the wireframe issue #57

This should result in a file such as template/homepage-something-band.tmpl along with the associated themes/ansible-community/sass/_homepage-something-band.scss definition.

See @GregSutcliffe for Discourse integration.

Implement the "Community" section from the wireframe issue #57

This should result in a file such as template/homepage-something-band.tmpl along with the associated themes/ansible-community/sass/_homepage-something-band.scss definition.

Ansible community banner icon for the homepage. Something to replace the "ansible.com" community banner: https://www.ansible.com/hubfs/2015_Images/Community/ansible-community-header-bg.jpg

Update the subscribe to the Bullhorn band so it matches the wireframe #57

Add the "Why Ansible?" section from the wireframe issue #57

This should result in a file such as template/homepage-something-band.tmpl along with the associated themes/ansible-community/sass/_homepage-something-band.scss definition.

To ensure we start with a good quality site and make this a community effort, we should put out a call for community voluneers with web/ux experience to provide input to the new site (or even design it) based on our list of requirements.

As a community website, we'll want to be able to see some analytics on the website use so we can adapt and improve popular pages over time, etc.

Some options to evaluate include plausible.io, simpleanalytics.com, and usefathom.com.

That's not an exhaustive list and more options people are familiar with are welcome.

Ansibull is great and the OG mascot based on https://twitter.com/ansibull

You can see Ansibull in places like the Bullhorn:

One piece of feedback from the Ansible community team has gathered is that Ansibull is maybe not the most all-round best representation of the actual humans in the Ansible community. Part of the issue might be that bulls need to be depicted as quite masculine otherwise they can be mistaken for cows.

The purpose of this issue is to consider a mascot revamp that all contributors can identify with and see as a welcoming companion. There to help you do awesome automation. Also this issue should not try to replace Ansibull. Maybe just sort of a facelift.

For quick iteration we built the initial homepage "on top" of a Nikola site. Next step is to integrate the homepage that we built with the rest of our Nikola site. To do this, extend the base template with base_helper to include the compiled css and index templates.

This issue follows up on #32

• Add custom base templates to themes/ansible-community that include the redhat footer and compiled css.
• Build index.html off the base template.
• Replace ansible.com navbar with the Nikola theme navbar generated from conf.py
• Ensure posts and pages build as expected with the parent theme.

There is a button attribute (maybe class="btn btn-primary") in the submenus that causes a red background on click.

To improve our ability to automatically update the community website after a PR merge, we should include some CI/tests to the project (zola for example?)

We'd like to have three main phases to this website:

• Alpha (currently labeled `alpha candidate' )
• MVP (to show at Ansible Community Day/Fest/Summit) - labeled MVP
• GA - our full release of the new website (no current label)

Let's use this issue to discuss what we want from these three phases.

We have an existing effort to define docsite personas. We should ensure that also covers the new community site, or finalize any additions/changes to that for the community website as a whole.

Don't direct users away from the site when they click on items in the nav bar.

Based on the defined user journeys, create the front page content of the new community site, with community input.

https://getnikola.com/handbook.html#deploying-to-github

This includes:

• Get quick feedback on a short-list of preferred static site generators
• Set this up in the github repo