github/Fabric
1
1
Fork 0
mirror of https://github.com/danielmiessler/Fabric.git synced 2026-01-09 14:28:01 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update README

Browse Source
This commit is contained in:
John
2025-01-01 02:48:15 -05:00
parent c107cce22e
commit 2aebc84c66
4 changed files with 5 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
web/README.md
View File

@@ -9,7 +9,7 @@ The goal of this app is to not only provide a user interface for Fabric, but als
## Installing
It can be installed by navigating to the `web` directory and using `npm install`, `pnpm install`, or your preferred package manager. Then simply run `npm run dev` or your equivalent command to start the app. *You will need to run fabric in a seperate terminal with the `fabric --serve` command.*
The app can be run by navigating to the `web` directory and using `npm install`, `pnpm install`, or your preferred package manager. Then simply run `npm run dev`, `pnpm run dev`, or your equivalent command to start the app. *You will need to run fabric in a seperate terminal with the `fabric --serve` command.*
A production build is available as well. You can run it with `npm run preview` or using your preferred package manager
@@ -17,7 +17,11 @@ A production build is available as well. You can run it with `npm run preview` o
When creating new posts make sure to include a date, description, tags, and aliases. Only a date is needed to display a note.
### If you choose to use Obsidian along side ths app
You can design and order your vault however you like, though a `posts` folder should be kept in your vault to house any articles you'd like to post.
### Production
The production build has not been setup to run on any particular provider.

21
web/SECURITY.md
View File

@@ -1,21 +0,0 @@
# Security Policy
## Supported Versions
Use this section to tell people about which versions of your project are
currently being supported with security updates.
| Version | Supported |
| ------- | ------------------ |
| 5.1.x | :white_check_mark: |
| 5.0.x | :x: |
| 4.0.x | :white_check_mark: |
| < 4.0 | :x: |
## Reporting a Vulnerability
Use this section to tell people how to report a vulnerability.
Tell them where to go, how often they can expect to get an update on a
reported vulnerability, what to expect if the vulnerability is accepted or
declined, etc.

39
web/src/lib/content/posts/2024-12-29-21-14-44.md
View File

@@ -1,39 +0,0 @@
---
title: How to Think Like a Developer
aliases: Guide to Thinking Like a Developer
description: Development Thinking. A guide to help prepare the mind.
date: 2024-12-29T21:14:44.150Z
tags:
- "inbox"
- "note"
updated: 2024-12-29T21:14:44.150Z
author: User
---
> [!Note]
> **This guide provides a framework for developing a developer's mindset through practical steps and project work.**
1. **Introduction**: Many new developers feel lost after learning the basics. It's important to recognize that learning takes time and practice.
2. **Disillusion**: Tutorials can set unrealistic expectations. Avoid comparing yourself to others; focus on your own progress.
3. **Projects**: Create a to-do app as a foundational project to practice coding skills.
4. **Breaking Down Problems**: Approach problems systematically. Break them down into manageable components, such as creating, reading, updating, and deleting (CRUD) tasks.
5. **Getting Started**: Use tools like CodePen or Github Codespaces to experiment without the pressure of setting up a local environment.
6. **Understanding User Input and Data Structures**: Learn to capture user input effectively and think in terms of data structures—like an array of todo objects.
7. **Wishful Thinking and Pseudocode**: Use "wishful thinking" to conceptualize functions before coding, and write pseudocode to outline your logic.
8. **CRUD Operations**: Implement features to create, update, and delete todos, focusing first on functionality before refining the code.
9. **Styling**: Styling should be the last thing to work on.
10. **Finding Project Ideas**: Explore resources for project ideas to build confidence and experience.
11. **Reading Documentation and Seeking Help**: Embrace documentation as a learning tool, and don't hesitate to ask for help in communities.
12. **Conclusion**: Understanding comes from doing. Break tasks down, practice consistently, and focus on working code rather than perfection.
This guide should encourage developers to embrace the learning journey, build projects, and continuously seek knowledge and improvement.

5
web/src/lib/content/posts/test.md
View File

@@ -1,5 +0,0 @@
---
date: 2024-12-31
---
You only need a date to define a note. All other frontmatter is optional.