Skip to content

Commit 21bace8

Browse files
authored
Merge pull request creativecommons#291 from krysal/krysal-post2
Add second post of CC Legal Database series
2 parents c34775f + 48085e6 commit 21bace8

File tree

2 files changed

+35
-0
lines changed

2 files changed

+35
-0
lines changed
Loading
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
title: CC Legal Database: Design
2+
---
3+
categories:
4+
cc-legal-database
5+
product
6+
outreachy
7+
---
8+
author: krysal
9+
---
10+
series: outreachy-may-2020-legal-database
11+
---
12+
pub_date: 2020-06-09
13+
---
14+
body:
15+
Finishing the third week since the project started (for context see this [first post](/blog/entries/legal-database-a-new-beginning/)), so the design phase is almost over and a new site look is out of the oven. The focus on these weeks was to draw the mockups for the user-facing parts of the site, integrating styles of CC Vocabulary and to get the data model for the database.
16+
17+
### Visual Styles
18+
The intention was to keep the content that is already present but improve its distribution and access by users. For this, the main menu was changed to provide direct links to listing of Cases and Scholarships. The old "Countries" page was removed and replaced by a more granular division by legal resource, so this data will be shown separately.
19+
20+
The final look for the home site is as follows.
21+
22+
<div style="text-align: center;">
23+
<figure>
24+
<img src="cc-caselaw-home.png" alt="New CC Caselaw Home Mockup" style="border: 1px solid black">
25+
<figcaption>New Home page design with Vocabulary.</figcaption>
26+
</figure>
27+
</div>
28+
29+
I made use of as many Vocabulary components as possible, like header, footer and table. This way is easier to keep consistency between CC products and to develop the frontend part of the site because those components are already built and tested, though some will require certain modifications (e.g. card link with a search input), and some others have to be created from scratch, like a pagination component that is actually now required for two sites.
30+
31+
### Data Model
32+
33+
The second main task I worked on was coding the models on Django, which is in charge of creating the database schema through migrations. For this, I had to review the sources of information (CSV files, sheets, forms) and how they are used. The key point here is to keep constant communication with staff who are more involved in the *business case*.
34+
35+
Several iterations were required for each task as well as some researching, and while the engineering and design work never seems to end, this makes good foundations to continue and advance.

0 commit comments

Comments
 (0)