Purple Flower

Prepare your CSV file

Make sure your file is exported as a "CSV" file, also known as a "Comma Separated Values" file. If you encounter any issues you'll want to verify your file is UTF-8 encoded and less than 5mb. If your file is larger than that, try removing columns you may not need. See below for additional information on specific fields.

Tip: You do not have to import every column from your CSV. Only fields set up in your CMS collection in the next step will be imported.

Rich Text Fields

Formatted text content needs to be formatted as HTML. Many tags are supported, such as paragraphs and headers <p>,<h1>, <h2>), formatting (<em>, <i>, <strong>), links (<a>), lists (<ol>, <ul>, <li>) and images (<img>). Images from URLs will be automatically downloaded from their original source and imported into Framer.

Image Fields

Images in your CSV content must be URLs to an image. They will be downloaded and imported into Framer. Relative paths are not supported.

Date Fields

Recommended format is ISO8601 compliant, for example: 2023-12-17T14:42:00. The shorthand value of year-month-day is also supported, for example: 1982-12-01. Long format strings may work, but will depend on your browser, for example: Tue May 12 2020 18:50:21 GMT-0500 (Central Daylight Time). All time data, including time zone information, will be stripped from the date.

Color Fields

A color formatted as CSS hexadecimal RGB code, rgb, hls or hlv expression, or a named color. All variants with an alpha value are also supported. Examples: #00ffee, rgb(0, 153, 255), hsla(204, 100%, 50%, 0.5), blue, darkgreen, rebeccapurple.

Toggle Fields

A boolean value. Y, yes, TRUE, 1 will be interpreted as the toggle being "Yes", all other values will be "No".

Prepare your CMS Collection

Here is a checklist to prepare your CMS collection for importing.

  1. Verify each field/column in your CSV has a matching field in your CMS collection with the same name.

  2. Include a unique field for each item, often named "Slug"

  3. Verify that your data types match (eg. a CMS Date field for a date field in your data)

Tip: Framer uses your Slug field to identify each item, and will use it to update that item with repeat imports.

Import your CSV file

You can find the Import feature by going to the CMS in your project, and clicking "Import" in the toolbar. From there, you can select your CSV file for importing. You may also drag & drop your CSV file directly into the CMS collection interface.

Tip: Importing supports Undo / Redo actions. If you're not happy with the import, you can simply undo the change with CMD+Z on MacOS or CTRL + Z on Windows. Redo will not re-run the import, but instantly apply the changes to the collection.

Updating or Re-Importing

To update your content, you can import into the same collection again. If any item in the new import has a slug field that matches one of the items in your collection, you will be able to update it or skip importing it again.

Prepare your CSV file

Make sure your file is exported as a "CSV" file, also known as a "Comma Separated Values" file. If you encounter any issues you'll want to verify your file is UTF-8 encoded and less than 5mb. If your file is larger than that, try removing columns you may not need. See below for additional information on specific fields.

Tip: You do not have to import every column from your CSV. Only fields set up in your CMS collection in the next step will be imported.

Rich Text Fields

Formatted text content needs to be formatted as HTML. Many tags are supported, such as paragraphs and headers <p>,<h1>, <h2>), formatting (<em>, <i>, <strong>), links (<a>), lists (<ol>, <ul>, <li>) and images (<img>). Images from URLs will be automatically downloaded from their original source and imported into Framer.

Image Fields

Images in your CSV content must be URLs to an image. They will be downloaded and imported into Framer. Relative paths are not supported.

Date Fields

Recommended format is ISO8601 compliant, for example: 2023-12-17T14:42:00. The shorthand value of year-month-day is also supported, for example: 1982-12-01. Long format strings may work, but will depend on your browser, for example: Tue May 12 2020 18:50:21 GMT-0500 (Central Daylight Time). All time data, including time zone information, will be stripped from the date.

Color Fields

A color formatted as CSS hexadecimal RGB code, rgb, hls or hlv expression, or a named color. All variants with an alpha value are also supported. Examples: #00ffee, rgb(0, 153, 255), hsla(204, 100%, 50%, 0.5), blue, darkgreen, rebeccapurple.

Toggle Fields

A boolean value. Y, yes, TRUE, 1 will be interpreted as the toggle being "Yes", all other values will be "No".

Prepare your CMS Collection

Here is a checklist to prepare your CMS collection for importing.

  1. Verify each field/column in your CSV has a matching field in your CMS collection with the same name.

  2. Include a unique field for each item, often named "Slug"

  3. Verify that your data types match (eg. a CMS Date field for a date field in your data)

Tip: Framer uses your Slug field to identify each item, and will use it to update that item with repeat imports.

Import your CSV file

You can find the Import feature by going to the CMS in your project, and clicking "Import" in the toolbar. From there, you can select your CSV file for importing. You may also drag & drop your CSV file directly into the CMS collection interface.

Tip: Importing supports Undo / Redo actions. If you're not happy with the import, you can simply undo the change with CMD+Z on MacOS or CTRL + Z on Windows. Redo will not re-run the import, but instantly apply the changes to the collection.

Updating or Re-Importing

To update your content, you can import into the same collection again. If any item in the new import has a slug field that matches one of the items in your collection, you will be able to update it or skip importing it again.

Want to See ORA for Yourself?

Venice Beach

In Person Virtual Tour

Famous for its bohemian spirit, colorful boardwalk, and eclectic street art.

Third Street Promenade

Zoom/ Phone Meeting

Bustling pedestrian-only shopping and dining district with street performers and local boutiques.

Monica Restaurant

VIP Experience

Farm-to-table dining experience featuring seasonal dishes and locally sourced ingredients.

EJ LUX CONSULTING, LLC is a consulting and promotional company. EJ LUX CONSULTING, LLC is not—and does not represent itself to be—the developer of any project shown on this website, its related landing pages, social media channels, or other marketing collateral. All content provided is for informational purposes only. While information has been gathered from sources believed to be reliable, it is subject to errors, omissions, and may change in price, availability, condition, or withdrawal without prior notice. Renderings, floor plans, square footages, and any other descriptions are approximate and should not be relied upon as exact representations. All marketing materials displayed have been supplied by the respective developer in affiliation with EJ LUX CONSULTING, LLC; EJ LUX CONSULTING, LLC assumes no responsibility for any inaccuracies or misstatements therein. Pricing, incentives, inventory, and other details may be updated or discontinued at any time. This information is not intended to be, nor should it be construed as, legal, tax, accounting, financial, or real estate advice. Prospective purchasers should consult their own advisors for guidance.

Any financial projections, income forecasts, leaseback or buyback returns, revenue splits, or pricing guidance displayed on this website are provided by developers or third-party sources and are strictly informational—not guarantees or investment advice. EJ LUX CONSULTING, LLC does not provide financial, legal, tax, or real estate brokerage services. Prospective purchasers should conduct independent due diligence and consult with their own professional advisors before making any financial decisions.

This website is not the official site of any developer. © EJ LUX CONSULTING, LLC. All rights reserved. Privacy Policy Here.

ORAL REPRESENTATIONS CANNOT BE RELIED UPON AS CORRECTLY STATING REPRESENTATIONS OF THE DEVELOPER. FOR CORRECT REPRESENTATIONS, MAKE REFERENCE TO THE DOCUMENTS REQUIRED BY SECTION 718.503, FLORIDA STATUTES, TO BE FURNISHED BY A DEVELOPER TO A BUYER OR LESSEE.

All dimensions, layouts, artist renderings, specifications, prices, and features are approximations and subject to availability and change without notice, as recommended by the architect, contractor, and/or developer, and/or as required by law. Stated dimensions are measured to the exterior boundaries if the exterior walls and corridor walls and to the centerline of interior demising and common walls, and may vary from the dimensions of the actual living space. Oral representations cannot be relied upon as correctly stating the representations of the developer. For correct representations, make reference to project documents provided by the developer to a buyer or lessee. All offers are subject to the terms and conditions of any sales or reservation agreement with the developer. Not an offer for or solicitation where prior registration is required or otherwise prohibited by these statutes..