Title: functions.php vs. @import
Last modified: August 30, 2016

---

# functions.php vs. @import

 *  [EBurden](https://wordpress.org/support/users/eburden/)
 * (@eburden)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/functionsphp-vs-import/)
 * I’ve successfully created child themes using the [@import](https://wordpress.org/support/users/import/)
   url, but recently I came across a child theme helper I was using which says and
   I quote, so I don’t mess it up,
 * “A functions.php file that is used to link your child theme to your master theme(
   this replaces the older version that was linking via the [@import](https://wordpress.org/support/users/import/)
   code in style.css which is now not the recommended way.”
 * This php is pretty much gibberish to me, though at the end it does refer to ‘/
   style.css’
 * I guess my questions are, 1, is this the preferred way to do this and 2, is there
   somewhere I can go to understand the various “enqueue” commands in this file.
   Or three what exactly does this file do?
 * Thanks, ernie

The topic ‘functions.php vs. @import’ is closed to new replies.

## Tags

 * [child](https://wordpress.org/support/topic-tag/child/)
 * [enqueue](https://wordpress.org/support/topic-tag/enqueue/)
 * [Import](https://wordpress.org/support/topic-tag/import/)
 * [style](https://wordpress.org/support/topic-tag/style/)

 * 0 replies
 * 1 participant
 * Last reply from: [EBurden](https://wordpress.org/support/users/eburden/)
 * Last activity: [10 years, 9 months ago](https://wordpress.org/support/topic/functionsphp-vs-import/)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics