seeddb.applegarthlabs.com
Open in
urlscan Pro
2607:ff18:80:4::4a02
Public Scan
URL:
https://seeddb.applegarthlabs.com/
Submission: On June 02 via automatic, source certstream-suspicious — Scanned from DE
Submission: On June 02 via automatic, source certstream-suspicious — Scanned from DE
Form analysis 1 forms found in the DOM
<form class="form-inline">
<div class="input-group flex-fill">
<input class="form-control nav-search-field" type="search" placeholder="Search" aria-label="Search">
<div class="input-group-append">
<button class="btn btn-outline-success" type="submit">
<i class="fas fa-search" aria-hidden="true"></i>
</button>
</div>
</div>
</form>Text Content
* Menu
Browse... Packets Varieties Cultivars Families Random My Lists Plants Beds
* SeedDB
* Sign in
* SeedDB
* Browse
Packets Varieties Cultivars Families Random
*
* Lists
Plants Beds
* Sign in
CARROT
Cultivar Daucus carota spp. sativus
GARDEN VITALS
* Soil Light, friable, sandy
* Sun Part sun, 6-8 hours
* Water Keep moist
* Spacing 6-8 in
TAXONOMY
* Family Apiaceae
* Order Apiales
* Group Eudicots
VARIETIES
* Dragon
* Purple
* 13 more...
ABOUT THE CARROT
Why orange? It's worth asking ourselves why a carrot should be orange. Or
rather, why it would care what it looks like. It spends most of its life hidden
just underground in the darkness, and is only seen in its last moments, as a
gatherer or critter pulls it up. Indeed, when humans were introduced to the wild
carrot it was a small, white, and woody root. Cultivators in the Netherlands
developed the carrot to be bigger, tastier and crunchier over time, and also
bred it to be orange. The domesticated carrot became so distant from its wild
ancestors that it was given its own subspecies, Daucus carota spp. sativa.
Sativa here means delicious! But... why orange? Because orange is awesome and
eye-catching! This is the same place where the tulip craze started - breeding
root vegetables into crazy colors is par for the course.
Eyesight booster? Not quite. During World War 2 Britain began to circulate a
myth about its pilots: they had such good eyesight because they ate a high
volume of carrots. This was a cover story to explain their pilots' uncannily
precise eyesight and their ability to locate seemingly invisible enemy forces,
in an attempt to hide their new invention, radar! The myth correlating carrots
to good eyesight has stuck around, but it isn't a particularly harmful one.
While carrots have some sugar, they are also high in many vitamins and minerals
and are a popular healthy snack.
Roots. It's also worth mentioning that baby carrots aren't just small carrots -
they're rounded down portions of carrots which weren't shapely or attractive
enough to sell whole. Pulling a young carrot out of the ground reveals something
that looks much like an adult carrot. Mature carrots have a lot of side roots,
so they may look a bit hairy when pulled out of the ground. It's those side
roots that nourish the carrot, as well as its taproot (the main body of the
carrot). The taproot grows down much farther than the bulk of the carrot, and
the full reach of the carrot can be triple the size of its main bulk!
SEEDDB WEBSITE PLAN
PLANNING
Target market: Gardeners.
Goal: Serve as a great portfolio piece. Provide a way for me to channel writing
skills as well as keep my Web design skills sharp. Maybe make a little money via
donations, and maybe even partner with a seed company.
Information needed: Quick and snappy, but very consistent and atomic, plant
facts. Good plant pictures. Good articles to keep interest for bored browsers.
Information organization: Make plant facts very accessible for gardeners to use
when out working in the garden, they have their gloves on and are ready to go.
Let them compare plants. Provide articles and photos later on for extended
information.
LANDSCAPE
Essential front-end features
* Quick Plant Facts driven by a database — Quickly answer question "CAN I plant
this?"
* Comparison feature — Quickly answer question "WHICH should I plant?"
* Advanced search — Quickly answer "Given scenario X, WHAT can I plant?"
* Photo gallery
* Ability to set zone and get zone-specific info
* A way to write articles when I wish to
* Ability to share and link pages easily, with a very clean URL structure to
boot
Back end features
* SSL of course
* Solid URL rewriting scheme
* Perhaps an edge caching service
* Data structure that can mutate from initial single-payload (one .json)
dataset to DB call structure
* Future room to partner shopping/list features with a seed co. and exchange
data (product stock, availability, images, etc)
Cool-to-have features
* User accounts with
* Wish lists
* Zone information
* User submitted photos, comments
* User requests to change/correct/update data
* Front end placeholder for partnering with a seed co.
* Additional articles explaining terms that are not linked to a certain kind of
plant
* API for other gardeners to use with a "data reveal" mode (hover over data to
see the entity name, like hovering over Carrot displays "Item.CommonName"
AESTHETICS
What should it look like based on target market? Simple but natural. This can be
hard to balance, simple web sites often look very technical. Dark font on light
backgrounds. Very simple mobile view for gardeners on the go, often in direct
sunlight (avoid low contrast at all costs).
Graphical content: The site should incorporate plant photos wherever possible,
but it is not possible to do so often. The header should be an eye catching
photo; but other than that things should stay pretty simple and photos should be
in their own photo section, and perhaps one or two in the article section. Look
for low cost stock options.
Above the fold: On mobile, quick plant facts should always be first (CAN I plant
this?) with links to quickly make other decisions. Of course, buying would be
next, where possible. In the desktop layout, the first 3 blocks should be Quick
Plant facts, Purchase (front and center), and links. The Amazon Effect means
that users will probably look at the middle item in the first row first, so it
should be the buy link, with other options to interact around it. If you are
having square-ish ads, put them as the first block on the desktop site because
it will often be skimmed over visually. Lists of varieties and the photo gallery
would come later, followed by other database content like taxonomy, and finally,
the article. After the article you could follow up with more links to other
things... previous/next vegetable, other vegetables in the family, varieties,
cultivars and so on.
Responsive design: Mobile is so important for this that it should probably be
done first. But the site must look really nice when expanded to full resolution
too.
Sources of inspiration: Gardenate (maybe)... not a lot else out there.
NAVIGATION
1. Home
1. Article of the Day
2. Browse
1. Families
2. Cultivars
3. Varieties
4. Packets
5. Articles
6. Random
3. Browse by Family
1. Umbellifers
2. Solanaceae
3. ... etc ...
4. Look Up
1. Compare Data
2. What Can I Grow?
5. (Account)
1. (My Lists)
2. (My Contributions)
6. (Suggest a Change)
Footer content
yep
Stuff
* First item
* Second item
* Third item
More stuff
First link
Second link
Third link