Skip to content

Commit

Permalink
Now use https protocol for links to refinerycms.com
Browse files Browse the repository at this point in the history
  • Loading branch information
@bricesanchez
bricesanchez committed Oct 30, 2017
1 parent 5fb301b commit 88b8084
Show file tree
Hide file tree
Showing 21 changed files with 54 additions and 54 deletions.
2 changes: 1 addition & 1 deletion contributing.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -33,4 +33,4 @@ inclusion.

## Links ##

See also the [Contributing to Refinery](http://refinerycms.com/guides/contributing-to-refinery) guide.
See also the [Contributing to Refinery](/guides/contributing-to-refinery) guide.
2 changes: 1 addition & 1 deletion core/app/views/refinery/_site_bar.html.erb
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
<div id='site_bar'>
<div id='site_bar_content' class='clearfix'>
<%= link_to 'http://refinerycms.com', :id => 'site_bar_refinery_cms_logo', :target => '_blank' do %>
<%= link_to 'https://www.refinerycms.com', :id => 'site_bar_refinery_cms_logo', :target => '_blank' do %>
<%= image_tag 'refinery/refinery-cms-logo.svg', alt: 'Refinery CMS™' %>
<% end %>
Expand Down
2 changes: 1 addition & 1 deletion core/refinerycms-core.gemspec
View file
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Gem::Specification.new do |s|
s.summary = %q{Core extension for Refinery CMS}
s.description = %q{The core of Refinery CMS. This handles the common functionality and is required by most extensions}
s.email = %q{[email protected]}
s.homepage = %q{http://refinerycms.com}
s.homepage = %q{https://www.refinerycms.com}
s.rubyforge_project = %q{refinerycms}
s.authors = ['Philip Arndt', 'Uģis Ozols', 'Rob Yurkowski']
s.license = %q{MIT}
Expand Down
4 changes: 2 additions & 2 deletions doc/guides/1 - Getting Started/1 - Installation Prerequisites.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ If you are already a Rails developer, you will most likely not have to install a
* __Database__ - SQLite3 (default), MySQL, or PostgreSQL
* __ImageMagick__ - Recommended that you have the latest version installed

If you have all of these things, great! Proceed on to the [Getting Started with Refinery](/guides/getting-started/) guide.
If you have all of these things, great! Proceed on to the [Getting Started with Refinery](https://www.refinerycms.com/guides/getting-started/) guide.

Otherwise, choose your operating system below.

Expand Down Expand Up @@ -109,4 +109,4 @@ Follow the instructions at <http://www.imagemagick.org/script/binary-releases.ph

## Ready to Install!

Easier than expected right? Now you're ready to start building great websites with Refinery! Proceed on to the [Getting Started with Refinery](/guides/getting-started/) guide.
Easier than expected right? Now you're ready to start building great websites with Refinery! Proceed on to the [Getting Started with Refinery](https://www.refinerycms.com/guides/getting-started/) guide.
18 changes: 9 additions & 9 deletions doc/guides/1 - Getting Started/2 - Getting Started.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ This guide is designed for beginners who want to get started with a Refinery CMS
* A working installation of the [SQLite3 Database](http://www.sqlite.org)
* A working installation of [ImageMagick](http://www.imagemagick.org/script/install-source.php)

__TIP__: If you don't already have these things, then you will need to follow the [Installing Refinery Prerequisites](/guides/installation-prerequisites/) guide.
__TIP__: If you don't already have these things, then you will need to follow the [Installing Refinery Prerequisites](https://www.refinerycms.com/guides/installation-prerequisites/) guide.

__TIP__: It is recommended that developers use [rbenv](https://github.com/rbenv/rbenv) to manage Ruby versions and gems.

Expand Down Expand Up @@ -56,7 +56,7 @@ The extensions Refinery comes with are:

## Creating a new Refinery project

![](/system/images/W1siZiIsIjIwMTAvMTIvMDIvMTJfMDdfMTRfNjQ3X3JpY2tfYXN0bGV5X25ldmVyX2dvbm5hX2dpdmVfeW91X3VwLmpwZyJdXQ/rick-astley-never-gonna-give-you-up.jpg?sha=d5fdafec8a158121)
![](https://www.refinerycms.com/system/images/W1siZiIsIjIwMTAvMTIvMDIvMTJfMDdfMTRfNjQ3X3JpY2tfYXN0bGV5X25ldmVyX2dvbm5hX2dpdmVfeW91X3VwLmpwZyJdXQ/rick-astley-never-gonna-give-you-up.jpg?sha=d5fdafec8a158121)

If you follow this guide, you'll create a Refinery site called `rickrockstar` that will have a custom design. Then you'll be ready to go further in the following guide and add events extension to allow Rick to tell his fans when his next gig is.

Expand Down Expand Up @@ -137,7 +137,7 @@ $ rails server

This will fire up an instance of the built-in Rails web server by default (called WEBrick). To see your application in action, open a browser window and navigate to <http://localhost:3000/refinery>. You should be greeted with a screen prompting you to create your first Refinery user.

![](/system/images/W1siZiIsIjIwMTIvMDMvMDQvMTRfMTFfMjRfOTkzX3NldF91cF95b3VyX2ZpcnN0X3VzZXIucG5nIl1d/set-up-your-first-user.png?sha=42b2ae6479070760)
![](https://www.refinerycms.com/system/images/W1siZiIsIjIwMTIvMDMvMDQvMTRfMTFfMjRfOTkzX3NldF91cF95b3VyX2ZpcnN0X3VzZXIucG5nIl1d/set-up-your-first-user.png?sha=42b2ae6479070760)

__TIP__: To stop the web server, hit `Ctrl+C` in the terminal window where it's running.

Expand All @@ -151,7 +151,7 @@ Fill out the sign up form to create your first user. This will be the super user

Once you've created your first user you'll see Refinery's admin.

![](/system/images/W1siZiIsIjIwMTMvMDYvMDkvMjNfNTdfNDRfNzIxX2Rhc2hib2FyZC5wbmciXV0/dashboard.png?sha=d05ed9da6bb78669)
![](https://www.refinerycms.com/system/images/W1siZiIsIjIwMTMvMDYvMDkvMjNfNTdfNDRfNzIxX2Rhc2hib2FyZC5wbmciXV0/dashboard.png?sha=d05ed9da6bb78669)

### Setting Your Site Name

Expand All @@ -173,13 +173,13 @@ Now you're setup, click around the various tabs in the backend and become famili

### Switching to your front-end

![](/system/images/W1siZiIsIjIwMTAvMTIvMDIvMTJfNTdfMDZfNDIyX3N3aXRjaF90b193ZWJzaXRlLnBuZyJdXQ/switch-to-website.png?sha=a13b44877a69739e)
![](https://www.refinerycms.com/system/images/W1siZiIsIjIwMTAvMTIvMDIvMTJfNTdfMDZfNDIyX3N3aXRjaF90b193ZWJzaXRlLnBuZyJdXQ/switch-to-website.png?sha=a13b44877a69739e)

You're currently in the back-end Refinery site editor. To see the front-end site, click "Switch to your website".

As you can see, Refinery is already displaying a basic menu and layout ready for you to customise.

![](/system/images/W1siZiIsIjIwMTIvMDMvMjUvMjNfMjVfMThfNjg1X3JlZmluZXJ5X2RlZmF1bHRfZnJvbnRfZW5kX3NtYWxsLnBuZyJdXQ/refinery-default-front-end-small.png?sha=021f1e16d298eb86)
![](https://www.refinerycms.com/system/images/W1siZiIsIjIwMTIvMDMvMjUvMjNfMjVfMThfNjg1X3JlZmluZXJ5X2RlZmF1bHRfZnJvbnRfZW5kX3NtYWxsLnBuZyJdXQ/refinery-default-front-end-small.png?sha=021f1e16d298eb86)

### Customising the Design

Expand Down Expand Up @@ -234,7 +234,7 @@ As you can see we're going to render a view with some HTML5 tags and along with

When you edit the About page you'll see something like this:

![](/system/images/W1siZiIsIjIwMTMvMDYvMDkvMjNfNTdfNDRfNDg5X2Fib3V0X3BhZ2VfZWRpdC5wbmciXV0/about_page_edit.png?sha=6d88aaa196ad01a2)
![](https://www.refinerycms.com/system/images/W1siZiIsIjIwMTMvMDYvMDkvMjNfNTdfNDRfNDg5X2Fib3V0X3BhZ2VfZWRpdC5wbmciXV0/about_page_edit.png?sha=6d88aaa196ad01a2)

You'll notice two tabs on the page: "Body" and "Side Body". These are `PageParts`, or in other words, a single piece of content attached to this page that you can render in your view. There is a "Body" tab with some content on this screen. To render that same content in your view, put:

Expand Down Expand Up @@ -286,7 +286,7 @@ __TIP__: You can add CSS for specific pages by using their slug with `-page`. Th

Now when you view your front-end at <http://localhost:3000/about> you'll notice your site has a grey background, with a horizontal menu and two white content areas.

![](/system/images/W1siZiIsIjIwMTAvMTIvMDIvMTRfMjRfNTFfMjI3X2RlZmF1bHRfZGVzaWduX3NtYWxsLnBuZyJdXQ/default-design-small.png?sha=84c3f6a40328b9a6)
![](https://www.refinerycms.com/system/images/W1siZiIsIjIwMTAvMTIvMDIvMTRfMjRfNTFfMjI3X2RlZmF1bHRfZGVzaWduX3NtYWxsLnBuZyJdXQ/default-design-small.png?sha=84c3f6a40328b9a6)

### What we just did

Expand All @@ -296,4 +296,4 @@ Finally we added a (super) simple style that changes the colour of the backgroun

## What Next?

You have Refinery up and running and know how to display content, change the design, and work with the administrative backend. Now you're ready to see how to use RefineryCMS with your own models, views, and controllers (MVCs). You do this by generating and customizing a Refinery extension, which is covered in the [Generate an Extension to Use Your Own MVCs](/guides/generate-an-extension-to-use-your-mvcs) guide.
You have Refinery up and running and know how to display content, change the design, and work with the administrative backend. Now you're ready to see how to use RefineryCMS with your own models, views, and controllers (MVCs). You do this by generating and customizing a Refinery extension, which is covered in the [Generate an Extension to Use Your Own MVCs](https://www.refinerycms.com/guides/generate-an-extension-to-use-your-mvcs) guide.
16 changes: 8 additions & 8 deletions doc/guides/1 - Getting Started/3 - Generate an Extension to Use Your MVCs.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,9 @@ __WARNING__: This guide is based on Refinery CMS 2.1.0 so some of the code shown

## Guide Assumptions

This guide continues the Rick Rock Star example from the [Getting Started](/guide/getting-started/) guide. You will need to have Refinery installed and running as explained in that guide.
This guide continues the Rick Rock Star example from the [Getting Started](https://www.refinerycms.com/guides/getting-started/) guide. You will need to have Refinery installed and running as explained in that guide.

This guide does not assume that you have any prior experience with Refinery beyond what is covered in the [Getting Started](/guide/getting-started/) guide, but it does assume that you are somewhat familiar with Rails. If you are not familiar with Rails, you will still be able to step through the guide but you may not fully understand all of the commands or code. Here are some resources to learn more about Rails:
This guide does not assume that you have any prior experience with Refinery beyond what is covered in the [Getting Started](https://www.refinerycms.com/guides/getting-started/) guide, but it does assume that you are somewhat familiar with Rails. If you are not familiar with Rails, you will still be able to step through the guide but you may not fully understand all of the commands or code. Here are some resources to learn more about Rails:

* [Ruby on Rails](http://rubyonrails.org/)
* [Ruby on Rails Guides for v3.2](http://guides.rubyonrails.org/v3.2.14/) - Note that these are the guides for Rails version `3.2` since that is the version Refinery requires.
Expand Down Expand Up @@ -47,7 +47,7 @@ Here is a list of the most often used field types and what they give you:
-------------------- -------------------------------------------------------------------------------------------------------
```
If you remember from the [Getting Started](/guide/getting-started/) guide, we told Rick that we'll give him an area to post up events he'll be at. Although we could technically create a new page in Refinery to add the event content there, areas that have special functionality are much better suited as an extension.
If you remember from the [Getting Started](https://www.refinerycms.com/guides/getting-started/) guide, we told Rick that we'll give him an area to post up events he'll be at. Although we could technically create a new page in Refinery to add the event content there, areas that have special functionality are much better suited as an extension.
Rick is going to want to enter the following information about each event:
Expand Down Expand Up @@ -131,7 +131,7 @@ __TIP__: Models in Refinery extensions expect a string field that acts as the ti
Now go to the backend of your Refinery site ([http://localhost:3000/refinery](http://localhost:3000/refinery)) and
you'll notice a new tab called "Events". Click on "Add new event" and you'll see something like this:
![](/system/images/W1siZiIsIjIwMTMvMDYvMDkvMjNfNTdfNDRfODYwX2V2ZW50X3BhZ2VfZWRpdC5wbmciXV0/event_page_edit.png?sha=d45dd13cf1a97d8f)
![](https://www.refinerycms.com/system/images/W1siZiIsIjIwMTMvMDYvMDkvMjNfNTdfNDRfODYwX2V2ZW50X3BhZ2VfZWRpdC5wbmciXV0/event_page_edit.png?sha=d45dd13cf1a97d8f)
You'll see the entire form has been generated for you based off the field types you specified when generating the events section. The blurb has a visual editor, the date field is a date picker and the photo allows you to pick or upload a new photo from a built-in Refinery dialog.
Expand All @@ -141,15 +141,15 @@ Now click on "Switch to your website", and navigate to <http://localhost:3000/ev
You'll notice not only has Refinery generated the backend "Events" tab but also a new menu item called "Events" and two new front-end views,`index.html.erb` and `show.html.erb`, located in `vendor/extensions/events/app/views/refinery/events/` for you to customise.
![](/system/images/W1siZiIsIjIwMTAvMTIvMDIvMTRfMjRfNTFfNDE1X2V2ZW50c19lbmdpbmVfc21hbGwucG5nIl1d/events-engine-small.png?sha=d3af41646dd136ba)
![](https://www.refinerycms.com/system/images/W1siZiIsIjIwMTAvMTIvMDIvMTRfMjRfNTFfNDE1X2V2ZW50c19lbmdpbmVfc21hbGwucG5nIl1d/events-engine-small.png?sha=d3af41646dd136ba)
As you can see, Refinery makes it insanely easy to quickly add new extensions to manage various areas of a site.
But I've noticed one problem. The "2011 Music Awards" is showing up in the middle when it makes more sense to order the events with the latest event at the top. To fix this we need to understand what's happening under the hood of a Refinery extension. Let's dive in.
## Testing your extension
There is a separate guide which covers this subject found at [Testing Your Extension](/guides/testing/).
There is a separate guide which covers this subject found at [Testing Your Extension](https://www.refinerycms.com/guides/testing/).
## Crudify: The Backbone of Refinery Engines
Expand Down Expand Up @@ -218,10 +218,10 @@ end
Now when you look at <http://localhost:3000/events> you'll notice they're now being sorted by the event date.
![](/system/images/W1siZiIsIjIwMTAvMTIvMDIvMTRfMjRfNTFfMzE0X2V2ZW50c19lbmdpbmVfZml4ZWRfc21hbGwucG5nIl1d/events-engine-fixed-small.png?sha=452dcc1cbd2522c3)
![](https://www.refinerycms.com/system/images/W1siZiIsIjIwMTAvMTIvMDIvMTRfMjRfNTFfMzE0X2V2ZW50c19lbmdpbmVfZml4ZWRfc21hbGwucG5nIl1d/events-engine-fixed-small.png?sha=452dcc1cbd2522c3)
## What's Next?
Now that you've made your first Refinery application with a custom events extension, you should feel free to update it and experiment on your own. But you don't have to do everything without help.
If you need assistance getting up and running with Refinery, follow the [How to get help with Refinery Guide](/guides/how-to-get-help/).
If you need assistance getting up and running with Refinery, follow the [How to get help with Refinery Guide](https://www.refinerycms.com/guides/how-to-get-help/).
6 changes: 3 additions & 3 deletions doc/guides/1 - Getting Started/4 - How to get help.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,16 +10,16 @@ One of Refinery's key principles is "Encourage and Help Others" so if you have a

Connect to our [Refinery Gitter channel](https://gitter.im/refinery/refinerycms).

If you ask a question and don't get an immediate response, don't take offence; either wait a half-hour and ask again, or just post your question on the [Google Group](http://group.refinerycms.org) instead. This gives developers who are in other timezones or who are temporarily unavailable a chance to help you out.
If you ask a question and don't get an immediate response, don't take offence; either wait a half-hour and ask again, or just post your question on the [Google Group](https://groups.google.com/forum/#!forum/refinery-cms) instead. This gives developers who are in other timezones or who are temporarily unavailable a chance to help you out.

Please remember that Refinery is a fully open-source application. None of us are paid to fix it or improve it; we do so because we like Refinery and we greatly appreciate its value. Unfortunately, we cannot immediately drop everything to solve a problem for you (as much as we'd like to). Be patient, and try to figure out the problem on your own while you wait. The more information you can dig up yourself, the easier it is for us to help you resolve your issues expediently.

## Google Group

The [Refinery CMS Google Group](http://group.refinerycms.org) is a great place to ask for help if you don't get a response on Gitter. Your first message may take a short while to appear, as all first-time posters are required by Google Groups to pass moderation.
The [Refinery CMS Google Group](https://groups.google.com/forum/#!forum/refinery-cms) is a great place to ask for help if you don't get a response on Gitter. Your first message may take a short while to appear, as all first-time posters are required by Google Groups to pass moderation.

## Other places

* API (click 'File List' in top right) - <a href="http://api.refinerycms.org" title="http://api.refinerycms.org">http://api.refinerycms.org</a>
* [GitHub Wiki](https://github.com/refinery/refinerycms/wiki)
* [Guides](http://refinerycms.com/guides)
* [Guides](https://www.refinerycms.com/guides)
2 changes: 1 addition & 1 deletion doc/guides/2 - Refinery Basics/7 - Translate Refinery.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Refinery supports internationalization (I18n for short), which includes translat

## Setup

Before you start translating, you should clone a fresh copy of Refinery from GitHub. See [the contributing guide](/guides/contributing-to-refinery) for information regarding how to do that.
Before you start translating, you should clone a fresh copy of Refinery from GitHub. See [the contributing guide](https://www.refinerycms.com/guides/contributing-to-refinery) for information regarding how to do that.

It's not required, but we strongly advise you to create a separate branch when adding a translation or a new feature. You can do so by typing the following shell command.

Expand Down
2 changes: 1 addition & 1 deletion doc/guides/2 - Refinery Basics/8 - Extending Models.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Sometimes you will want to graft in extra functionality that requires extra data

In some situations, you may find it necessary to extend the existing models that come with Refinery. This will enable you to add additional functionality without resorting to overriding the model itself (an act which can break patch-level upgrades) or without resorting to duplicating the functionality of the existing models.

Model decorators are almost identical to [controller decorators](/guides/extending-controllers-and-models-with-decorators). The only difference, in fact, is in the name of the constant on which to invoke `class_eval` on. Keep in mind that adding an additional stored field will require you to create a new migration to update your database, too. If you are simply adding a convenience method on a model that doesn't change the database, this will obviously not apply.
Model decorators are almost identical to [controller decorators](https://www.refinerycms.com/guides/extending-controllers-and-models-with-decorators). The only difference, in fact, is in the name of the constant on which to invoke `class_eval` on. Keep in mind that adding an additional stored field will require you to create a new migration to update your database, too. If you are simply adding a convenience method on a model that doesn't change the database, this will obviously not apply.

In this example, we will add a background image to the Page model. Our use case is to allow an administrator to set a different background per page. To track this data, we will need to generate a migration:

Expand Down
2 changes: 1 addition & 1 deletion doc/guides/3 - Advanced Techniques and Tips/2 - Troubeshooting Image Problems.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Check that the file is still where Dragonfly saved it.

Refinery/Dragonfly allow you to use stores like Amazon S3, Couch and Mongo, or to write your own.

Refer to Refinery's Guide [Amazon S3 for Uploads](http://refinerycms.com/guides/amazon-s3-for-uploads) or to
Refer to Refinery's Guide [Amazon S3 for Uploads](https://www.refinerycms.com/guides/amazon-s3-for-uploads) or to
Dragonfly's [Data Store document](http://markevans.github.io/dragonfly/data-stores/).

## Dragonfly.log
Expand Down
2 changes: 1 addition & 1 deletion doc/guides/5 - Using Refinery as an Engine/1 - With an existing Rails app.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -70,4 +70,4 @@ You can create the initial admin user by visiting `localhost:3000/subfolder/refi

## Getting Help

As this is a relatively new process, if you need help with any of these steps we would love to [hear about it](/guides/how-to-get-help/).
As this is a relatively new process, if you need help with any of these steps we would love to [hear about it](https://www.refinerycms.com/guides/how-to-get-help/).
Loading

0 comments on commit 88b8084

Please sign in to comment.