Skip to content

docs: add history page #904

Open
Solant wants to merge 8 commits into
feature-sliced:mainfrom
Solant:docs/history
Open

docs: add history page #904
Solant wants to merge 8 commits into
feature-sliced:mainfrom
Solant:docs/history

Conversation

@Solant

@Solant Solant commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

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

@github-actions

github-actions Bot commented Mar 9, 2026

Copy link
Copy Markdown
built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
pr-fsd ✅ Ready (View Log) Visit Preview aa03c94

@Gaic4o Gaic4o left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@Gaic4o
Gaic4o self-requested a review March 11, 2026 02:54
@Gaic4o

Gaic4o commented Jul 13, 2026

Copy link
Copy Markdown
Member

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.

@Gaic4o Gaic4o changed the title History page docs: add history page Jul 13, 2026
@Solant

Solant commented Jul 13, 2026

Copy link
Copy Markdown
Contributor Author

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.

@Gaic4o

Gaic4o commented Jul 18, 2026

Copy link
Copy Markdown
Member

Since the current title is History, I think readers who click on this document may expect to learn when FSD first emerged, how concepts such as FSD’s layers and segments were discussed and developed, and how it evolved into version 2.

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.

@Solant

Solant commented Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

Yeah, this is kind of an issue with this page. Previously it was named “Alternatives,” but it was comparing FSD to other “older” approaches, and this name didn't make sense. I tried to rename it to “History” instead to see what happens.

Do you think we can rename it? Something like:

  • Alternatives (well, I don't really like it, because those are not really alternatives)
  • History (as in “approach evolution history”, not the “FSD” history)
  • Comparisons (a new one, but it should be descriptive enough)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants