-
Notifications
You must be signed in to change notification settings - Fork 193
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #460 from alexpricedev/feat/link-components-attrs
feat(components): added support for all anchor attrs
- Loading branch information
Showing
3 changed files
with
94 additions
and
57 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,25 +5,30 @@ The draft looks good and covers the key aspects, but let's enhance it to better | |
First and foremost: Thank you for helping make web development simpler and more standards-focused! ❤️❤️ | ||
|
||
## Writing and Sharing | ||
|
||
The most valuable contribution right now is spreading awareness about standards-first development. Write blog posts, create demos, or share examples that showcase the power of modern web standards. Show how native browser capabilities can replace complex framework abstractions. | ||
|
||
Focus especially on: | ||
|
||
- How modern CSS enables sophisticated design systems | ||
- The untapped power of semantic HTML | ||
- Progressive enhancement through vanilla JavaScript | ||
- Real-world examples of framework complexity vs web standards simplicity | ||
|
||
## Community Support | ||
|
||
Help fellow developers discover the elegant simplicity of standards-first development. While I (Tero Piirainen, product lead) focus intensely on the core engineering, the community's guidance is essential. Answer questions, suggest solutions, and share your experiences. | ||
|
||
## Bug Fixes | ||
|
||
When fixing bugs, always include a test case that demonstrates both the issue and the solution. This helps maintain the codebase's minimalist nature while ensuring reliability. | ||
|
||
## Feature Proposals | ||
Nue has a clear vision: take modern web standards to their absolute peak. Before implementing any new feature, no matter how small, let's discuss how it aligns with this goal. The framework's power comes from ruthless simplicity - every addition must justify its existence. | ||
|
||
Nue has a clear vision: take modern web standards to their absolute peak. Before implementing any new feature, no matter how small, let's discuss how it aligns with this goal. The framework's power comes from ruthless simplicity - every addition must justify its existence. | ||
|
||
## Development Philosophy | ||
|
||
Nue's development style might surprise those coming from traditional JavaScript projects. For engineers steeped in TypeScript, dependency injection, and "enterprise patterns", the codebase might even look stupid or feel like a toy project at first glance. This reaction reveals a fundamental divide in how we think about web development. | ||
|
||
While most codebases optimize for type safety, abstraction layers, and "proper engineering practices", Nue pursues radical minimalism. We strive to make each line of code meaningful through its functionality and clarity. The goal is to figure out what's truly needed (and only that) and find out the cleanest way to implement it. | ||
|
@@ -34,9 +39,8 @@ Or take view transitions: Nue's entire implementation fits in about 250 lines of | |
|
||
By working directly with web standards rather than building layers of abstractions, we strive to create systems that are both more powerful and easier to maintain. | ||
|
||
|
||
|
||
### Code Style | ||
|
||
Maintain the existing minimalist aesthetic: | ||
|
||
1. No semicolons - they add visual noise without value | ||
|
@@ -47,6 +51,7 @@ Maintain the existing minimalist aesthetic: | |
Nue avoids Prettier/ESLint as they would add 40MB of complexity. The `.prettierrc.yaml` provides sufficient consistency. | ||
|
||
### Testing | ||
|
||
```sh | ||
# Bun (recommended) | ||
bun install | ||
|
@@ -60,23 +65,39 @@ npm test | |
``` | ||
|
||
### Local Development | ||
|
||
#### Using Bun (recommended) | ||
|
||
```sh | ||
# Bun (recommended) | ||
# Clone the Nue repository | ||
cd your-projects-dir | ||
git clone [email protected]:nuejs/nue.git | ||
cd nue | ||
# Install dependencies | ||
bun install | ||
# Link the nuekit package | ||
cd packages/nuekit | ||
bun link | ||
cd my/nue/project | ||
# Link the nuekit package in your project | ||
cd your-projects-dir/your-nue-project-dir | ||
bun link nuekit | ||
# Serve the project using the local nuekit package | ||
nue | ||
nue build --production | ||
``` | ||
|
||
# Node | ||
#### Using Node | ||
|
||
```sh | ||
cd your-projects-dir | ||
git clone [email protected]:nuejs/nue.git | ||
cd nue | ||
npm install | ||
cd packages/nuekit | ||
npm link | ||
cd my/nue/project | ||
cd your-projects-dir/your-nue-project-dir | ||
npm link nuekit | ||
npm install --save-dev esbuild | ||
node $(which nue) | ||
node $(which nue) build --production | ||
``` | ||
|
||
Let's maintain this clear vision of simplicity and standards as we build something extraordinary together. | ||
Let's maintain this clear vision of simplicity and standards as we build something extraordinary together. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters