SKU: 57823204321
dracaena fragrans species

dracaena fragrans species Janet Craig Dracaena

Sale price$26.44 Regular price$29.38
Save 10%

Pay in installments of $7.34 with ShopPay, AfterPay and Klarna

Shipping Estimate
USA
  • USA
  • CAN

Ships within 48 hours · Estimated delivery Jul 28 - Aug 2

Promo Codes Available:

For Your Every Summer RSVP, with Code: SUMMER15

Description

dracaena fragrans species Janet Craig DracaenaDracaena fragrans 'Janet Craig' Dracaena fragrans 'Janet Craig' is one of the classic plain green corn plant cultivars, valued for broad, glossy, dark green leaves on upright woody stems. It carries deep green foliage in dense clusters at the cane tips. This cultivar has a steady plain green cane form. The leaves are sword shaped and slightly arching, while the stems create height as the plant matures. In a multi cane pot, 'Janet Craig' can look full,

Dracaena fragrans 'Janet Craig'

Dracaena fragrans 'Janet Craig' is one of the classic plain-green corn plant cultivars, valued for broad, glossy, dark green leaves on upright woody stems. It carries deep green foliage in dense clusters at the cane tips.

This cultivar has a steady plain-green cane form. The leaves are sword-shaped and slightly arching, while the stems create height as the plant matures. In a multi-cane pot, 'Janet Craig' can look full, green and established.

Plain dark foliage and classic canes

  • Foliage: Plain dark green leaves with a glossy surface and strong, clean outlines.
  • Stem habit: Upright woody canes topped with dense leaf clusters.
  • Growth pace: Slow to moderate indoors, with gradual cane development over time.
  • Placement: A strong green cane plant for bright to moderately lit interiors.

A classic corn plant frame

'Janet Craig' belongs to the Dracaena fragrans group often grown as cane plants. The plant starts with leafy heads and gradually reveals more stem as older leaves age away. This gives mature plants their familiar indoor tree silhouette while keeping most of the foliage concentrated near the top.

The accepted species is native to tropical Africa and grows as a shrub or tree, so indoor care should respect its woody structure. The roots need air as much as moisture, and the canes should not sit in a cold, wet pot. Stable warmth and a drying interval between waterings are more important than frequent attention.

Care for dark green Dracaena foliage

  • Light level: Bright filtered light gives the strongest growth, and 'Janet Craig' also handles moderate indoor light well. Protect the leaves from direct hot sun.
  • Watering: Water when the upper 40–50% of the mix is dry. Plain-green leaves do not mean the plant wants constant moisture.
  • Mix texture: Use a free-draining indoor plant substrate. A mix with mineral aeration helps prevent the heavy lower root zone from staying wet.
  • Warmth: Keep it in warm rooms, ideally above 18 °C. Sudden cold around the roots can trigger decline while the foliage still looks firm.
  • Air: Average humidity is usually enough. Keep the plant away from hot radiators if tips start crisping.
  • Feeding: Feed sparingly in spring and summer. Slow cane growth does not need strong fertiliser doses.
  • Repotting: Repot when roots are crowded or the plant dries too quickly after watering. Avoid jumping into an oversized pot.
  • Leaf care: Remove older yellow leaves and wipe dust from the wide leaf surface so the foliage keeps its deep sheen.

Signals to check before damage spreads

  • Brown tips: Check for dry spells, low humidity near heating, fluoride-sensitive foliage, or fertiliser salts. Flush the mix and consider filtered or rainwater.
  • Lower yellow leaves: One or two old leaves are normal. Several at once suggest overwatering, cold roots, or a sudden change in light.
  • Cane softness: Press gently near the base. Soft tissue means the plant may have stayed wet too long and needs immediate root-zone inspection.
  • Dull leaf surface: Dust can flatten the glossy look. Clean leaves gently rather than using leaf-shine products.
  • Small pests: Check the underside of leaves, cane nodes, and leaf bases for scale, mealybugs, or spider mites.

Pet safety with lower leaves

Because the broad leaves can sit within easy reach on younger canes, keep Dracaena fragrans 'Janet Craig' away from pets that chew plants. Fallen or pruned leaves should be removed from pet-accessible areas.

The name behind 'Janet Craig'

The genus name Dracaena comes from Greek drakaina, meaning female dragon. The species name fragrans refers to the sweetly scented flowers produced by mature plants. The cultivar name 'Janet Craig' identifies this long-used plain-green indoor selection.

Dracaena fragrans 'Janet Craig' has glossy dark foliage, sturdy canes and a classic indoor tree shape.

Shipping Notes
  • Free Standard Shipping on $100+ Orders to the USA.
  • Except Preorder products are shipped in 48 hours.
  • Delivery to the USA:
  1. Standard Shipping : 3-10 business days
  • If time is of the essence, please consider selecting expedited delivery for faster service.
Exchange/Return Notes
  • We offer a 30-day return/exchange service after receiving.
  • Final sale items are not eligible for returns or exchanges.
  • To process your return/exchange, please contact us at [email protected]
  • Please click here for more details>>> Return & Exchange Policy
SKU: 57823204321

Discover Niche Categories That Outsell dracaena fragrans species

Top-Converting Item to Boost Your Average Order

4.7 ★★★★★
Based on 29 reviews
Sort
Highest Rating
Newest First
Oldest First
Product Reviews
A
Amazon Customer
New York, US
★★★★★ 5
This is a "Go-To" for thinking about Cloud Challenges.
Format: Paperback
Delivering and managing fully realized applications in the cloud is different. Different approaches to classic engineering problems than traditional On Premise development and different ways of thinking through the problems of "always available" solutions. I've been in the software delivery business a long time, and with the cloud emerging, for good and ill: I understand the problems, but may be just a little set in my ways. I find this book helps me re-frame challenges in a way that aligns with the strengths of cloud computing. Solve the same problems faster, by thinking about them differently. I'm finding "97 Things Every Cloud Engineer Should Know" great for re-centering my expectations about Cloud Native development and deployment of assets. I started reading it cover to cover over the Christmas Holiday but now i just pick it up and look for the group of essays about exactly the problem I'm wrestling with. P.S. I'm heartened by the editors commitment to Black Lives Matter and Rule of Law. Mentioned only to balance the concerns from another review.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on January 24, 2021
C
Verified Purchase
cloud-learner
Charlottesville, US
★★★★★ 3
have some good contents but too general
Format: Paperback
The book covers some good points, but overall, it's too general.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on June 28, 2024
E
Verified Purchase
Engineer Dude
Belleville, US
★★★★★ 3
Why Politics in a Tech Book????
Format: Kindle
Well... I'm surprised to see the book blatently calls out its dedication to Black Lives Matter, which is in all caps so I assume it's referring to the political organization. It goes on to speak of 2020 being the year of an "awakening of injustices of systematic racism"... I thought I was buying a technical book??? Had I known this political bs was included I wouldn't have purchased it! However, I bought and I'm still reading it. If the politics goes away and the TECHNICAL content is good I'll update my review.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on December 13, 2020
P
Verified Purchase
PeaceBee
Belleville, US
★★★★★ 2
Not good use of time
Format: Paperback
It’s not clear who this book targets - neither experts nor novice will benefit. There are expert perspectives, only few of these are helpful, rest are too generic to be of any use. For instance the last entry is one an engineer who shares how she went from zero to expert in cloud engineering in six months but fails to mention a single resource or pathway for others to follow.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on April 2, 2022
N
Nilendu Misra
Los Angeles, US
★★★★★ 3
Uneven compendium of tips and insights, but still very useful
Format: Kindle, Format: Kindle
“In theory, theory and practice are the same. In practice, they are not" is why such bottom-up insights and lessons from the field are the fastest way to learn real life stuff. This series had a GREAT start with "Engineering Management" - I guess because it is way more subjective than Cloud Engineering and offered a variety of non-overlapping POVs. This one is a mixed bag, perhaps because "Cloud Engineering" was perceived amorphously by the authors. The scope was broad - from cloud-native (architecture), to cloud-ready (topology), to cloud-operations, to choosing tech (e.g., Lambda/serverless), to -ilities and economics -- it is like celebrating Halloween, Christmas and Labor Day together in a single long weekend. I would give it 4/+ stars if at least 25% of such a book was "superb", giving 3 because about 10% of the book is. That still leaves 10 solid insights or learning that would otherwise take many failures to learn. And failures, especially in this emerging domain of complexity, is VERY expensive. Would love to see more books like this. Let's summarize some key insights - -- Real-time visibility across the entire DevOps lifecycle is key to winning in cloud. -- Operations, especially operations at scale, is extremely hard. So, wherever possible, use Managed Services. -- Distinguish between "availability" and "uptime" and measure each separately, and concretely. -- In FaaS/Serverless, calling a function synchronously increases debugging complexity. -- Good code is like good joke - it needs no explanation. -- "Building your app or platform on top of the abstractions that a cloud provider gives you does not make the underlying layers stop existing. In many cases, it makes them even more important." That makes the failure modes LESS obvious than we were used to. Therefore having "extreme visibility" into your systems will help "separate the issues at the layer you're focused on from the fundamental system issues". i.e., just because what was under the hood is now even less visible, don't forget them. Many recent "cloud failures" have been in networking fault domains. -- Cloud is not optimized for replacing static infrastructures. -- Containers, service meshes and serverless jumpstart dev productivity but they also change the attack surface of apps and infra. -- "Number of containers that are alive for 10 sec or less has doubled to 22%". 73% of all containers live for 30 minutes or less. -- Adopt an "assume breach" stance for everything. Have a break-glass account. -- Ensure you have a thorough understanding of where and how secrets are secured. -- Grey failures (transient degradation of services) are often worse than complete crashes, since the latter have a short feedback loop. -- Resilience engineering has existed as a sub-discipline within safety sciences. We just recently started applying its concepts in technology. Resilience can be thought of as a "socio-technical system" with Robustness ("system X has property Y that is robust in sense Z to perturbation W"); Reliability (consistent operations or service levels); Rebound (ability to deal with a chaotic situation using structures developed AND deployed BEFORE the chaos). In other words, robustness protects systems against a SPECIFIC type of failure mode. When a system is robust in many dimensions, it approaches good resilience to failure. -- Resilience is something you "do", not something you "have". Resilience is a verb. -- Moving from one class of nines to the next is 10 times more expensive. -- Production System really means "system that someone else, anyone else, can hold you accountable for". -- Most common theme across incidents is that something, somewhere was surprising. -- Incidents are unplanned investments...your challenge is to maximize ROI. -- We used to think of scale in two dimensions - horizontal (more) and vertical (bigger). In cloud, think of "scale out" (when demands increase) and "scale in" (when demand decreases). -- Architecture diagram is also a map of failure modes. -- Async communication is a friend of Cloud Reliability. -- Test in production is a competitive advantage. The complexity of traffic patterns going through high-scale production systems is increasingly harder to reproduce in a controlled env. -- Hundreds of open issues is fine, but if the repo has gone months (or, years!) without a release, THAT is a warning sign. -- It is hard to write good tests for bad code. -- Platforms come and go. But first principles and patterns will always exist, because they are the ones and zeros.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on November 6, 2023

recommand products