web design
why taller tintor builds websites clients can update themselves
a website should adapt to your brand journey. when taller tintor builds websites in framer, cms collections can give clients a guided way to add blog posts, products, projects, publications, resources, or other recurring content after launch. the client updates the content, while the layout, structure, and brand system stay protected.
Jun 12, 2026
why taller tintor builds websites clients can update themselves
gaby s.
a website should keep growing after launch
many people think of a website as something finished: you design it, publish it, and move on.
in real life, businesses keep changing:
a new project appears,
a product needs to be added,
a blog post is ready,
a publication goes live,
a menu changes,
a resource needs to be shared.
the website has to keep moving with the brand.
this is where many clients start feeling stuck, if the website was built in a way that depends completely on the designer or developer, every small update becomes another message, another payment, and another waiting period. the content waits until someone else has time and the website slowly stops reflecting what the business is doing.
at taller tintor, this is one of the reasons we build websites with cms collections in framer when the project needs them. the goal is simple: the website should be professional, well designed, and useful after launch, and clients should be able to update the right parts themselves without touching the design.
what a cms collection does
a cms collection is an organized place for recurring content.
think of it as a structured drawer inside the website. each drawer has fields:
for a blog post, those fields might be title, date, cover image, author, category, summary, and full text.
for a portfolio project, they might be project name, location, year, images, description, status, and related services.
for a publication, they might be title, link, date, source, topic, and excerpt.
taller tintor designs the website, defines the layout, creates the fields, and connects those fields to the places where the content should appear. after that, the client can go into the cms collection and add or edit the information there.
the client is editing content, while the website keeps the structure intact (spacing, hierarchy, layout, image rhythm, and brand rules stay guided by the system that was already designed).
that difference matters, as editing content should feel practical. changing the website structure should stay intentional.
what clients can update themselves
cms collections are useful when a business has content that will keep growing over time. that can include blog posts, products, portfolio projects, research, publications, resources, team members, events, faqs, press mentions, testimonials, or service examples.
the exact setup depends on the business. taller tintor does not build the same cms structure for every project, we look at the content the client has today, the content they may need later, and the way each item should appear across the site.
the questions are practical:
what content will change often?
who will update it?
what information does each item need?
where should that information appear?
what should stay protected?
what should be easy to edit?
when those answers are part of the website strategy, the cms becomes part of the design system. it supports the way the business will use the site after publishing.
why guided editing protects the design
a website can become messy when it was never built for client-side updates. the client still needs to add information, so they try to make the site work with whatever tools they have. over time, the spacing changes, the image sizes become uneven, the typography shifts, and the page starts feeling disconnected from the original design.
this is common, and it usually comes from a useful need. the client wants the website to keep growing. the system simply was not planned for that use.
cms collections help by giving the client the right amount of flexibility: they can add the information they need, inside fields that were already designed for that type of content. they do not have to rebuild a page, copy sections, adjust layouts, or guess where something should go.
the boundaries make the system easier to use. the client knows where the title goes, where the image goes, where the description goes, and where the link goes, while the website knows how to display that information.
why taller tintor uses framer for csm collections
taller tintor builds websites in framer because it allows design and cms structure to work together. the visual experience can be carefully designed, while editable content areas give clients a practical way to keep the website active.
this matters for clients who want a professional website and also want to keep updating it themselves. they can add a new post, product, project, or publication through the cms without entering the visual layout. the design stays in place. the content keeps growing.
this approach also reduces unnecessary maintenance. there will always be moments when a client needs support, especially for structural changes, new sections, or bigger strategy decisions. still, regular content updates should not require a full design intervention every time.
training is part of the handoff
a website handoff should teach the client how the site works.
at taller tintor, training happens after the website is built and before publishing. we walk the client through the cms collections, the editable fields, and the update process. the point is for the client to understand where to add information and how that information will appear on the live site.
there is also a follow-up after launch. once the website is live, new questions can appear because the client is using the system in real conditions. that follow-up helps answer doubts and support the transition from “this is the new website” to “this is how i keep using it.”
the client should know what they can manage themselves and when it makes sense to ask for support.
proyecto raíz: a website designed for evolving work
proyecto raíz is a good example of why cms planning matters.
the website presents a landscape practice with a body of work that keeps expanding. its “territorios” section gathers projects across categories such as executed, under construction, in process, and conceptual. its “semillas” section presents investigations and processes that feed each territory. the site also includes a methodology section that explains the process behind the work.
for a project like this, the website needed to function as more than a fixed presentation. it had to hold portfolio work, research, publications, and process-based content without making every update feel heavy.
taller tintor built cms collections around the recurring types of information proyecto raíz needed to keep feeding. that meant the client could add new content through structured fields instead of manually rebuilding pages. once an item was added, the site could show that content in the places where it belonged.
this is especially useful when the same piece of content needs to appear across different pages or sections, the client can feed the cms once, and the website can distribute the information according to the structure already designed.
the result is a website that can keep receiving new work and new thinking while the visual rhythm stays intact.
what can happen without an editable system
when a website has no guided way to grow, one of two things usually happens:
the first is that content stops. the client has projects, posts, products, or updates to share, although publishing them takes too long or depends on someone else’s schedule. the website begins to feel outdated, even when the business is active.
the second is that the client edits areas that were never meant to be edited. this can break the rhythm of the site. a page that once felt well designed starts to feel improvised.
both situations can be avoided when future use is part of the website strategy. before designing, the team needs to understand what the client will keep adding, how often they will add it, and how comfortable they feel managing content.
how to know if your website needs cms collections
your website may need cms collections if you publish the same type of content often. this could be articles, projects, products, events, resources, press mentions, publications, or case studies.
cms collections are also useful when content needs to appear in more than one place. a project might appear on the home page, inside the portfolio, and in a related work section. a publication might appear in a research page and also in a featured section. without a cms, those updates may need to be repeated manually.
they are also useful when the business is still evolving. many brands do not need every future page on day one. they need a website that can receive new pieces over time.
questions to ask before building your website
before starting a website, ask:
what content will change often?
who will update the website?
what information does each content type need?
where should new content appear?
what parts should stay guided?
what should be easy to edit?
will the site need posts, products, projects, publications, or resources later?
how much support will the team need after launch?
these questions shape a better website brief. they help the site respond to the way the business will use it, instead of only focusing on how it should look on launch day.
a website should adapt to the brand journey
a website is more useful when it supports what happens after publishing.
when editable content is planned from the beginning, the client can keep the site active. the brand can keep growing its content. the design system can stay intact. regular updates become easier because they happen inside a structure built for that purpose.
that is why taller tintor builds websites clients can update themselves. the work is not only about launching a site that looks finished. it is about building a system the client can keep feeding as the brand continues to move.
faq: updating your own website after launch
what does it mean to update my website myself?
it means you can make changes to certain information without needing the person who built the website to do it for you. depending on how the site is built, you may be able to add products to your shop, upload new projects to your portfolio, publish blog posts, add resources, update publications, add testimonials, or edit recurring information through a guided system.
what is a cms collection?
a cms collection is a structured content area inside the website. think of it as the backstage of a specific type of content, where you add or edit the information in fields, and the website shows that information using the design that was already created.
can i update my website without changing the design?
yes, with cms collections. you can add or edit the information, and the way it looks on the website stays the same. the design, layout, spacing, and visual rhythm are already connected to the collection.
what parts of the website should i be able to edit?
this depends on what your website needs, although common editable areas include product photos and details, portfolio projects, blog posts, events, resources, publications, faqs, press mentions, testimonials, team members, service examples, locations, menus, and case studies.
what parts should stay guided by the designer?
anything related to design, layout, code, or structure should stay guided. in simpler terms: anything that changes how the website looks should be handled with more care, because those decisions affect the full experience of the site.
do i need technical knowledge to update cms content in Framer?
no. you only need to understand what each field is for and how to organize the new information so it fits the structure. once you know where each piece goes, updating cms content becomes much easier to manage.
will taller tintor teach me how to update the website?
yes. taller tintor teaches clients how to edit their cms collections before the website is published, so they know how to add, edit, and organize content once the site is live.
what happens if i need help after launch?
you can reach out with your questions. if the question is related to cms updates, taller tintor can give you a refresh lesson or answer the new doubts that came up while using the site. if the request involves building or editing layout, design, structure, or code, taller tintor quotes that separately.
how do i know if my website needs cms collections?
start by asking whether there is anything on your website that you or your team will need to update regularly. if you will keep adding posts, products, projects, publications, resources, events, or similar content, cms collections can make the site easier to maintain.
can a professional website still be easy for the client to update?
yes. that is why taller tintor loves cms collections. they allow the website to look professional and still give the client a practical way to keep feeding it with new content
