docs: add history page #904
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
|
I re-read the document, and overall it's really well organized. It helped me understand the context in which FSD emerged. I do have one thought on the direction I'd like to share though. Right now each methodology section reads as though the approach has certain downsides or problems, and therefore FSD is better in that regard. But the way I see it, frontend architecture is an ecosystem that has evolved incrementally by building on and improving previous methodologies, and FSD itself came out of that same flow, learning from and refining what came before. So rather than highlighting each methodology's shortcomings to emphasize FSD's superiority, I think it might be better to show the difference in context. For example, we could frame it as this methodology being designed for a certain context such as backend or design systems, and FSD bringing that idea into the frontend context in a different way. That way we can respect the other methodologies while still explaining FSD's choices, and more importantly, I think it's simply a more accurate description. |
|
From my perspective, there is nothing particularly wrong in being correct and cool and superior, but I see your point. I updated some of the most superior points, and I'll give it a think for a bit in case I come up with something better (that doesn't require adding a ton of text) Let me know if I got it right now. |
|
Since the current title is However, the current document seems to focus more on how FSD was influenced by existing architectures and methodologies, and how it differs from each of those approaches, rather than on the history of FSD itself. Because of that, I feel there is a slight mismatch between the title and the actual content of the document. |
Background
I updated /docs/about/alternatives/ page to more about history, keeping it in line with original content.
Changelog
Updated /docs/about/alternatives/ page, URL is the same