Skip to content
This repository was archived by the owner on Aug 8, 2023. It is now read-only.

Commit 69f6706

Browse files
Added intended strategy for new builds.
1 parent 218f46d commit 69f6706

1 file changed

Lines changed: 7 additions & 3 deletions

File tree

css/hybrid-projects/Readme.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Hybrid App Projects
22

3-
## Structuring Your Styles For a Legacy Mobify Site
3+
## Structuring App Styles For a Legacy Mobify Site
44

55
CSS written specifically for webviews contained in a Native application should follow all normally prescribed best practices. This page will outline how to start a new app project, avoid adhering to legacy CSS code style, and provide a minimally sized CSS file to the web.
66

@@ -50,6 +50,10 @@ A hybrid project has a stylesheet specific to the OS. So a typical app project f
5050
@import 'android/templates/search-error';
5151
```
5252

53-
Stylesheets will be generated and served to the page depending on the context. If it’s an android app it gets ``android.css``, if its a website it gets ``stylesheet.css``, etc.
53+
Stylesheets will be generated and served to the page depending on the context. If it’s an android app it gets ``android.css``, if its a website it gets ``stylesheet.css``, etc.
5454

55-
> Stay tuned for what to do on brand new projects
55+
## Structuring App Styles For a Legacy Mobify Site
56+
57+
The current intended strategy in mind for future new builds is to have a single stylesheet for all platforms. Incorporating platform-specific theming and components into our existing CSS system.
58+
59+
This could serve to decrease the complexity associated with the system we use for legacy Mobify sites and potentially make hybrid projects easier to maintain.

0 commit comments

Comments
 (0)