|
1 | 1 | --- |
2 | | -title: "What is Stack-Breakthrough." |
| 2 | +title: "What is Stack-Train." |
3 | 3 | layout: post |
4 | | -author: "Michael Rose" |
5 | | -author-url: "https://github.com/mrose" |
| 4 | +author: "Levis A" |
| 5 | +author-url: "https://github.com/alevis" |
6 | 6 | categories: category |
7 | 7 | --- |
8 | 8 |
|
9 | | -You’ll find this post in your `_posts` directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run `jekyll serve`, which launches a web server and auto-regenerates your site when a file is updated. |
| 9 | +Stack-Train is a guided progression through a modern tech stack, where each “stop” represents a tool, language, or concept you learn in sequence. |
10 | 10 |
|
| 11 | +### 1. Learning path / roadmap |
| 12 | +A sequence of technologies grouped by layer: |
| 13 | +Frontend (HTML, CSS, JavaScript, frameworks) |
| 14 | +Backend (servers, APIs, databases) |
| 15 | +Dev tools (Git, CLI, deployment) |
| 16 | +Organized to reflect how developers typically grow skills step-by-step |
11 | 17 |
|
12 | | -To add new posts, simply add a file in the `_posts` directory that follows the convention `YYYY-MM-DD-name-of-post.ext` and includes the necessary front matter. Take a look at the source for this post to get an idea about how it works. |
13 | 18 |
|
| 19 | +### 2. Stack-oriented thinking |
14 | 20 |
|
15 | | -{% highlight ruby %} |
16 | | -def print_hi(name) |
17 | | - puts "Hi, #{name}" |
18 | | -end |
19 | | -print_hi('Tom') |
20 | | -#=> prints 'Hi, Author' to STDOUT. |
21 | | -{% endhighlight %} |
| 21 | +The site emphasizes: |
22 | 22 |
|
23 | | -<!-- |
24 | | -[jekyll-docs]: http://jekyllrb.com/docs/home |
25 | | -[jekyll-gh]: https://github.com/jekyll/jekyll |
26 | | -[jekyll-talk]: https://talk.jekyllrb.com/ |
27 | | ---> |
| 23 | +Understanding how different layers of a tech stack connect |
| 24 | +Learning tools in logical order instead of randomly |
| 25 | +Seeing development as a system, not isolated skills |
| 26 | + |
| 27 | +### 3. Lightweight, static design |
| 28 | +Very simple UI (typical of GitHub Pages) |
| 29 | +Likely built with plain HTML/CSS or a lightweight static generator |
| 30 | +No heavy interactivity—focus is on content, not features |
| 31 | + |
| 32 | +### Purpose |
| 33 | + |
| 34 | +A self-learning guide for aspiring developers |
| 35 | +A reference map of technologies used in modern web development |
| 36 | +A personal or community-curated curriculum |
| 37 | + |
| 38 | +- Not a product or framework |
| 39 | +- Not a full tutorial platform |
| 40 | +- Instead: a structured roadmap for learning full-stack development |
0 commit comments