Cosmetic #151
Cosmetic #93: Basic design for initial launch
Theme Occupation node view
| Status: | Resolved | Start date: | 01/13/2012 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | 02/17/2012 | ||
| Assignee: | - | % Done: | 80% |
||
| Category: | theming | Spent time: | 13.00 hours | ||
| Target version: | 1.0 | ||||
| Difficulty: | average |
Description
The occupation content type is done.
We're going to leave the node view up to your magic fingers.
Related issues
| related to #OWSdirectory - Cosmetic #150: theme occupation node edit form | Closed | 02/04/2012 | 02/17/2012 | |
| related to #OWSdirectory - Cosmetic #833: Update Site design/layout | Resolved | 11/06/2012 |
History
Updated by Andrew Mallis over 1 year ago
- Assignee changed from Nikkiana Henninger to Trevor Twining
Updated by Andrew Mallis over 1 year ago
- Due date changed from 01/17/2012 to 01/23/2012
Updated by Andrew Mallis over 1 year ago
- Priority changed from Normal to High
Updated by Trevor Twining over 1 year ago
Andrew and I just spoke and we're going to prioritize efforts between now and Thursday on the following.
1) Occupation node view. If you want to put a basic wireframe together that improves the overall understanding of that information, I think that would be great. In the meantime I'll work on basic typography and grouping of data, and try to add visual elements to data where appropriate.
2) Tightening up normal pages. This includes sidebar, footer, and menu formatting (let me know if I'm missing anything Andrew)
3) Directory display (as shown on front page). This should probably be more in a card-style layout.
4) Node form theming. We should probably take our cues on layout from the node display, but there might be particular constraints or things we'll need to factor in for the edit view.
Based on my understanding, 1) and 2) really need to be done before we can launch, and 3) & 4) can potentially wait until the next release (but would be nice to have).
Updated by Andrew Mallis over 1 year ago
- Due date changed from 01/23/2012 to 01/26/2012
2) Tightening up normal pages. This includes sidebar, footer, and menu formatting (let me know if I'm missing anything Andrew)
We'll have some static content (about pages) that I gotta work on.
Started on a basic card view
Updated by Andrew Mallis over 1 year ago
- Due date changed from 01/26/2012 to 02/06/2012
- Priority changed from High to Urgent
Updated by Trevor Twining over 1 year ago
- Status changed from New to Feedback
First pass complete. We will need to enable omega_tools on the dev site in order to make sure the code-based theme config is used rather than the db-config.
I also have a bunch of changes to the occupation feature (added a new manage display view for full node, and added a bunch of grouping options for that display).
The sidebar cannot be displayed on this page. We should probably remove the sidebars from the default zone/region config, and then add them in using a context/delta variant for uses cases where it's needed. None of the work here would interfere with that if the use case arose.
Also, discovered while I was working on this that I don't have access to the dropbox with all of Thiago's files. I'll need that when you get a chance.
TT
Updated by Andrew Mallis over 1 year ago
I enabled Omega_Tools on dev.
Would it make sense for us to roll an "Occupation Directory Theme" feature that sets omega_tools and your custom module (?) as dependencies + whatever else you think fits the mold? Some contexts?
We so don't need a sidebar on the public-facing side. Let's kill it for non-logged in users, for one.
Second, let's only expose it in certain contexts, like on /occupations/manage and whatever else we add to this rubrik. We could also do this on a block-level. Maybe better for bootstrapping?
I've added you to the dropbox.
I pushed the code up to staging, resetting the omega settings and cleared the cache. Seems to have taken.
I'll let you do this on DEV, to be sure everything goes off smoothly.
I guess maybe revert the features also if the DIFFs make sense to you also, please/
Updated by Andrew Mallis over 1 year ago
I rolled an "Occupation Directory Structure" feature that requires context and manages most of our blocks.
I killed the Navigation block altogether for now.
Did some experimenting locally with Omega Tools and felt confident enough to revert to the .info on DEV.
Updated by Andrew Mallis over 1 year ago
- Due date changed from 02/06/2012 to 02/17/2012
- Status changed from Feedback to In Progress
- Priority changed from Urgent to High
- Target version changed from 0.5.0 to 0.6.0
We've gone pretty far with this and am considering the task "done" for 0.5. Rather than re-rolling a ticket, i'm going to push the target version here and push the due data back
Updated by Andrew Mallis about 1 year ago
- Assignee deleted (
Trevor Twining) - Priority changed from High to Normal
- Target version changed from 0.6.0 to 1.0
- % Done changed from 0 to 80
Updated by Andrew Mallis 11 months ago
- Status changed from In Progress to Resolved