geo/geo-coop
geo/geo-coop
7
1
Fork 0
Code Issues 55 Pull requests Projects Releases Packages Wiki Activity Actions

A visitor can see the latest articles, blog posts, gleanings, issues, and featured information on the front page (homepage) #33

New issue
Closed
opened 2019-08-22 20:30:34 +00:00 by cedewey · 22 comments
cedewey commented 2019-08-22 20:30:34 +00:00 (Migrated from gitlab.com)
Copy link

Background

We need to figure out what content will appear on the homepage. Ideally we stick to what Drutopia provides as much as possible.

Drutopia homepage for reference - https://demo.drutopia.org/

Homepage structure

  1. Hero content area (can be used to provide a blurb of GEO, feature an article or something else)
  2. Latest articles
  3. Latest blog posts
  4. Latest gleanings
  5. Latest issues/Movement pages (Issue index content type)
  6. Featured articles (changed manually, highlights popular/older articles)
  7. Three across blocks (can be used for ad space, donation call out, sign up for newsletter, etc.)

Design

Design will be the same as Drutopia offers, with one exception - the first call to action block should span the full width of the page and be directly below the menu, no space.

Work Required

  • Define the content and the order it will appear on the homepage.
  • Implement according to requirements
## Background We need to figure out what content will appear on the homepage. Ideally we stick to what Drutopia provides as much as possible. Drutopia homepage for reference - https://demo.drutopia.org/ ## Homepage structure 1. Hero content area (can be used to provide a blurb of GEO, feature an article or something else) 1. Latest articles 1. Latest blog posts 1. Latest gleanings 1. Latest issues/Movement pages (Issue index content type) 1. Featured articles (changed manually, highlights popular/older articles) 1. Three across blocks (can be used for ad space, donation call out, sign up for newsletter, etc.) ## Design Design will be the same as Drutopia offers, with one exception - the first call to action block should span the full width of the page and be directly below the menu, no space. ## Work Required * [x] Define the content and the order it will appear on the homepage. * [x] Implement according to requirements
cedewey commented 2019-08-22 20:31:50 +00:00 (Migrated from gitlab.com)
Copy link

@joshua_davis I've taken a first pass on the homepage structure - https://gitlab.com/agaric/sites/geo/issues/33#homepage-structure

Keep in mind that the description field does not have version control. So, you might want to compose the final list in a text editor then paste it in.

@joshua_davis I've taken a first pass on the homepage structure - https://gitlab.com/agaric/sites/geo/issues/33#homepage-structure Keep in mind that the description field does not have version control. So, you might want to compose the final list in a text editor then paste it in.
joshua_davis commented 2019-08-26 14:38:10 +00:00 (Migrated from gitlab.com)
Copy link

Here are my additions/changes (not many)

Hero content area (can be used to provide a blurb of GEO, feature an article or something else)

Latest articles

Latest blog posts

Latest gleanings

Latest issues/Movement pages (Issue index content type)

Featured articles (changed manually, highlights popular/older articles)

Three across blocks (can be used for ad space, donation call out, sign up for newsletter, etc.)

Here are my additions/changes (not many) Hero content area (can be used to provide a blurb of GEO, feature an article or something else) Latest articles Latest blog posts Latest gleanings Latest issues/Movement pages (Issue index content type) Featured articles (changed manually, highlights popular/older articles) Three across blocks (can be used for ad space, donation call out, sign up for newsletter, etc.)
cedewey commented 2019-08-26 16:34:23 +00:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
cedewey commented 2019-08-26 16:34:36 +00:00 (Migrated from gitlab.com)
Copy link

Perfect, thanks!

Perfect, thanks!
cedewey commented 2019-08-26 16:34:42 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @cedewey and unassigned @joshua_davis

assigned to @cedewey and unassigned @joshua_davis
cedewey commented 2019-08-30 16:12:05 +00:00 (Migrated from gitlab.com)
Copy link

marked the checklist item Define the content and the order it will appear on the homepage. as completed

marked the checklist item **Define the content and the order it will appear on the homepage.** as completed
cedewey commented 2019-08-30 16:13:37 +00:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
cedewey commented 2019-08-30 16:20:02 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in issue #24

mentioned in issue #24
cedewey commented 2019-08-30 16:20:26 +00:00 (Migrated from gitlab.com)
Copy link

closed

closed
mlncn commented 2019-09-22 21:56:46 +00:00 (Migrated from gitlab.com)
Copy link

reopened

reopened
mlncn commented 2019-09-22 21:57:32 +00:00 (Migrated from gitlab.com)
Copy link

changed title from {-Define requirements for the homepage-} to {+A visitor can see the latest articles, blog posts, gleanings, issues, and featured information on the front page (homepage)+}

changed title from **{-Define requirements for the homepage-}** to **{+A visitor can see the latest articles, blog posts, gleanings, issues, and featured information on the front page (homepage)+}**
mlncn commented 2019-09-22 21:57:58 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @mlncn and unassigned @cedewey

assigned to @mlncn and unassigned @cedewey
mlncn commented 2019-09-22 21:58:58 +00:00 (Migrated from gitlab.com)
Copy link

marked this issue as related to #24

marked this issue as related to #24
mlncn commented 2019-09-23 14:45:10 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 3de2cf05e0

mentioned in commit 3de2cf05e0819b00830e510619ab2c1d462cbc78
mlncn commented 2019-09-24 13:03:28 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in issue #13

mentioned in issue #13
mlncn commented 2019-09-29 19:50:19 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit dabce158c9

mentioned in commit dabce158c90c14c81723341163f477906eceec08
cedewey commented 2019-09-30 15:29:40 +00:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
mlncn commented 2019-10-13 09:14:27 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @FreeScholar

assigned to @FreeScholar
mlncn commented 2019-10-13 09:14:54 +00:00 (Migrated from gitlab.com)
Copy link

unassigned @mlncn

unassigned @mlncn
cedewey commented 2019-10-16 20:18:17 +00:00 (Migrated from gitlab.com)
Copy link

marked the checklist item Implement according to requirements as completed

marked the checklist item **Implement according to requirements** as completed
cedewey commented 2019-10-16 20:18:28 +00:00 (Migrated from gitlab.com)
Copy link

Homepage looks great. Closing!

Homepage looks great. Closing!
cedewey commented 2019-10-16 20:18:28 +00:00 (Migrated from gitlab.com)
Copy link

closed

closed
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
drupal10-rebased
drupal10
master
12-comments
old-aug-left-on-local
No results found.
Labels
Clear labels   
A11y

Accessibility-related issues

  
Automated Testing

   
Contributable

Issues with work that can (potentially) be contributed back to Drupal or other FLOSS projects.

  
Contributed

Tag issues where we have contributed work back to FLOSS projects (replace Contributable tag; the Contributed tag can be removed once the contribution is recorded in a blog or something.

  
Decision

An issue that requires a decision be made.

  
Design

Issues that should include a UX/design work or review.

  
Development

   
Drutopia

Issues related to Drutopia features or infrastructure, or are potential Drutopia enhancements (with tag Contributable).

  
IndieWeb

Anything related to interlinking web sites in a broadly IndieWeb fashion, see https://indieweb.org/

  
Infrastructure

   
Launch Critical

Issue that must be done in time for launch.

  
Marketing

   
Needs documentation

When an issue has uncovered something that should be documented in a user guide or the project wiki or anywhere else outside the issue queue.

  
Post-Launch

An issue that needs to be completed, but can happen after launch.

  
status
Abandoned
An issue that has been abandoned and will not be completed.

  
status
Blocked
An issue that is blocked for a reason outside Agaric's control.

  
status
Deploy
An issue that has been tested and is ready to be deployed.

  
status
Doing

  
status
Done

  
status
In Review
An issue that has been completed and is ready for a code and/or design review.

  
status
Needs Clarification

  
status
Test
An issue that has been completed and is ready to be tested.

  
status
To Do
An issue that is an agreed priority and has all information needed to be completed.

  
type
Bug

  
type
Task

  
type
User Story

No labels
A11y
Automated Testing
Contributable
Contributed
Decision
Design
Development
Drutopia
IndieWeb
Infrastructure
Launch Critical
Marketing
Needs documentation
Post-Launch
status
Abandoned
status
Blocked
status
Deploy
status
Doing
status
Done
status
In Review
status
Needs Clarification
status
Test
status
To Do
type
Bug
type
Task
type
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: geo/geo-coop#33
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?