-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Format off for Community Page #126
Comments
@lunacodes perhaps you and I could write up some guidelines for the given format and how to keep it going forward that then @tetron and @mr-c can review? |
A few thoughts on the page, now that I'm looking at it again:
|
Hi Luna - I would suggest the following - make a new page for the Weekly Meetings and adjust that and have the text go back to the old text and adjusting the following text for the last bullet point:
---> where the link is the details for the meeting, times, login as less as the previously in the bullet google groups sign in. |
Also started the document for Guidelines here: |
Change <img> tags to markdown format in community.md
* Change <img> tags to markdown format in community.md * Add additional helper classes for SCSS
@swzCuroverse Makes sense. I have a PR #131 with revised formatting already - so I'll add this there. I can name the new page Just to clarify:
Is that correct? |
Yes, thank you. |
The meeting details on the new community page are not formatted by like the rest of the page.
In general: Perhaps we don't need this on the community page but a link to a new page since it swallows up the rest of the resources of which the page was intended. We already have a mention of the weekly chat in the bullet points, so it is extra confusing. Perhaps that should link to a nicely formatted page about the meetings if people are interested.
To look like the rest of the page/general guidelines:
(1) Follow look and feel of rest of site
(2) Make things are new person/user friendly as possible: No explanation made about what the Weekly Meeting is, why one would attend or any context. Again, lots of work to make things as user-friendly in mind so we should keep doing this.
In general, we should have a review process since a bunch of work was made to make the website look good , organized, be approachable and consistent. Otherwise, I fear we will lose the headway we made quickly with the reformat.
The text was updated successfully, but these errors were encountered: