# Can a Classic file be read by Elements?

**URL:** <https://forums.realmacsoftware.com/t/can-a-classic-file-be-read-by-elements/45128>\
**Category:** RapidWeaver Elements\
**Created:** [November 2, 2024, 8:23pm UTC](https://forums.realmacsoftware.com/t/can-a-classic-file-be-read-by-elements/45128 "2024-11-02T20:23:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![richjh](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/richjh/32/25726_2.png) [@richjh](https://forums.realmacsoftware.com/u/richjh)\
**Post date:** [November 2, 2024, 8:23pm UTC](https://forums.realmacsoftware.com/t/can-a-classic-file-be-read-by-elements/45128/1 "2024-11-02T20:23:45Z")

</div>

My Classic file has developed over years and the thought of Elements is a possibility when finished but if I have to start all over it won’t be worth it unless a means exists to port over my large site.

---

<div class="post-metadata">

**Author:** ![trinube](https://avatars.discourse-cdn.com/v4/letter/t/df788c/32.png) [@trinube](https://forums.realmacsoftware.com/u/trinube)\
**Post date:** [November 2, 2024, 9:07pm UTC](https://forums.realmacsoftware.com/t/can-a-classic-file-be-read-by-elements/45128/2 "2024-11-02T21:07:20Z")

</div>

In a word, no.

---

<div class="post-metadata">

**Author:** ![jscotta](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/jscotta/32/26082_2.png) [@jscotta](https://forums.realmacsoftware.com/u/jscotta)\
**Post date:** [November 3, 2024, 2:55am UTC](https://forums.realmacsoftware.com/t/can-a-classic-file-be-read-by-elements/45128/3 "2024-11-03T02:55:47Z")

</div>

I don’t think it will because things are very different. However, if I am reading the tea leaves correctly, most sites should be very easy to replicate in Elements. A lot will depend on the number and kinds of Stacks (if any) that you used. For example, if you using Workman’s excellent TCMS, at this point I think that is going to be very difficult to replicate.

---

<div class="post-metadata">

**Author:** ![cookie](https://avatars.discourse-cdn.com/v4/letter/c/d26b3c/32.png) [@cookie](https://forums.realmacsoftware.com/u/cookie)\
**Post date:** [November 5, 2024, 5:00am UTC](https://forums.realmacsoftware.com/t/can-a-classic-file-be-read-by-elements/45128/4 "2024-11-05T05:00:00Z")

</div>

Elements is a visual tailwind editor the Classic code is for bootstrap code however there is some tailwind code for incorporating bootstrap code I may be wrong Pinegrow uses both tailwind and seem to be using either your choice.

---

<div class="post-metadata">

**Author:** ![Bruno](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/bruno/32/25457_2.png) [@Bruno](https://forums.realmacsoftware.com/u/Bruno)\
**Post date:** [November 5, 2024, 5:32am UTC](https://forums.realmacsoftware.com/t/can-a-classic-file-be-read-by-elements/45128/5 "2024-11-05T05:32:17Z")

</div>

Hi @cookie

Yes, Pinegrow can use both Bootstrap and Tailwind CSS, but it’s generally not recommended to use them simultaneously due to potential conflicts. Here are three examples:

1. **Button Styles** : Bootstrap and Tailwind both provide button styles that might clash, leading to inconsistent appearances.
2. **Grid Systems** : Using both frameworks’ grid systems can cause layout issues as they follow different methodologies.
3. **Utility Classes** : Tailwind’s utility classes might override Bootstrap’s component styles, resulting in unexpected design changes.

Thanks to Perplexity for these examples.