Spaces:
Sleeping
Sleeping
Create article_instructions.md
Browse files- article_instructions.md +69 -0
article_instructions.md
ADDED
|
@@ -0,0 +1,69 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Article Generation Instructions
|
| 2 |
+
|
| 3 |
+
## Writing Style Guidelines
|
| 4 |
+
|
| 5 |
+
1. **Voice**: Use a conversational yet professional tone
|
| 6 |
+
2. **Perspective**: Write in third person, but include first-person quotes from the interviewee
|
| 7 |
+
3. **Length**: Aim for 1500-3000 words
|
| 8 |
+
4. **Audience**: Other builders, founders, and project leaders who want to learn from real experiences, consider the readers may have worked for 20 years not learning new words and had left school since 8th grade, they want to contribute the community even with limited skills and knowledge
|
| 9 |
+
|
| 10 |
+
## Structure Template
|
| 11 |
+
|
| 12 |
+
### Title
|
| 13 |
+
- Make it compelling and specific
|
| 14 |
+
- Example: "How [Project] Solved [Problem] for [Users]" or "Building [Project]: From [Starting Point] to [Outcome]"
|
| 15 |
+
|
| 16 |
+
### Opening Hook (1-2 paragraphs)
|
| 17 |
+
- Start with the most compelling moment, challenge, or outcome
|
| 18 |
+
- Make readers want to know the full story
|
| 19 |
+
|
| 20 |
+
### The Spark (Background/Motivation)
|
| 21 |
+
- What problem did they notice?
|
| 22 |
+
- Why did they feel compelled to act?
|
| 23 |
+
- What was their unique perspective?
|
| 24 |
+
|
| 25 |
+
### The Journey
|
| 26 |
+
- Key milestones and turning points
|
| 27 |
+
- Major decisions with reasoning
|
| 28 |
+
- Challenges faced and how they were overcome
|
| 29 |
+
- Resources gathered (funding, people, tools)
|
| 30 |
+
|
| 31 |
+
### The Team
|
| 32 |
+
- How it formed
|
| 33 |
+
- Who joined and why
|
| 34 |
+
- How the team worked together and maintain momentum
|
| 35 |
+
- Roles and dynamics
|
| 36 |
+
|
| 37 |
+
### Building & Delivering
|
| 38 |
+
- How the project was developed
|
| 39 |
+
- Key technical or process decisions
|
| 40 |
+
- How they reached users
|
| 41 |
+
|
| 42 |
+
### Impact & Feedback
|
| 43 |
+
- User reception
|
| 44 |
+
- Measurable outcomes
|
| 45 |
+
- Unexpected results
|
| 46 |
+
|
| 47 |
+
### Lessons Learned
|
| 48 |
+
- What worked well
|
| 49 |
+
- What they'd do differently
|
| 50 |
+
- Advice for others
|
| 51 |
+
|
| 52 |
+
### Key Takeaways (Bullet points)
|
| 53 |
+
- 3-5 actionable insights readers can apply
|
| 54 |
+
|
| 55 |
+
## Formatting Rules
|
| 56 |
+
|
| 57 |
+
- Use markdown headers (##, ###) for sections
|
| 58 |
+
- Include relevant quotes in blockquotes (>)
|
| 59 |
+
- Use bullet points for lists and takeaways
|
| 60 |
+
- Bold key terms and important phrases
|
| 61 |
+
- Keep paragraphs short (3-5 sentences max)
|
| 62 |
+
|
| 63 |
+
## What Makes a Good Case Article
|
| 64 |
+
|
| 65 |
+
1. **Specificity**: Include concrete numbers, dates, names when available
|
| 66 |
+
2. **Honesty**: Don't shy away from failures or challenges
|
| 67 |
+
3. **Actionability**: Every section should have something readers can learn from
|
| 68 |
+
4. **Story Arc**: Build tension and resolution
|
| 69 |
+
5. **Human Element**: Show the emotions, doubts, and victories
|