Can you keep a substantial website going without frameworks or libraries?

November 18, 2026 5 answers
Asked by _c92~zeldriva.6

I'm curious about maintaining a site from scratch as it grows beyond static pages into accounts, articles, comments and forums. Is that a practical way to work long term, or does the maintenance become too much?

Answers

q.263+torvexa

Yes, it's possible. A site doesn't need a framework just because it has accounts or stores data. You can add features gradually as the content calls for them rather than planning the entire system up front.

That can be a good fit for a project where coding is only part of the work and you enjoy having control over the implementation. Possible doesn't mean effortless, though. The code you write is also code you have to maintain.

6r+gobletspindle_418:

Incremental development isn't unique to a from-scratch site, either. You can build a feature at a time with a framework too.

Reply to this answer
r.839~mosaiccrank

For a commercial project, I'd look hard at what you're spending time recreating. Established frameworks and libraries can provide tested solutions for common problems, leaving more time for the features that make the site useful.

That doesn't make every dependency worthwhile. It does mean avoiding all of them has a cost, especially when someone else eventually needs to understand and maintain the code.

Reply to this answer
_j63+vexnari.4

Accounts and public comments are where I'd get cautious. Authentication, permissions, input handling and abuse prevention all need attention. Writing those pieces yourself doesn't guarantee either better security or worse security, but it does put the responsibility for reviewing and updating them on you.

_c92~zeldriva.6:

That makes sense. Having fewer dependencies wouldn't mean there are fewer things to keep secure.

Reply to this answer
n.483~bracketmixer

There are two different questions here: is it useful for learning, and is it the fastest way to deliver a site? Building the pieces yourself can teach you a lot about how they fit together. That doesn't necessarily make it the best choice when time or budget is tight.

Reply to this answer
8e!parcelspindle_574

Even for a mostly static site, think about the content workflow. Shared page elements and writing formatting directly in HTML can get tedious as the number of pages grows. A static site generator can handle templates and simpler content editing if that's the part slowing you down.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions