<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Organizing &#8211; Fountn</title>
	<atom:link href="https://fountn.design/resource-tags/organizing/feed/" rel="self" type="application/rss+xml" />
	<link>https://fountn.design</link>
	<description>Curated design resources. No clutter. Just flow.</description>
	<lastBuildDate>Tue, 30 Dec 2025 16:53:08 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.1</generator>

<image>
	<url>https://fountn.design/wp-content/uploads/2024/03/cropped-Default-150x150.png</url>
	<title>Organizing &#8211; Fountn</title>
	<link>https://fountn.design</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Naming Guidelines for UX &#038; Design Systems (GoodPractices.design)</title>
		<link>https://fountn.design/resource/naming-guidelines-for-ux-design-systems-goodpractices-design/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Tue, 30 Dec 2025 16:53:07 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=17003</guid>

					<description><![CDATA[Naming Guidelines on GoodPractices.design is a structured resource that outlines principles and examples for naming conventions in UX and product design. It covers how to choose clear, intuitive names for design system elements, components, tokens, and UI patterns to reduce ambiguity and improve team alignment. The guide emphasizes readability, predictability, and meaningful hierarchy in names [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Brand Hub: Centralize Digital Brand Assets</title>
		<link>https://fountn.design/resource/brand-hub-centralize-digital-brand-assets/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Sat, 07 Jun 2025 07:00:35 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=13870</guid>

					<description><![CDATA[Lingo’s Digital Brand Hub is a centralized platform designed to consolidate all brand assets, guidelines, and documentation in one place. The goal is to streamline team workflows by eliminating redundant asset requests and empowering collaborators to access the files they need without delays. Teams can organize kits for branding, fonts, icons, photography, and more—all structured [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Playbook &#8211; Organize your creative files</title>
		<link>https://fountn.design/resource/playbook-organize-your-creative-files/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Tue, 03 Jun 2025 08:11:17 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=13733</guid>

					<description><![CDATA[Playbook is a centralized media library platform designed to help creative professionals and teams manage their visual assets more efficiently. Positioned as an all-in-one solution, the tool consolidates a wide variety of media types—including photos, videos, design files, and documents—into a single, easy-to-navigate workspace. With features such as AI-powered search, collaborative boards, and file sharing, [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Styles &#038; Variables Organizer</title>
		<link>https://fountn.design/resource/styles-variables-organizer/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Tue, 06 May 2025 06:29:04 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=12334</guid>

					<description><![CDATA[Styles &#38; Variables Organizer is a Figma plugin developed by Chemu Wu that helps designers efficiently manage and audit design tokens within their files. The plugin provides a centralized interface to analyze and link values—such as color, number, text, and effect variables—to their corresponding styles or variables. It supports both traditional styles (e.g. text, fill, [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Design System Organizer</title>
		<link>https://fountn.design/resource/design-system-organizer/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Wed, 23 Apr 2025 08:00:22 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=10864</guid>

					<description><![CDATA[The Design System Organizer is a Figma plugin developed by Floweare, designed to streamline the management and organization of design systems within Figma. It offers a suite of tools aimed at simplifying the handling of components, styles, and variables, making it particularly useful for teams dealing with extensive design libraries. ￼ Key functionalities include the [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>How we Organize Figma Projects and Files On Our Design Team</title>
		<link>https://fountn.design/resource/how-we-organize-figma-projects-and-files-on-our-design-team/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Sun, 20 Apr 2025 07:38:01 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=10586</guid>

					<description><![CDATA[Lee Munroe, VP of Design at OneSignal, shares his team’s approach to organizing Figma projects and files to enhance collaboration and efficiency. Recognizing that organization needs vary based on team size and structure, Munroe emphasizes the importance of consistency and clear navigation as teams grow and more stakeholders engage with design files. The OneSignal design [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>How to improve your design process with copy docs</title>
		<link>https://fountn.design/resource/how-to-improve-your-design-process-with-copy-docs/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Wed, 19 Feb 2025 09:24:05 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=8276</guid>

					<description><![CDATA[Andrea Drugay discusses the use of copy documents to enhance collaboration between designers and writers. A copy doc is a shared document that combines design elements and written content, allowing teams to work together more effectively. Drugay suggests creating a template for copy docs to standardize the process and improve efficiency. Andrea emphasizes the importance [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>The Microcopy Canvas</title>
		<link>https://fountn.design/resource/the-microcopy-canvas/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Mon, 17 Feb 2025 12:27:01 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=8221</guid>

					<description><![CDATA[Jane Ruffino’s The Microcopy Canvas offers a structured framework for writing clear and purposeful microcopy in digital products. The framework helps teams create content that aligns with user needs by considering context, emotional state, and specific use cases. It emphasizes defining the target audience, identifying the goal of the copy, and evaluating its effectiveness, ensuring [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Work together to make the words work</title>
		<link>https://fountn.design/resource/work-together-to-make-the-words-work/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Mon, 17 Feb 2025 12:25:38 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=8219</guid>

					<description><![CDATA[Jane Ruffino’s article explores the importance of collaboration between designers and writers in shaping user experiences. She emphasizes that content strategy should be integrated early in the design process to create more coherent and user-friendly products. The article highlights common challenges that arise when teams work in silos, leading to inconsistent messaging and disjointed interfaces. [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Why do they ignore my awesome design documentation?</title>
		<link>https://fountn.design/resource/why-do-they-ignore-my-awesome-design-documentation/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Thu, 13 Feb 2025 10:47:29 +0000</pubDate>
				<guid isPermaLink="false">https://fountn.design/?post_type=resource&#038;p=8142</guid>

					<description><![CDATA[Slava Shestopalov examines why design documentation is often ignored and how designers can make it more effective. The article highlights common pitfalls, such as static, too-detailed, or disconnected documentation from real workflows. Shestopalov emphasizes the need for regular updates, clear structure, and making documentation more accessible and relevant to users. He also discusses how fostering [&#8230;]]]></description>
		
		
		
			</item>
	</channel>
</rss>
